ERROR: Invalid attribute in connection string...
The Vantive error message "[INTERSOLV][ODBC Oracle driver]Invalid attribute in connection string: DBQ [INTERSOLV][ODBC Oracle driver][Oracle]ORA-12154: TNS: Could not resolve service name" is received when trying to run a Crystal Report is received because you are either not mapped to an N: drive or the TNSNAMES.ORA file needs to be reassociated with the N: drive.
Your N: drive must be mapped to \\ servername \psuserws. For regional employees, "servername" SHOULD be the first three letters of the site at which you are located followed by file-01. For example: Boston employees would be mapped to \\ bos-file-01\psuserws. For corporate headquarters (PeopleSoft Plaza, CarrAmerica (AT&T) Building, Campus) employees, the servername should be psp-common-01 or ple-common-01. Generally, your login script will automatically map you to the closest server.
For information on how to map your N: drive, click on the operating system you are using below:
WINDOWS NT 3.51
WINDOWS NT 4.0
WINDOWS 95
If you are sure that your N: drive is properly mapped, you need to verify that the Oracle client is pointing to the network version of the TNSNAMES.ORA file. For information on how to reassociate the TNSNAMES.ORA file to the N: drive, click here.
Open File Manager in the Main window of Program Manager.
Click on the Disk option of the menu bar and select Connect Network Drive....
Scroll down and select N: for the Drive:.
Type \\ servername\psuserws in the Path: field.
Click on the box next to Reconnec t at Startup so that this drive may be available to you in future sessions when you are logged onto the network.
Click on OK.
If your N: drive does not map automatically at logon after following the above steps, contact Technical Support Operations for further assistance.
Click here to return to the beginning of this document.
Open Windows Explorer by right-clicking on the Start menu and clicking on Explore.
Click on the Tools option of the menu bar and select Map Network Drive....
Scroll down and select N: for the Drive:.
Type \\ servername\psuserws in the Path: field.
Click on the box next to Reconnec t at Startup so that this drive may be available to you in future sessions when you are logged onto the network.
Click on OK.
If your N: drive does not map automatically at logon after following the above steps, contact Technical Support Operations for further assistance.
Click here to return to the beginning of this document.
To reassociate the TNSNAMES.ORA file with the N: drive:
Click on the Start button.
Select Programs from the pop up window and select PS Oracle from the next pop up menu.
Click on TNSNames on Network.
A Registry Editor window will pop up which says Information in C:\Apps\DB\ORACLE7\TNSNames.reg has been successfully entered into the registry will appear. Click on OK. The TNSNAMES.ORA file has now been reassociated with the N: drive.
Try running the Crystal report again.
If you continue receiving the error message, you will need to check your registry entries by doing the following:
Click on the Start button and select Run... from the pop up menu.
Type regedit in the Open: field and click on OK.
Double-click on HKEY_LOCAL_MACHINE in the Registry Editor and double-click on the SOFTWARE folder.
Click on ORACLE and verify that the TNS_ADMIN key says "n:\apps\dos\orawinv2\network\admin".
Close the Registry Editor by selecting Registry from the menu bar and E xit from the drop down menu.
Try running the Crystal report again. If you still cannot run the report, you will need to contact the Vantive Administrator for further assistance.
Click here to return to the beginning of this document.
Created by the PeopleSoft Knowledge Management Team.
Copyright © 1999
All rights reserved.
Created: dcb 06/24/1998
Revised: jem 01/26/1999