Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
||
Product |
Prinergy Connect 2.0 | |
Platform |
||
Operating system |
||
|
|
||
Error |
When you start up Workshop for the first time on a system (typically after a fresh install), and you have left the Workshop dialog box with the default server selected, Workshop crashes with a NullPointerException trace. |
|
|
|
||
Symptoms |
Only happens when Workshop is run for the first time, after a fresh install, when you have not changed the default Prinergy primary server in the pull down list. This problem was introduced in 2.0.7.9. |
|
|
|
||
Cause |
The workshop crashes because the login.props file does not exist yet. | |
|
|
||
Solution |
In the Prinergy Workshop login dialog box, if you select any new entry (including selecting Other... and typing in the correct server name) in the pull down list, the Login.props file will be created, and the problem will then go away. This problem should not happen in the field, unless a new Workshop client is installed from scratch. If workshop was previously run, the login.props file will exist and the problem will not occur. Permanent fix: Prinergy 2.0 |
|
|
|
||
See also |
||
|
|
||
Keywords |
install, workshop |
|
|
|
||
Technical contact(s) |
Gordon Miller |
|
Submitted by |
Brian Laberge |
|
Date submitted |
23 Nov 2001 |
|