Issue time10:48:00 am, by Tom Green Email 12951 views
Categories: SQL Server, Errors


After a Sql Server restart, the service failed to start giving the following error messages:


Error: 26049, Severity: 16, State: 1.

Server local connection provider failed to listen on [ \\.\pipe\SQLLocal\MSSQLSERVER ]. Error: 0x5

Error: 17182, Severity: 16, State: 1.

TDSSNIClient initialization failed with error 0x5, status code 0x40. Reason: Unable to initialize the Shared Memory listener. Access is denied.

Error: 17182, Severity: 16, State: 1.

TDSSNIClient initialization failed with error 0x5, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Access is denied.

Error: 17826, Severity: 18, State: 3.

Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

Error: 17120, Severity: 16, State: 1.

SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.



When the SQL Server starts it tries to open listening named-pipes to accept client share memory or named-pipe connections. If the listening named-pipes are not closed properly during the last shutdown of SQL Server (maybe after a forced kill of the SQL Server process), there will be orphan named-pipe handles in the windows kernel file system.

To solve this issue, a quick solution will be to reboot the machine hosting the SQL Server.


Leave a comment
Issue time11:51:00 am, by Tom Green Email 11273 views
Categories: SSIS, Errors, Server Configuration


When trying to browse the SSIS packages from Management Studio the following error can apear:

The SQL Server specified in Integration Services service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic "Configuring the Integration Services Service" in SQL Server 2008 Books Online.


This error appears when you have only named SQL instances on the machine, or when the default instance runs on a different port than the default one (1433).

To fix this edit the MsDtsSrvr.ini.xml file:

SQL 2005 location:
C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml

SQL 2008 location:
C:\Program Files\Microsoft SQL Server\100\DTS\Binn\MsDtsSrvr.ini.xml

SQL 2012 location:
C:\Program Files\Microsoft SQL Server\110\DTS\Binn\MsDtsSrvr.ini.xml


Full story »

Leave a comment
Issue time12:20:00 pm, by Tom Green Email 6919 views
Categories: SSAS, Errors


 When trying to process a database cube the following error is received:

 Internal error: An unexpected exception occured.


After the restart of the SSAS service the event view shows the following error:

The file '\\?\X:\...\Data\master.vmp' could not be deleted. Please check the file for permissions.



Note that even if the SSAS Service is up and running when trying to execute some operation, even if they complete successfully, no modification are actually done. For example after restoring a cube database from a backup, although the operation completes successfully, the new database doesn?t appear in the Management Studio list.

The ?master.vmp could not be deleted? error message can appear sometimes if you just moved the SSAS databases from one location to another on the same server.

In this situation the solution is to grant rights "Modify" on this new data folder to the service account used to start the SSAS service. More information about this scenario you can find in this article:

If previous suggestion didn?t solved the issue you can try to find out if there is another process that is locking the master.vmp file. To do this you can use the Process Explorer tool, which can be found here:


Full story »

Leave a comment
Issue time06:45:00 am, by Tom Green Email 2760 views
Categories: SSAS, Errors


When trying to connect locally to a SSAS 2005 or 2008 instance, the following error can appear:


Cannot connect to ServerName\InstanceName.

A connection cannot be made. Ensure that the server is running.


Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. (System)

An existing connection was forcibly closed by the remote host (System)


Note that the connection to that specific SSAS instance can be established from SQL Server Management Studio remotely.



You can connect locally to the SSAS instance by using in SSMS instead of SERVER_NAME\Instance the following: local, . , ./Instance , SERVER_IP

Full story »

Leave a comment
Issue time08:20:00 am, by Tom Green Email 8768 views
Categories: SQL Server, Errors


When trying to select data from a view through a linked server the following error can appear:


OLE DB provider "SQLNCLI" for linked server "SERVER_NAME" returned message "Binding information is invalid.".

Msg 7346, Level 16, State 2, Line 1

Cannot get the data of the row from the OLE DB provider "SQLNCLI" for linked server " SERVER_NAME".


Tested with other views / tables, the linked server turns out to work fine so the problem is in particular with that view.



As a workaround you can select data from that view using OPENQUERY, and it works. 



The problem seems to be related to this particular view definition (wrong data type used, etc).

After recreating the view the select through linked server worked fine.


Leave a comment
July 2024
Sun Mon Tue Wed Thu Fri Sat
 << <   > >>
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31      


Email Subscription

Enter your email address:

Delivered by FeedBurner



XML Feeds

DBA Blog

Latest posts

SSAS More...
SSRS More...
Server Configuration More...
Server Configuration More...
Errors More...
SQL Server More...
SSIS More...


Which database platform do you use?

View Results

Powered by b2evolution