@Remote ID2 issues

[Itanic]

Hi all,,
We're a small company and only just started to get machines on @Remote a few months back. All our sites are pretty small with a maximum of 10 machines at most.
Of course 1 or 2 machines have failed to go onto @Remote because of a bad or missing ID2. So....we have no R/C Gates and really don't have a need for them.
@Remote support says to correct this you'll need an R/C gate and connect into the same network as the machine and rewrite the ID2 this way.
Have tried all the fixes offered 5816-209 5570-3 and -1. On one machine @remote was disabled in security but it then rewrote an odd number still into 5811-3..
As said all our machines are embedded,, if there is no other way and we have to buy an old R/C gate to get round this so be it....
So.....Does anyone know if there's a way to rewrite the ID2 via the NVRam? like through a hex editor or something? or will we have to bite the bullet and get hold of an R/C Gate? Cheers

[slimslob]

Re: @Remote ID2 issues

ID2 is normally rewritten by the @Remote server during registration. Check SP 5816-174. If it is too low, a timeout might occur. SP 5816-209 can be used to clear the embedded installation so you can start again.

NVram data can be exported to a SD card through SP mode. The file could then be edited with a hex editor. The problem is where in the file is the encrypted data you need to change and what do you changed it to.

[Itanic]

Re: @Remote ID2 issues

Thanks Slimslob. I just thought that you guys who have been using @Remote for almost 10 years might have had an easy way of resetting the ID2 other than use an R/C gate, as we've only been using using @Remote for literally 5 minutes in comparison.

[zed255]

Re: @Remote ID2 issues

As far as I know you need to use an appliance to do the ID2 re-write, never seen any other method.

Those of us handling @Remote issues usually carry an old appliance for the purpose, mine is an RC Gate A.

Might be something to consider getting as a 'service tool' the branch / dealership can share as needed.

[mavetherave311]

Re: @Remote ID2 issues

the only other way is sp5870 3 and then 1

[zed255]

Re: @Remote ID2 issues

the only other way is sp5870 3 and then 1

That is only for the common certificate. It has no effect on clearing or resetting the ID2 code in my experience.

[slimslob]

Re: @Remote ID2 issues

That is only for the common certificate. It has no effect on clearing or resetting the ID2 code in my experience.

A bad or missing common certificate will give the same error code in SP5816-208 as a bad or missing ID2.

[zed255]

Re: @Remote ID2 issues

Slim, he already knows the ID2 is trashed and is asking how to fix it. Someone suggested re-initializing and re-writing the Common Certificate to correct the issue, which it will not.

[slimslob]

Re: @Remote ID2 issues

Slim, he already knows the ID2 is trashed and is asking how to fix it. Someone suggested re-initializing and re-writing the Common Certificate to correct the issue, which it will not.

Sinnce he was not very specific as to when in the process that he got the error or the exact error number he got I can only assume that either SP 5816-202 or SP5816-206 failed with a Confirm Result or Register Result code of 8: Other error (See SP5-816-208 for detail). The error in SP 5816-208 was either "-12004 Attempted to install with invalid certification, ID2, and without input the machine number" or "-12009 Mismatched between ID2 in NR-RAM and ID2 in the individual certification". Both cases n=can be caused by a corrupted or missing common certificate. In fact, if ID2 contains five asterisks (*****) in stead of five spaces, the asterisks indicates a bad common certificate.

In any case what does it hurt to do as mavetherave311 says, clear the @Remote installation and start over. It might work and if it does it is a lot faster and less expensive than trying to get an RC gate.