A remote instance with the same instance id already exists.

[prasanna11]

This error shows up though this is the first update source i am creating for an instance.

I am trying to move updates from prod to non prod instance. where prod is in eureka and non prod is in FUJI patch 2.

I have already looked into http://wiki.servicenow.com/index.php?title=Transferring_Update_Sets#

and Transferring Update sets - Connection Fails   But these havent helped much.

Can someone help me understand what an instance id is exactly? (the datatype of it and the value assigned to it)

Is there any possibility that two instances to have same instance ID.

Forgive my ignorance.

[Pradeep Sharma]

Hi Prasanna,

Go to system update sets->update sources->Now check if the URL already exists for the source you are trying to create now.

[Pradeep Sharma]

This is the BR Validate Instance ID which validates it.

[prasanna11]

Already checked that and found no update sources for the instance from which i need to pull updates.

[Jim Coyne]

Why don't you clone your production instance back down to the non-prod one and then update the non-prod to Fuji?   You should not be moving update sets down to non-production instances that way.   Update sets move up the chain from dev, test, qa to production and then you clone backwards.   Otherwise you will end up in an endless loop.

And why are there updates sets in production that are not in your non-prod environment?