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 ; Prinergy Direct 2.0 ; Prinergy Access 2.0 ; Prinergy PowerPack 1.0 ; Prinergy Connect 2.1 ; Prinergy Direct 2.1 ; Prinergy Access 2.1 ; Prinergy Powerpack 2.1 | |
Platform |
Intel |
|
Operating system |
Windows 2000 |
|
|
|
||
Error |
TNS:listener could not resolve SERVICE_NAME given |
|
|
|
||
Symptoms |
Whenever Prinergy is started after a re-boot, several Oracle error messages appear in Diagview indicating that Prinergy cannot connect to the database. |
|
|
|
||
Cause |
These four Oracle services have been set to startup manually: - OracleCreoTNSListener - OracleServiceCreo - OracleStarter - OracleWebAssistant0 |
|
|
|
||
Solution |
The Oracle services must be set to start automatically. 1) Click Start -> Programs -> Administrative Tools -> Services 2) In Services, right-click the OracleTNSListener service and select Properties. 3) In Properties, set the Startup Type to Automatic and click OK to save the change. 4) Repeat the steps for the OracleServiceCreo, OracleStarter and OracleWebAssistant0 services. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
oracle |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
10 Dec 2002 |
|