ReadTrace failing with "Login timeout expired"

Question

Hi,

I recently started looking at using the RML tools.
I have set them up and run them on my own machine with a cleanly installed version of SQL Server 2008.
That runs fine.

I then installed the tools on the DB server (Windows Server 2003, SQL Server 2008) and ran a trace, this produces a trc file.

When I try to see the output using ReadTrace it fails.
I am logged on to the server to run this so it is all local and I have full rights to SQL Server.

Here is the command line
ReadTrace -I"C:\temp\TraceFolder\sp_trace.trc" -oc:\temp\PPBreakout -S(localhost) -dPPProd

I have tried using the machine name instead of localhost and I have tried using a SQL user gave fully rights to instead of Windows Authentication but it makes no difference.

Below is the error log.
Can anyone offer any suggestions?
Or ideas on how to diagnose it further?

  Thanks, Vincent.


11/06/09 16:57:51.734 [0X00000FC0] Readtrace a SQL Server trace processing utility.
Version 9.01.0109 built for x64.
Copyright (c) Microsoft Corporation 1997-2008. All rights reserved.
11/06/09 16:57:51.734 [0X00000FC0] Number of processors: 1
11/06/09 16:57:51.734 [0X00000FC0]     Active proc mask: 0x00000001
11/06/09 16:57:51.734 [0X00000FC0]         Architecture: 9
11/06/09 16:57:51.734 [0X00000FC0]            Page size: 4096
11/06/09 16:57:51.735 [0X00000FC0]         Highest node: 0
11/06/09 16:57:51.735 [0X00000FC0]         Package mask: 0x00000001
11/06/09 16:57:51.735 [0X00000FC0]         Processor(s): 0x00000001 Function units: Separated
11/06/09 16:57:51.735 [0X00000FC0]           Processors: 0x00000001 assigned to Numa node: 0
11/06/09 16:57:51.735 [0X00000FC0] –IC:\temp\TraceFolder\sp_trace.trc
11/06/09 16:57:51.735 [0X00000FC0] –oc:\temp\PPBreakout
11/06/09 16:57:51.735 [0X00000FC0] –S(localhost)
11/06/09 16:57:51.736 [0X00000FC0] –dPPProd
11/06/09 16:57:51.736 [0X00000FC0] Using language id (LCID): 1024 [English_Ireland.1252] for character formatting with NLS: 0x00500100 and Defined: 0x00050100
11/06/09 16:57:51.736 [0X00000FC0] Attempting to cleanup existing RML files from previous execution
11/06/09 16:57:51.736 [0X00000FC0] Using extended RowsetFastload synchronization
11/06/09 16:57:51.737 [0X00000FC0] Establishing initial database connection:
11/06/09 16:57:51.737 [0X00000FC0] Server: (localhost)
11/06/09 16:57:51.737 [0X00000FC0] Database: PPProd
11/06/09 16:57:51.737 [0X00000FC0] Authentication: Windows
11/06/09 16:58:13.762 [0X00000FC0] Initial HRESULT: 0x80004005
11/06/09 16:58:13.762 [0X00000FC0]
11/06/09 16:58:13.762 [0X00000FC0] Dumping error record 1 of 3:
11/06/09 16:58:13.762 [0X00000FC0] --------------------------------------------------------------------------
11/06/09 16:58:13.762 [0X00000FC0]    Description       = Login timeout expired
11/06/09 16:58:13.763 [0X00000FC0]    Source            = Microsoft SQL Server Native Client 10.0
11/06/09 16:58:13.763 [0X00000FC0]    ERRORINFO.hrError = 0x80004005
11/06/09 16:58:13.763 [0X00000FC0]    ERRORINFO.dwMinor = 0
11/06/09 16:58:13.763 [0X00000FC0]    ERRORINFO.clsid   = {8F4A6B68-4F36-4E3C-BE81-BC7CA4E9C45C}
11/06/09 16:58:13.763 [0X00000FC0]    SQL State         = HYT00
11/06/09 16:58:13.763 [0X00000FC0]    Native Error      = 0
11/06/09 16:58:13.763 [0X00000FC0]
11/06/09 16:58:13.763 [0X00000FC0] Dumping error record 2 of 3:
11/06/09 16:58:13.764 [0X00000FC0] --------------------------------------------------------------------------
11/06/09 16:58:13.764 [0X00000FC0]    Description       = A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.
11/06/09 16:58:13.764 [0X00000FC0]    Source            = Microsoft SQL Server Native Client 10.0
11/06/09 16:58:13.764 [0X00000FC0]    ERRORINFO.hrError = 0x80004005
11/06/09 16:58:13.764 [0X00000FC0]    ERRORINFO.dwMinor = 53
11/06/09 16:58:13.765 [0X00000FC0]    ERRORINFO.clsid   = {8F4A6B68-4F36-4E3C-BE81-BC7CA4E9C45C}
11/06/09 16:58:13.765 [0X00000FC0]    SQL State         = 08001
11/06/09 16:58:13.765 [0X00000FC0]    Native Error      = 53
11/06/09 16:58:13.765 [0X00000FC0]
11/06/09 16:58:13.765 [0X00000FC0] Dumping error record 3 of 3:
11/06/09 16:58:13.765 [0X00000FC0] --------------------------------------------------------------------------
11/06/09 16:58:13.765 [0X00000FC0]    Description       = Named Pipes Provider: Could not open a connection to SQL Server [53].
11/06/09 16:58:13.766 [0X00000FC0]    Source            = Microsoft SQL Server Native Client 10.0
11/06/09 16:58:13.766 [0X00000FC0]    ERRORINFO.hrError = 0x80004005
11/06/09 16:58:13.766 [0X00000FC0]    ERRORINFO.dwMinor = 53
11/06/09 16:58:13.766 [0X00000FC0]    ERRORINFO.clsid   = {8F4A6B68-4F36-4E3C-BE81-BC7CA4E9C45C}
11/06/09 16:58:13.766 [0X00000FC0]    SQL State         = 08001
11/06/09 16:58:13.766 [0X00000FC0]    Native Error      = 53
11/06/09 16:58:13.766 [0X00000FC0] Unable to connect to the specified server.
11/06/09 16:58:13.767 [0X00000FC0] ERROR: Performance analysis failed to initialize.  See previous errors and correct the problem before retrying.
11/06/09 16:58:13.767 [0X00000FC0] *******************************************************************************
* ReadTrace encountered one or more ERRORS. An error condition typically      *
* stops processing early and the ReadTrace output may be unusable.            *
* Review the log file for details.                                            *
*******************************************************************************
11/06/09 16:58:13.767 [0X00000FC0] ***** ReadTrace exit code: -9

