Unable to export update set as an XML file

[Praveen Paleka2]

Hi,

I am trying to export an update set as an XML file, but unable to do so. When i click the "Export to XML" link , it takes 5 mins to process the request and then a blank white screen appears.           1. Could it be because there are about 45k customer updates in the update set?? Or Could it be because its an update set of a scoped app??

        2. I understand that there is another way of retrieving the update sets from the target instance, but i dont want to use that method as it will import other completed update sets.

        3. I also tried publish link in studio , but that as well is not working as its throwing error "You do not own the vendor prefix for this scope"

FYI.. my instance version is helsinki and i would like to move the update set to a test env.

Any suggestions on how do I fix this issue.

Thanks!

[Ankur Bawiskar]

Hi Praveen,

If there are 45k customer updates in that update set that may be causing an issue since it would be large file and servicenow instance is getting timed out and you are getting blank screen.

If this problem persists you can check with ServiceNow team or else only option would be to retrieve completed update set via update sources.

Mark Correct if this solves your issue and also hit Like and Helpful if you find my response worthy based on the impact.

Thanks

Ankur

[Praveen Paleka2]

Thanks Ankur. Yes, we will be trying via update sources, lets see how that goes!

[Chuck Tomasi]

Praveen,

The best way to move updates for scoped apps is to publish them to the app repo and then install them on the other instance. There should be no need to publish to an update set and then export the update set unless you are moving from one organization to another (e.g. PDI to your company.) 45K updates is a lot. That sounds like the entire application, plus a lot more. Have you verified how many files are in the Application Files related list under System Applications> Application (then click the title of your scoped app.)

[Praveen Paleka2]

Hi Chuck,

We are unable to publish to app repo as an error appears "You do not own the vendor prefix for this scope". We will be trying via update sources from the target instance, lets see how that goes! Thanks for your reply!