Instead of manually entering queries for this problem table, why not just run the load_login.sql file? You can hand edit that before running it via sql command prompt to place in your name/password and the short and long server names. Since the password is SHA'd anyway this would skip a problem step.. hell if you want, PM me your details (Name, password, Server Long name, Server description, server short name) and I'll edit the files, zip em and you can try that. Worked a treat for me when I was a greenie smashing my head against the local loginserver.
Disclaimer - I've only loosely followed this thread, so I may be off base. I'll check back in a few, got dinner going right now.
|
Threaded Mode
