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: Explanation of Error 777  (Read 1274 times)

crotrei

  • Full Member
  • ***
  • Posts: 12
  • Place Personal Text Here
Explanation of Error 777
« on: September 13, 2005, 08:30:54 am »

I was just wondering if you could give me some clarity as to why error 777 comes up.  Is it a conflict between two ip addresses having the same sequence number? Have been getting a lot of people calling me about this and I would like to just have a better understanding of it myself.
Logged

Bob

  • Administrator
  • Ice Artist
  • *****
  • Posts: 1607
Explanation of Error 777
« Reply #1 on: September 13, 2005, 08:42:28 am »

777 simply means that 2 computers on the network have the same sequence number. The message tells you which IP's they are.

There are various reasons one can get into this situation:

Multiple license servers.
A reinstalled license server without restoring the licenses from the previous server.
Manually deleting active licenses in licenseadmin so that the next new licensed computer ends up getting an active sequence number.

Logged

RVWatson

  • Newbie
  • *
  • Posts: 1
  • Place Personal Text Here
Explanation of Error 777
« Reply #2 on: September 20, 2005, 09:59:00 am »

How do you fix it?
Logged

Bob

  • Administrator
  • Ice Artist
  • *****
  • Posts: 1607
Explanation of Error 777
« Reply #3 on: September 20, 2005, 10:10:58 am »

If your license database isn't too out of whack you can run licenseadmin (make sure there is only ONE license server) and delete the 2 conflicting users from the database and then rerun configwizard on the license server machine by BROWSING to it on the 2 conflicting client PC's and get a new sequence number (uncheck get configuration profile). Be sure to fill out both the user name and comment fields. If you get another conflict after that you can either repeat the process or depending on the number of client PC's, rerun configwizard on all of them as above. There are lots of posts here with details on running configwizard. You can search on those if you need more detail.
Logged
 

Page created in 0.013 seconds with 20 queries.