Same device id for two devices

[AnkushBaveja]

Recently i was working on a UDS, i tested it successfully.

After applying it in envision, In gui->manage messages it was showing messages of some other device. Then i saw the ini file and my new device had picked up a device id which was already used by some other device and resulted in the conflict.

Is this a known bug with uds.exe ?

[CharlesBeierle]

What version of envision are you using? uds.exe is 'over with ' and should be replaced by ESI for devices without advanced envision xml functions. Thinking back to when I used uds.exe I believe support had to fix my database when I had that problem.

[AnkushBaveja]

M using 4.0 sp2. 

Can you explain a bit more on the fix 

Do you know if  support has introduced a update/patch for it since then ?

[RSAAdmin]

It is a known problem with uds.exe.  I don't know if they ever fixed it.

If you take the newest device that has an already used device ID, I believe you can just go into the INI file for that device and change the device ID to one that is unused and restart the services...IIRC that is what I did when I ran into the problem.

Now, that I know there is an issue, I always check the device ID in the INI before I restart services after doing an uds -create to make sure I have no overlap.

[RSAAdmin]

and if you are deploying using ESI installer, the VBS script there checks for next available device ID and updtes it automatically in .ini file. Watch out for next release of ESI due in November, which will allow you to update all appliances from a single server with uniue device ID.