Answer 1

Please change -S(localhost) to -S<server name> (eg. -Sserver1) if this is the default instance and if it is a named instance, change it to -S<Server name>\<instance>

HTH

---

This posting is provided "AS IS" with no warranties, and confers no rights. My Blog: Troubleshooting SQL

Answer 2

Hi,

I had already tried the server name.
I have also tried adding the port number (it using the default, 1433) on to the machine name.
I also tried logging in as local Admin and Domain admin, and I tried doing it from my machine (remote) as well as local to the server.

All my attempts give me the same error.

I can open the "SQL Server Management Studio" using either the server name or localhost so I do have access and the same goes for the SQL User I created.


How can I tell if it is a named instance?
The instance is called MSSQLSERVER (so the default), and I can't open it in Managment Studio using "server\MSSQLSERVER", I have to use just "server", so I am assuming it isn't named.
I did try putting "server\MSSQLSERVER" into the command and still got the same error.

Any other suggestions?

  Thanks, Vincent

Answer 3

So, this is a default instance. Are you able to connect to the SQL Server instance using Named Pipes and TCP. In the Server Name text box, specify np:<server name> for Named Pipes and for TCP specify tcp:<server name>.

If any of these fails, create a named pipe or TCP alias (which ever failed) using Client Configuration utility.
Ref: http://msdn.microsoft.com/en-us/library/ms188635(SQL.90).aspx

HTH

---

This posting is provided "AS IS" with no warranties, and confers no rights. My Blog: Troubleshooting SQL

Answer 4

Hi,

Sorry for the delay, I have been working on other things and didn't see your response until now.

Both of those work.

  Vin