ICE

Please login or register.

Login with username, password and session length
Advanced search  

News:

ICETCP.PRO and ICETCP.PLUS are compatible with Windows 11!

Author Topic: Configuration Error 777  (Read 1640 times)

jgt

  • Newbie
  • *
  • Posts: 1
  • Place Personal Text Here
Configuration Error 777
« on: March 31, 2004, 04:17:40 pm »

Fatal ICE.TCP Pro Configuration error 777
Conflict between IP address xx.xx.x.xx and xx.xx.x.xx.
Sequence #2 is duplicated.

5 User ICE.TCP Pro
This error has recently occurred...  
Now the 5 users who use ICE.TCP Pro are not working in harmony...

Is there a quick fix for this error?

Please Advise
Thank you,
jgt
Logged

Bob

  • Administrator
  • Ice Artist
  • *****
  • Posts: 1607
Configuration Error 777
« Reply #1 on: April 05, 2004, 09:57:17 am »

Rerun configwizard on the two conflicting machines. Do this by BROWSING to the TCP5_USER share on the license server machine and go into TCP-PRO and run configwizard.exe. Just tell it to get a sequence number.

Make SURE you don't have 2 license servers!

Let configwizard get the sequence numbers as detailed above instead of entering them manually. Most times this problem arises when someone makes a mistake and enters incorrect data manually.
Logged

sphilip

  • Newbie
  • *
  • Posts: 4
  • Place Personal Text Here
Re:Configuration Error 777
« Reply #2 on: June 07, 2004, 01:30:02 pm »

I am having the same problem.  I have unitstalled and Re-installed ICE on both workstation.  The admin server shows that both machines have different sequence numbers, but It is still giving the 777 error
Logged

Bob

  • Administrator
  • Ice Artist
  • *****
  • Posts: 1607
Configuration Error 777
« Reply #3 on: June 08, 2004, 10:36:52 am »

It's possible in that case that the admin server is not the same version as the version you are installing on the client PC's. If you clear out those two entries in the licenseadmin and run a net install FROM the licenseadmin server you should end up with unique sequence numbers at the end of the process. Make sure the version on the licenseadmin server is >5.0.80 if you are going to install on 2k or xp.

Finally, we have had some reports of these duplicates when the machine names are the same except for a number at the end. Like dhcp1 dhcp2 dhcp3, etc but have not been able to reproduce them here. If this is the case for you and the above process doesn't work, change the name of one of the conflicting machines and repeat the above process.

Let us know what the results are please.
Logged
 

Page created in 0.015 seconds with 21 queries.