Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

error 599 cannot connect to SQL

Status
Not open for further replies.

yolly12

MIS
Mar 21, 2005
83
this is a sidebar to the question I asked the other day about ODBC.

I am running Crystal 8.5 developer, GoldMine 6.7, SQL 2000 and Windows 2003 standard sever.

If I create an ODBC File dsn to my SQL box and use windows authentication it runs just fine. that would mean that the NT login would have to exist locally on the machine with the ODBC connection and that is not a good idea for admin (over 200 users). If I take that same dsn and then say for it to use SQL authentication and create a user in SQL, the connection fails. The error states that either the server doesn't exist or access is restricted.

If I try to run the report I get the error listed in my subject line. Where does one set the security to allow login from an ODBC source?

thanks

 
hi
read as follow
This is a known issue that occurs when IIS or any other application creates and attempts to use a System DSN after the installation of Crystal Reports 8. For more information, see the following Crystal Decisions Knowledge Base article:
(The Crystal Reports installation modifies the permissions for the HKEY_LOCAL_MACHINE\Software\ODBC\odbc.ini registry key and its subkeys. The Everyone group's permissions are changed from Special Access to Full Control.

When you create a new System DSN, it does not inherit the Windows NT default permissions, or the new permissions created by the Crystal Reports 8 installation. Instead, the subkey for the new DSN receives permissions for two user groups:

• Local Machine\Administrators -- Full Control

SYSTEM -- Full Control


Only the permissions for Administrators are set, and no permissions are set for the Everyone group. Therefore, only users with Administrator rights can access the System DSN.
RESOLUTION
Download and run the fix from the following Web site:
(MORE INFORMATION
Description of the Fix
The Scr8_webregfix.exe update resets all existing permissions in the HKEY_LOCAL_MACHINE\Software\ODBC\odbc.ini registry key (and all of its subkeys) to the Windows NT default permissions. It also resets sections of the HKEY_CLASSES_ROOT\Interface and HKEY_CLASSES_ROOT\Typelib subkeys to the Windows NT default values. Any new and existing System ODBC DSNs now inherit the Windows NT default permissions.

Version 8.0.0.84 requires that the Everyone group is set to Full Control and cannot connect to a System DSN by using a Special Access (default) registry permission level. The updated P2sodbc.dll file (version 8.0.0.85) is required to connect to a System DSN by using the Windows NT default registry permissions. (For example, the Everyone group is set to Special Access.)

NOTE: The P2sodbc.dll issue also applies when version 8.0.0.84 is distributed to computers that do not have Crystal Reports installed (for example, as part of an application previewing a Crystal Report). For more information, see the following Crystal Decisions Knowledge Base article:
(This fix also resolves the following SQL Server error messages if the System DSN has been set after Crystal Reports was installed:
Infinite logon to the database

Error 20599 - Cannot open SQL Server

Error 599

Error - An error has occurred on the server in attempting to access datasource
For more information, see the following Crystal Decisions Knowledge Base articles:
(
(

Durango122
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top