Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Theresa Danowski 16 posts 78 karma points
    Nov 18, 2014 @ 12:20
    Theresa Danowski
    0

    Zbu ModelsBuilder: API version conflict

    Hi guys,

    I'm working with this realy cool framework and first of all I have to say great work!!!

    Lately I get an errormessage every time I try to rebuild my Models with the builder:

    ZbuModelsBuilder: ZbuModelsBuilder failed to generate code: Exception: Response status code does not indicate success (Forbidden)
    "API version conflict: client version (0.0.0.0) is not compatible with server version(2.0.0.26)."
    ZbuModelsBuilder:    bei Zbu.ModelsBuilder.AspNet.ModelsBuilderApi.EnsureSuccess(HttpResponseMessage result)
       bei Zbu.ModelsBuilder.AspNet.ModelsBuilderApi.ValidateClientVersion()
       bei Zbu.ModelsBuilder.CustomTool.CustomTool.ZbuModelsBuilder.GenerateRaw(String wszInputFilePath, String wszDefaultNamespace, IntPtr[] rgbOutputFileContents, UInt32& pcbOutput, String& errMsg)

    To be honest, I'm not quite sure what I might have changes in my project to get this error and I don't know what have caused it. I also tried to run the builder in some other demo-projects with the framework, everytime I get the same error.
    A look to the dlls wasn't usefull eihter, all dlls are version 2.0.0.26.
    I also tried to reinstall the tool in Visual Studio, which didn't fixed the problem.

    Do you have any clues what I can do to run the builder successful again?

    Thanks for the help and best wishes
    Theresa

  • Jeroen Breuer 4861 posts 12139 karma points MVP 3x admin c-trib
    Nov 18, 2014 @ 12:39
    Jeroen Breuer
    100

    Hello,

    I've also run into these issues and Stephan fixed them: 

    https://github.com/zpqrtbnk/Zbu.ModelsBuilder/releases/tag/2.0.2-final

    https://github.com/zpqrtbnk/Zbu.ModelsBuilder/issues/21

    If you upgrade Models Builder NuGet to 2.0.2 and the Visual Studio Extension to 2.0.2 it should work again.

    The visual studio extension 2.0.0 is the only version that is compatible with NuGet 2.0.0 and 2.0.2. That version isn't available for download anymore, but I could email it if you want it.

    Jeroen

     

  • Theresa Danowski 16 posts 78 karma points
    Nov 18, 2014 @ 13:29
    Theresa Danowski
    0

    Thanks for the quick reply.

    Lucky me, I got the installation for the Visual Studio Extension 2.0.0 still in my pc and could downgrade it again. Now everything is working again :)
    Thank you so much for your help!!!

    Best wishes
    Theresa 

  • Daniel P 1 post 21 karma points
    Nov 20, 2014 @ 01:21
    Daniel P
    0

    I am running into this problem with 2.0.2-final for both the VS extension AND the NuGet packages. It worked for the briefest of moments late last night... then I checked in my work and quit for the day. Did a pull first thing in the morning (nothing had changed) and nothing. All I get is this:

    ZbuModelsBuilder: Starting 11/19/2014 12:26:00 PM.
    ZbuModelsBuilder: ZbuModelsBuilder failed to generate code: Exception: Response status code does not indicate success (Forbidden)
    "API version conflict: client version (0.0.0.0) is not compatible with server version(2.0.2.31)."
    ZbuModelsBuilder:    at Zbu.ModelsBuilder.AspNet.ModelsBuilderApi.EnsureSuccess(HttpResponseMessage result)
       at Zbu.ModelsBuilder.AspNet.ModelsBuilderApi.ValidateClientVersion()
       at Zbu.ModelsBuilder.CustomTool.CustomTool.ZbuModelsBuilder.GenerateRaw(String wszInputFilePath, String wszDefaultNamespace, IntPtr[] rgbOutputFileContents, UInt32& pcbOutput, String& errMsg)
    

    Over and over and over again. I uninstalled, re-installed using every method available to me and nothing works. I have even pulled the source down and run the console application against my local site... same problem. The "client version" ALWAYS EQUALS 0.0.0.0.

  • Stephen 767 posts 2271 karma points c-trib
    Nov 20, 2014 @ 13:08
    Stephen
    0

    Damn, I was pretty sure I got rid of those pesky versionning issues!!! Looking at it ;-)

  • Robert Lundberg 14 posts 60 karma points
    Dec 05, 2014 @ 08:28
    Robert Lundberg
    0

    Is there a solution to this? I'm also running in to this problem and i dont have the 2.0 VSIX (if thats even work?)

    //
    regards
    Robert 

  • Barry Fogarty 493 posts 1129 karma points
    Dec 09, 2014 @ 12:50
    Barry Fogarty
    0

    @Robert - it is possible but it involves a fair bit of jiggerey pokery configuring the Nuget packages/dependencies.  See this thread

     

     

     

     

     

  • Robert Lundberg 14 posts 60 karma points
    Dec 15, 2014 @ 11:54
    Robert Lundberg
    0

    Thanks Barry. I did manage to solve this but in the end It just worked when i did reinstall everything (ModelsBuilder, ModelBuilder Site integration and ModelsBuilder VSIX) I think it was that The System.Collections.Immutable was bumped to a higher version, but I'm not at all sure..

    //Robert

  • Stephen 767 posts 2271 karma points c-trib
    Jan 12, 2015 @ 09:13
    Stephen
    0

    Have released 2.0.3 which should take care of most versions issues.

  • Jeroen Breuer 4861 posts 12139 karma points MVP 3x admin c-trib
    Jan 27, 2015 @ 10:37
    Jeroen Breuer
    0

    I've got the VSIX extension 2.0.0. Zbu.ModelsBuilder and Zbu.ModelsBuilder.AspNet are 2.0.3-final. When I try to run the models builder I get the following exception:

    ZbuModelsBuilder: Starting 27-01-15 10:35:44.
    ZbuModelsBuilder: ZbuModelsBuilder failed to generate code: Exception: Response status code does not indicate success (InternalServerError)
    {"Message":"An error has occurred.","ExceptionMessage":"Value cannot be null.\r\nParameter name: v1","ExceptionType":"System.ArgumentNullException","StackTrace":"   at System.Version.op_LessThanOrEqual(Version v1, Version v2)\r\n   at Zbu.ModelsBuilder.Compatibility.IsCompatible(Version clientVersion)\r\n   at Zbu.ModelsBuilder.AspNet.ModelsBuilderApiController.ValidateClientVersion(ValidateClientVersionData data)\r\n   at lambda_method(Closure , Object , Object[] )\r\n   at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass13.<GetExecutor>b__c(Object instance, Object[] methodParameters)\r\n   at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.Execute(Object instance, Object[] arguments)\r\n   at System.Threading.Tasks.TaskHelpers.RunSynchronously[TResult](Func`1 func, CancellationToken cancellationToken)"}
    ZbuModelsBuilder:    at Zbu.ModelsBuilder.AspNet.ModelsBuilderApi.EnsureSuccess(HttpResponseMessage result)
       at Zbu.ModelsBuilder.AspNet.ModelsBuilderApi.ValidateClientVersion()
       at Zbu.ModelsBuilder.CustomTool.CustomTool.ZbuModelsBuilder.GenerateRaw(String wszInputFilePath, String wszDefaultNamespace, IntPtr[] rgbOutputFileContents, UInt32& pcbOutput, String& errMsg)

    Any idea what this could be?

    Jeroen

  • Stephen 767 posts 2271 karma points c-trib
    Jan 27, 2015 @ 10:50
    Stephen
    0

    2.0.0 VSIX won't work w/ latest versions - upgrade VSIX. Though you should have got a nicer message.

  • Jeroen Breuer 4861 posts 12139 karma points MVP 3x admin c-trib
    Jan 27, 2015 @ 10:56
    Jeroen Breuer
    0

    On the release page of 2.0.3 it says this: "You do not need to upgrade the VSIX extension as it is unchanged since 2.0.0.".

    We've still got some websites running on Zbu.ModelsBuilder 2.0.0-final. We don't want to upgrade those. It would be nice it we could have 1 VSIX extension that works on both Zbu.ModelsBuilder 2.0.0-final and Zbu.ModelsBuilder 2.0.3-final.

    Jeroen

  • Stephen 767 posts 2271 karma points c-trib
    Jan 27, 2015 @ 11:10
    Stephen
    0

    My bad. 2.0.0 vsix should indeed work with 2.0.3 website - let me check.

    OTOH cannot do a vsix that works with 2.0.0 AND 2.0.3+ website because 2.0.0 website does not have the required plumbing to support a "more recent" VSIX. Was added later on which is why 2.0.3 VSIX will talk to 2.0.2 website (because 2.0.2 has the required plumbing to support a "more recent" VSIX -- basically it accepts that the VSIX tells it to please support it).

  • Jeroen Breuer 4861 posts 12139 karma points MVP 3x admin c-trib
    Jan 27, 2015 @ 11:16
    Jeroen Breuer
    0

    I understand that you cannot do a vsix that works with 2.0.0 AND 2.0.3+ website, but I've still got the vsix 2.0.0 version which was always compatible with 2.0.0 website and shoud also work with the 2.0.3+ website right? So vsix 2.0.0 should work on both versions.

    Jeroen

  • Stephen 767 posts 2271 karma points c-trib
    Jan 27, 2015 @ 11:23
    Stephen
    0

    Exactly, and why vsix 2.0.0 fails is something I cannot explain at the moment - looking into it. I suspect something weird happening with WebAPI - some ppl report what you see (version is null) while others report that version is "0.0.0.0" which does not make much sense either.

  • Jeroen Breuer 4861 posts 12139 karma points MVP 3x admin c-trib
    Jan 27, 2015 @ 11:26
    Jeroen Breuer
    0

    So for now it's best to just use vsix 2.0.0 for 2.0.0 website and vsix 2.0.3 for 2.0.3 website. Too bad you can't have multiple versions of the vsix installed. Need to uninstall and reinstall it depending on the website version.

    Jeroen

Please Sign in or register to post replies

Write your reply to:

Draft