Home » SQL ServerRSS

The specified resource type cannot be found - event id 17137

Hi,

We've got these errors appearing 4 at a time every 5 minutes on a new SBS 2008 box.

Log Name:      Application
Source:        MSSQL$MICROSOFT##SSEE
Event ID:      17137
Task Category: (2)
Level:         Information
User:          NETWORK SERVICE

Description:
The description for Event ID 17137 from source MSSQL$MICROSOFT##SSEE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
SharePoint_AdminContent_d4e397f2-a27a-48a0-a628-d25db6672bab
The specified resource type cannot be found in the image file

Anyone have any idea why this may be or how to resolve it ?

Olly

 

8 Answers Found

 

Answer 1

Hello,

Please do the following procedure for each of your Sharepoint databases:

1)Open SQL server management studio.

2)Right-click on the database and select “Properties”

3)Click on the Options page

4)Set “Auto close” to False

Hope this helps.

Regards,

Alberto Morillo
SQLCoffee.com

 

Answer 2

Thanks Alberto.

Can you help me with how I connect to the server-name\microsoft##ssee instance using the SQL express management studio ? No matter what I do it won't let me connect (this is using the administrator logon with windows authentication).

THe error I get connectng to that instance is;

TITLE: Connect to Server
------------------------------

Cannot connect to our-server\MICROSOFT##SSEE.

------------------------------
ADDITIONAL INFORMATION:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
-------------------------------

It works fine when connecting to the SBSMONITORING session.

Thanks

Olly

 

Answer 3

Hello,

Before trying to connect to your database instance, please enable network protocols. The following link will tell you how:

http://msdn.microsoft.com/en-us/library/ms165718.aspx

Enable Named Pipes and TCP/IP.

After that, restart your SQL Server instance.

1.On the Start menu, point to All Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Configuration Manager.

2.In SQL Server Configuration Manager, expand Services, and then click SQL Server.

3.In the results pane, right-click SQL Server (MSSQLSERVER), and then click Restart. Stopping and restarting the service will have the same effect. If SQL Server Agent is running, you will receive a notice that SQL Server Agent will also stop. In that case, choose “Yes”.

Now you can use SQL Server Management Studio to connect to your database instance, and change the “Auto close” option on your Sharepoint databases.

Hope this helps.

Regards,

Alberto Morillo
SQLCoffee.com

 

Answer 4

Hi Alberto.

Thanks again. We've hit another problem.

The Microsoft#ssee instance isnt visible in the SQL Server Configuration Manager under "SQL Server 2005 Network Configuration". I only see the SBSMONITORING instance. As such I can't edit the network connections properties to allow Named Pipes and TCP/IP.

However, I can get to those settings using the SQL Server 2005 Surface Area tool, but after restarting the WID (Microsoft#ssee) instance the remote connections properties reset back to Local Connections Only.

Ultimately, I still can't get the Management tool to log on to the Microsoft##ssee instance.

Any ideas why I wouldn't be seeing the instance in the SQL Configuration Manager ?

Olly
 

Answer 5

Thanks Alberto,

I figured out I could access the microsoft##ssee instance using the management app by uising the following details at the logon prompt;

Server Type: Database Engine
Server Name: \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
Authentication: Windows Authentication
 

Answer 6

Hello Oliver,

Great job! Are you able now to change
the “Auto close” option on your SharePoint databases?

I think after that you won't see the Event ID 17137 on the Application Event Log.

Regards,

Alberto Morillo
SQLCoffee.com

 

Answer 7

Hi,

We have been having the same issue on an SBS 2008 box. I followed the above suggestion to change the "Auto close" option and am now receiving the following event log entries:

The description for Event ID 5084 from source MSSQL$MICROSOFT##SSEE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

AUTO_CLOSE
OFF
SharePoint_AdminContent_d4e397f2-a27a-48a0-a628-d25db6672bab

The specified resource type cannot be found in the image file
 

Answer 8

Yes - Auto-Close was on.  Turning it off drastically reduced the number of events in the log.  However, even with all the "rll" files that are located in  the sql resource folder listed in the registry the event veiwer still complained it couldn't find the right resource file. It may be becase there are mulitple versions of SQL on the box....  Anyway, thanks for the auto-close advice!
 
 
 

<< Previous      Next >>


Microsoft   |   Windows   |   Visual Studio   |   Follow us on Twitter