![]()
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
||
Product |
Prinergy 1.0; Prinergy 1.1; Prinergy Connect 2.0 | |
Platform |
||
Operating system |
||
|
|
||
Error |
||
|
|
||
Symptoms |
Workshop rejects your password. |
|
|
|
||
Cause |
Here's an example of how authentication works: If the Araxi authentication server (PMainDirectoryD, also known as MDIR) is running on BOND, MDIR will try to look up the username/password in BOND's local account database. You might be able to log in as ARAXI since the Installer creates a local ARAXI account automatically. If that doesn't work, MDIR will try to look up the username/password in the list of domains known to the server (for example, at Creo, this would typically be the CREO domain.) Lookup in the CREO domain will only work if Araxi/MDIR is running under a sufficiently privileged account. The account Araxi/MDR runs under also has to have the "Act as part of the Operating System" privilege, which can be set using the NT User Manager. (The Installer takes care of this but it can be changed at a later time, accidentally or otherwise.) An error message will appear in DIAG if the account does not have this privilege. |
|
|
|
||
Solution |
If your password doesn't work, try the following: 1) Make sure are you using the correct upper/lower case (and that the CAPS key hasn't been left on accidentally). 2) If you are using an NT domain account, do not prefix the user name with the domain name (this is in contrast to connecting to an NT share, where the domain name would be needed). Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
workshop |
|
|
|
||
Technical contact(s) |
Gordon Miller |
|
Submitted by |
||
Date submitted |
||