Apr
30
Written by:
Cindy Gross
Wednesday, April 30, 2008 2:31:16 PM
For SQL Server 2005:
1. Right click on your desktop (or wherever you are having the problem) and create a new text doc.
2. Rename it to .udl (make sure you do NOT have on "hide known extensions").
3. Double click, choose the SQL Server driver on the first tab (Provider).
4. On the 2nd tab (Connection) enter the SQL Server name (or SQL servername\instance for a named instance) in the Data Source box. Leave Location empty. For the server name enter the shortname/netbios name.
5. On the 2nd tab (Connection) choose "Use Windows NT Integrated security".
6. On the 2nd tab (Connection) choose the button "Test Connection".
7. If it fails, do a control-C and a cut/paste of the exact error and send it to me.
8. Now go to the 4th tab (All) and scroll down to highlight SSPI. Click on "Edit Value" and enter Kerberos as the Property Value.
9. Go back to the 2nd tab (Connection) and choose "Test Connection".
10. If it fails, do a control-C and a cut/paste of the exact error and send it to me.
11. If the shortname fails, try again with the FQDN and the IP address.
Please capture a SQL profiler trace with the error, login, and session events chosen during a failed connection attempt and send the trace file to me. Only run the GUI for the duration of the test, using the GUI profiler against a production server is not generally a good idea (for any lengthy or event intensive capture you should use command line, like PSSDiag does).
==================================
For Analysis Services 2005:
Test from a UDL on the client and the middle tier
1. Right click on your desktop and create a new text doc.
2. Rename it to .udl (make sure you do NOT have on "hide known extensions").
3. Double click, choose "Microsoft OLE DB Provider for Analysis Services 9.0" on the first tab (Provider)
4. On the 2nd tab (Connection) enter the AS server name (or AS servername\instance for a named instance) in the Data Source box. Leave Location empty. For the server name enter either the shortname/netbios name or the FQDN. Do not use the IP address.
5. On the 2nd tab (Connection) choose "Use Windows NT Integrated security".
6. On the 2nd tab (Connection) choose the button "Test Connection".
7. If it fails, do a control-C and a cut/paste of the exact error and send it to me.
8. Now go to the 4th tab (All) and scroll down to highlight SSPI. Click on "Edit Value" and enter Kerberos as the Property Value.
9. Go back to the 2nd tab (Connection) and choose "Test Connection".
10. If it fails, do a control-C and a cut/paste of the exact error and send it to me.
Please capture an AS profiler trace with the error, login, and session events chosen during a failed connection attempt and send the trace file to me.
Tags: