Sign in
 
HomeLibraryLearnDownloadsTroubleshootingCommunityForums
SQL Server Developer Center >
> 
> 
Management Studio: Internal connection fatal error (System.Data) on x64 clients

Unanswered Management Studio: Internal connection fatal error (System.Data) on x64 clients

  • Wednesday, February 01, 2012 1:55 PM
     
     
    Sign In to Vote
    0

    Our IT guys set up a new SQL 2008 R2 x64 server, and we've been using it for a few days without any problems. But when I tried to connect to it from SSMS on a Vista x64 PC, I get this error, as well as .NET Framework errors, e.g. Specified cast is not valid. I then set up a new PC with Windows 7 x64 and SQL 2008 R2, and I get the same problem.

    Is this a known issue? Have IT done something wrong installing SQL? Or do I have a problem on both x64 cliens? All our other clients are x86.

    Davesemm
     

All Replies

  • Thursday, February 02, 2012 3:15 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi Davesemm,

    Could you please post the detailed error message showed in the error log? And what is the detailed version of your failed OS and SQL Server?

     

    Best Regards,
    Peja

    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
     
  • Thursday, February 02, 2012 6:32 AM
     
     
    Sign In to Vote
    0

    Hi Peja,

    Here is the log. We use SQL Server authentication & connect via IPv4. There is an error on a login, SMSUser, but that was fixed after that message.

    Date,Source,Severity,Message
    02/02/2012 00:00:03,spid22s,Unknown,This instance of SQL Server has been using a process ID of 1832 since 2012/01/31 11:27:28 AM (local) 2012/01/31 09:27:28 AM (UTC). This is an informational message only; no user action is required.
    02/01/2012 10:22:09,Logon,Unknown,Login failed for user 'SMSUser'. Reason: Could not find a login matching the name provided. [CLIENT: 192.168.1.41]
    02/01/2012 10:22:09,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 5.
    02/01/2012 10:08:54,spid59,Unknown,AppDomain 20 (SMS2008-NMMM.dbo[runtime].19) created.
    02/01/2012 10:08:23,spid56,Unknown,FILESTREAM: effective level = 0<c/> configured level = 0<c/> file system access share name = 'MSSQLSERVER'.
    02/01/2012 10:08:23,spid56,Unknown,Configuration option 'clr enabled' changed from 0 to 1. Run the RECONFIGURE statement to install.
    02/01/2012 00:00:03,spid23s,Unknown,This instance of SQL Server has been using a process ID of 1832 since 2012/01/31 11:27:28 AM (local) 2012/01/31 09:27:28 AM (UTC). This is an informational message only; no user action is required.
    01/31/2012 15:19:08,spid22s,Unknown,AppDomain 19 (SMS2008-NMMM.dbo[ddl].18) unloaded.
    01/31/2012 15:19:07,spid27s,Unknown,AppDomain 18 (SMS2008-NMMM.dbo[ddl].17) unloaded.
    01/31/2012 15:19:07,spid21s,Unknown,AppDomain 17 (SMS2008-NMMM.dbo[ddl].16) unloaded.
    01/31/2012 15:19:06,spid24s,Unknown,AppDomain 16 (SMS2008-NMMM.dbo[ddl].15) unloaded.
    01/31/2012 15:19:05,spid19s,Unknown,AppDomain 15 (SMS2008-NMMM.dbo[ddl].14) unloaded.
    01/31/2012 15:19:05,spid28s,Unknown,AppDomain 14 (SMS2008-NMMM.dbo[ddl].13) unloaded.
    01/31/2012 15:19:04,spid20s,Unknown,AppDomain 13 (SMS2008-NMMM.dbo[ddl].12) unloaded.
    01/31/2012 15:19:04,spid18s,Unknown,AppDomain 12 (SMS2008-NMMM.dbo[ddl].11) unloaded.
    01/31/2012 15:19:03,spid16s,Unknown,AppDomain 11 (SMS2008-NMMM.dbo[ddl].10) unloaded.
    01/31/2012 15:19:02,spid16s,Unknown,AppDomain 10 (SMS2008-NMMM.dbo[ddl].9) unloaded.
    01/31/2012 15:19:02,spid23s,Unknown,AppDomain 9 (SMS2008-NMMM.dbo[ddl].8) unloaded.
    01/31/2012 15:19:01,spid26s,Unknown,AppDomain 8 (SMS2008-NMMM.dbo[ddl].7) unloaded.
    01/31/2012 15:19:01,spid21s,Unknown,AppDomain 7 (SMS2008-NMMM.dbo[ddl].6) unloaded.
    01/31/2012 15:19:00,spid28s,Unknown,AppDomain 6 (SMS2008-NMMM.dbo[ddl].5) unloaded.
    01/31/2012 15:19:00,spid27s,Unknown,AppDomain 5 (SMS2008-NMMM.dbo[ddl].4) unloaded.
    01/31/2012 15:18:59,spid22s,Unknown,AppDomain 4 (SMS2008-NMMM.dbo[ddl].3) unloaded.
    01/31/2012 15:18:58,spid25s,Unknown,AppDomain 3 (SMS2008-NMMM.dbo[ddl].2) unloaded.
    01/31/2012 15:18:31,spid20s,Unknown,AppDomain 2 (SMS2008-NMMM.dbo[ddl].1) unloaded.
    01/31/2012 15:18:30,spid57,Unknown,Common language runtime (CLR) functionality initialized using CLR version v2.0.50727 from C:\Windows\Microsoft.NET\Framework64\v2.0.50727\.
    01/31/2012 11:27:32,spid51,Unknown,Using 'xplog70.dll' version '2009.100.1600' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
    01/31/2012 11:27:32,spid51,Unknown,Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
    01/31/2012 11:27:31,spid51,Unknown,Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
    01/31/2012 11:27:31,spid51,Unknown,Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
    01/31/2012 11:27:31,spid51,Unknown,Using 'xpsqlbot.dll' version '2009.100.1600' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
    01/31/2012 11:27:31,spid51,Unknown,Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
    01/31/2012 11:27:28,spid6s,Unknown,Recovery is complete. This is an informational message only. No user action is required.
    01/31/2012 11:27:27,spid16s,Unknown,Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
    01/31/2012 11:27:27,spid19s,Unknown,Starting up database 'SMS2008-NMMM'.
    01/31/2012 11:27:27,spid18s,Unknown,Starting up database 'ReportServerTempDB'.
    01/31/2012 11:27:27,spid17s,Unknown,Starting up database 'ReportServer'.
    01/31/2012 11:27:27,spid16s,Unknown,Starting up database 'msdb'.
    01/31/2012 11:27:27,spid21s,Unknown,A new instance of the full-text filter daemon host process has been successfully started.
    01/31/2012 11:27:24,Logon,Unknown,Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
    01/31/2012 11:27:24,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 38.
    01/31/2012 11:27:22,Logon,Unknown,Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
    01/31/2012 11:27:22,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 38.
    01/31/2012 11:27:05,Server,Unknown,SQL Server is now ready for client connections. This is an informational message; no user action is required.
    01/31/2012 11:27:05,Server,Unknown,The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b<c/> state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
    01/31/2012 11:27:05,Server,Unknown,Dedicated admin connection support was established for listening locally on port 1434.
    01/31/2012 11:27:05,Server,Unknown,Server is listening on [ 127.0.0.1 <ipv4> 1434].
    01/31/2012 11:27:05,Server,Unknown,Server is listening on [ ::1 <ipv6> 1434].
    01/31/2012 11:27:05,Server,Unknown,Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
    01/31/2012 11:27:05,Server,Unknown,Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
    01/31/2012 11:27:05,Server,Unknown,Server is listening on [ 'any' <ipv4> 1433].
    01/31/2012 11:27:05,Server,Unknown,Server is listening on [ 'any' <ipv6> 1433].
    01/31/2012 11:27:05,Server,Unknown,A self-generated certificate was successfully loaded for encryption.
    01/31/2012 11:27:05,spid11s,Unknown,Service Broker manager has started.
    01/31/2012 11:27:04,spid11s,Unknown,The Database Mirroring protocol transport is disabled or not configured.
    01/31/2012 11:27:04,spid11s,Unknown,The Service Broker protocol transport is disabled or not configured.
    01/31/2012 11:27:04,spid10s,Unknown,Starting up database 'tempdb'.
    01/31/2012 11:27:04,spid10s,Unknown,Clearing tempdb database.
    01/31/2012 11:27:04,Server,Unknown,Virtual Interface Architecture protocol is not supported for this particular edition of SQL Server.
    01/31/2012 11:27:04,Server,Unknown,Warning: Support for the VIA protocol is deprecated and will be removed in a future version of Microsoft SQL Server. If possible<c/> use a different network protocol and disable VIA.
    01/31/2012 11:27:04,spid6s,Unknown,Server name is 'WIN-WC6BP8FI4TV'. This is an informational message only. No user action is required.
    01/31/2012 11:27:04,spid10s,Unknown,Starting up database 'model'.
    01/31/2012 11:27:03,spid6s,Unknown,The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
    01/31/2012 11:27:03,spid6s,Unknown,Starting up database 'mssqlsystemresource'.
    01/31/2012 11:27:03,spid6s,Unknown,SQL Trace ID 1 was started by login "sa".
    01/31/2012 11:27:03,spid6s,Unknown,FILESTREAM: effective level = 0<c/> configured level = 0<c/> file system access share name = 'MSSQLSERVER'.
    01/31/2012 11:27:02,spid6s,Unknown,Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    01/31/2012 11:27:02,spid6s,Unknown,Starting up database 'master'.
    01/31/2012 11:27:01,Server,Unknown,Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    01/31/2012 11:27:00,Server,Unknown,Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    01/31/2012 11:26:59,Server,Unknown,Detected 4 CPUs. This is an informational message; no user action is required.
    01/31/2012 11:26:59,Server,Unknown,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    01/31/2012 11:26:59,Server,Unknown,Registry startup parameters: <nl/>  -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf<nl/>  -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG<nl/>  -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    01/31/2012 11:26:59,Server,Unknown,This instance of SQL Server last reported using a process ID of 1868 at 2012/01/31 11:24:13 AM (local) 2012/01/31 09:24:13 AM (UTC). This is an informational message only; no user action is required.
    01/31/2012 11:26:59,Server,Unknown,Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    01/31/2012 11:26:59,Server,Unknown,Authentication mode is MIXED.
    01/31/2012 11:26:59,Server,Unknown,System Manufacturer: 'HP'<c/> System Model: 'ProLiant DL380 G5'.
    01/31/2012 11:26:59,Server,Unknown,Server process ID is 1832.
    01/31/2012 11:26:59,Server,Unknown,All rights reserved.
    01/31/2012 11:26:59,Server,Unknown,(c) Microsoft Corporation.
    01/31/2012 11:26:59,Server,Unknown,Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) <nl/> Apr  2 2010 15:48:46 <nl/> Copyright (c) Microsoft Corporation<nl/> Standard Edition (64-bit) on Windows NT 6.0 <X64> (Build 6002: Service Pack 2)

     

    Davesemm
     
  • Thursday, February 02, 2012 7:17 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi Davesemm,

    You may face the issue on 02/01/2012 .This part of error messsage may address the reason.

    02/01/2012 10:22:09,Logon,Unknown,Login failed for user 'SMSUser'. Reason: Could not find a login matching the name provided. [CLIENT: 192.168.1.41]
    02/01/2012 10:22:09,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 5.
    02/01/2012 10:08:54,spid59,Unknown,AppDomain 20 (SMS2008-NMMM.dbo[runtime].19) created.
    02/01/2012 10:08:23,spid56,Unknown,FILESTREAM: effective level = 0<c/> configured level = 0<c/> file system access share name = 'MSSQLSERVER'.
    02/01/2012 10:08:23,spid56,Unknown,Configuration option 'clr enabled' changed from 0 to 1. Run the RECONFIGURE statement to install.
    02/01/2012 00:00:03,spid23s,Unknown,This instance of SQL Server has been using a process ID of 1832 since

     

    If DB user SMSUser has already been matched login, please refer to this online article about how to trouble shooting remote connecting.

    Best Regards,
    Peja

    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
     
  • Thursday, February 02, 2012 7:46 AM
     
     
    Sign In to Vote
    0

    Please note that it does connect, but there are many errors. So it is not an issue of not being able to connect at all. x86 clients work normally, x64 clients (Win7 and Vista) have lots of errors. This is from SQL Managment Studio: other applications can connect.

    This is the Advanced Information from the connection error - it looks like an issue with the .Net library.

    ===================================

    Internal connection fatal error. (System.Data)

    ------------------------------
    Program Location:

       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
       at System.Data.SqlClient.SqlDataReader.CloseInternal(Boolean closeReader)
       at System.Data.SqlClient.SqlDataReader.Close()
       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
       at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
       at System.Data.SqlClient.SqlCommand.ExecuteReader()
       at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException)
       at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteReader(String sqlCommand, SqlCommand& command)
       at Microsoft.SqlServer.Management.Smo.ExecuteSql.GetDataReader(String query, SqlCommand& command)
       at Microsoft.SqlServer.Management.Smo.DataProvider.SetConnectionAndQuery(ExecuteSql execSql, String query)
       at Microsoft.SqlServer.Management.Smo.ExecuteSql.GetDataProvider(StringCollection query, Object con, StatementBuilder sb, RetriveMode rm)
       at Microsoft.SqlServer.Management.Smo.SqlObjectBase.FillData(ResultType resultType, StringCollection sql, Object connectionInfo, StatementBuilder sb)
       at Microsoft.SqlServer.Management.Smo.SqlObjectBase.FillDataWithUseFailure(SqlEnumResult sqlresult, ResultType resultType)
       at Microsoft.SqlServer.Management.Smo.SqlObjectBase.BuildResult(EnumResult result)
       at Microsoft.SqlServer.Management.Smo.SqlObjectBase.GetData(EnumResult erParent)
       at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()
       at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req, Object ci)
       at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object connectionInfo, Request request)
       at Microsoft.SqlServer.Management.Smo.ExecutionManager.GetEnumeratorDataReader(Request req)
       at Microsoft.SqlServer.Management.Smo.SqlSmoObject.GetInitDataReader(String[] fields, OrderBy[] orderby)
       at Microsoft.SqlServer.Management.Smo.SqlSmoObject.ImplInitialize(String[] fields, OrderBy[] orderby)
       at Microsoft.SqlServer.Management.Smo.SqlSmoObject.Initialize(Boolean allProperties)
       at Microsoft.SqlServer.Management.Smo.SqlSmoObject.OnPropertyMissing(String propname, Boolean useDefaultValue)
       at Microsoft.SqlServer.Management.Smo.PropertyCollection.RetrieveProperty(Int32 index, Boolean useDefaultOnMissingValue)
       at Microsoft.SqlServer.Management.Smo.PropertyCollection.GetValueWithNullReplacement(String propertyName, Boolean throwOnNullValue, Boolean useDefaultOnMissingValue)
       at Microsoft.SqlServer.Management.Smo.PropertyCollection.GetValueWithNullReplacement(String propertyName)
       at Microsoft.SqlServer.Management.Smo.Information.get_Edition()
       at Microsoft.SqlServer.Management.Smo.SqlSmoObject.IsExpressSku()
       at Microsoft.SqlServer.Management.Smo.SqlSmoObject.CheckVersionNotExpress(String uft)
       at Microsoft.SqlServer.Management.Smo.Server.get_JobServer()
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.AgentPropertyHandler.SetTsxInformation(Server server, INameObjectCollection properties)
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.AgentPropertyHandler.PopulateProperties(INodeInformation source, INameObjectCollection properties)
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NodeContext.PopulateProperties()
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.SetStaticProperties(NodeContext nodeContext)
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.BuildDynamicItemWithQuery(IList`1 nodes, INodeInformation source, INavigableItem sourceItem, String urnQuery, Boolean registerBuilder, Boolean registerBuiltItems)
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.BuildDynamicItem(IList`1 nodes, INodeInformation source, INavigableItem sourceItem, IFilterProvider filter)
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.Build(IList`1 nodes, INodeInformation source, INavigableItem sourceItem, IFilterProvider filter)
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItem.RequestChildren(IGetChildrenRequest request)
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ExplorerHierarchyNode.BuildChildren(WaitHandle quitEvent)

     

    Davesemm
     
  • Thursday, February 02, 2012 7:55 AM
     
     
    Sign In to Vote
    0

    This is the OS and SQL Info:

    Product: Microsoft SQL Server Standard Edition (64-bit)
    OS: Microsoft Windows NT 6.0 (6002)
    Platform: NT x64
    Version: 10.50.1600.1

    If I try to view the connection properties, all properties are shown as "Server is unavailable", even though I can open tables etc.

     

     

    Davesemm
     
  • Friday, February 03, 2012 9:08 AM
     
     
    Sign In to Vote
    0

    Another interesting problem: I couldn't close SQL Management Studio on the Vista x64 client. It simply stayed running; I rebooted the PC to get rid of it.

    I have been using the Vista x64 PC for about 2 years with no problems, connecting to hundreds of databases on about 15 SQL 2000, 2005 and 2008, x86 and x64 servers.

    The IT guys have either done something wrong, or there is a patch or something different that is causing this problem on this server. I'm worried that this server is going to go into production, and we'll have serious problems later on when x64 clients start trying to connect.

    Is there anything they could have configured wrong so that x86 clients are fine, but x64 clients get flakey connections?

    Davesemm