Microsoft KB Archive/105811: Difference between revisions
(importing KB archive) |
m (Text replacement - """ to """) |
||
Line 22: | Line 22: | ||
== SUMMARY == | == SUMMARY == | ||
SQL Server version 4.2 for Windows NT must be assigned a valid user account to be able to access resources on an OS/2 server running under Microsoft LAN Manager user security. Instructions on how to do this are in the section | SQL Server version 4.2 for Windows NT must be assigned a valid user account to be able to access resources on an OS/2 server running under Microsoft LAN Manager user security. Instructions on how to do this are in the section "Configuring Network Permissions for SQL Server" in the SQL Server for Windows NT "Configuration Guide," chapter 2, Server Configuration. | ||
<br /> | <br /> | ||
Line 69: | Line 69: | ||
</div></blockquote> | </div></blockquote> | ||
<br /> | <br /> | ||
Both of these cases can be resolved by using the Windows NT Control Panel/Services applet to have the SQL Server service run under a valid network account. Instructions for this are in the section | Both of these cases can be resolved by using the Windows NT Control Panel/Services applet to have the SQL Server service run under a valid network account. Instructions for this are in the section "Configuring Network Permissions for SQL Server in the SQL Server" in the "Configuration Guide." | ||
Additional query words: 4.20 Windows NT | Additional query words: 4.20 Windows NT |
Latest revision as of 10:02, 20 July 2020
INF: Accessing LAN Manager from SQL Server for Windows NT |
Q105811
The information in this article applies to:
- Microsoft SQL Server version 4.2x
SUMMARY
SQL Server version 4.2 for Windows NT must be assigned a valid user account to be able to access resources on an OS/2 server running under Microsoft LAN Manager user security. Instructions on how to do this are in the section "Configuring Network Permissions for SQL Server" in the SQL Server for Windows NT "Configuration Guide," chapter 2, Server Configuration.
MORE INFORMATION
Windows NT services run under system accounts. SQL Server setup puts the SQL Server service in a default System Account, sometimes referred to as the LocalSystem account. The LocalSystem account is unique in that it does not have an ID which can be passed to an OS/2 LAN Manager server for permission validation. If a user requests SQL Server to access a resource on an OS/2 server running LAN Manager user level security, Windows NT has no identifier to pass to the LAN Manager server and the access will be denied.
For example, when attempting to do a SQL Remote Procedure Call from SQL Server for Windows NT to SQL Server for OS/2 running under LAN Manager user security, the RPC may fail with,
unable to login to remote server
or a 7221 error:
Login to site '%.*s' failed
This is because the SQL Server for Windows NT does not have permissions to the LAN Manager's named pipe resource.
In addition, when attempting to dump to a dump device defined on a remote server running LAN Manager user security, the dump may fail with a 3201 error:
Can't open dump device x, device error or device offline. Please consult the SQL Server errorlog for more details.
The errorlog shows the message:
dbsopen: Backup device 'x:\dumpx.dat' failed to open, operating system error = 65(Network access is denied.)
Both of these cases can be resolved by using the Windows NT Control Panel/Services applet to have the SQL Server service run under a valid network account. Instructions for this are in the section "Configuring Network Permissions for SQL Server in the SQL Server" in the "Configuration Guide."
Additional query words: 4.20 Windows NT
Keywords : kbother
Issue type :
Technology : kbSQLServSearch kbAudDeveloper kbSQLServ420OS2
Last Reviewed: March 18, 1999 |