Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

ObjXml is invalid when publishing to nuget



  • Hi
    Trying to evaulate ProGet..

    In Teamcity I can push a nuget package to the default feed that comes with the installation of ProGet, but when I create another feed which looks to have the exact same settings etc I get this error:

    [14:32:48][push] Failed to process request. 'There was an error processing the request: objXml is invalid. Parameter name: objXml'.
    [14:32:48][push] The remote server returned an error: (500) Internal Server Error..

    I also get the same error when manually adding a package to may new feed via the "add package" button

    I've turned off the symbol/source setting and still doesn't work.

    Thanks
    Danny

    Product: ProGet
    Version: 3.3.5



  • Strange... That error message looks like it can only come from the extensibility system, if there is a failure deserializing the XML configuration for an extension. Do you have any extensions loaded (feed adapters, custom package stores, etc)?



  • No connector, filters or adapters. The default feed as the nuget connector, but I replicated this on my new feed and still got the error.
    thanks
    danny



  • Could you connect to the ProGet SQL database and run:

    SELECT * FROM Feeds
    

    and either post those results here or email to us at support at inedo.com?

    It seems like maybe somehow something got written to the PackageStore_Configuration column on the new feeds. I'm not sure where else this error could be coming from.



  • If you edit the feed properties for each feed, is there anything in the "Package store configuration" field? Based on the CSV you've sent, there is a * in one of the entries which would cause this error. Just delete that and it should work.



  • thanks I removed the '*' and the problem has gone.. not sure how that got there!

    But can you put some validation in place as I shouldn't really have got the error.

    Thanks for the very quick turnaround on the help.

    Danny



  • Reworking that page was already on our list of things to do for the next version, so this won't be an issue after that :) Thanks for your help!



Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation