Management Studio crashing on local SQL Server console

Unable to start the SQL Server Management Studio on the SQL Server 2012 running on Windows Server 2012 and 2012 R2
We have a number of SQL Servers deployed and in the last month all instances of the SSMS have stopped working with the following error message
Problem signature:
  Problem Event Name:                        APPCRASH
  Application Name:                            
Ssms.exe
  Application Version:                           2011.110.3000.0
  Application Timestamp:                     5081c1cd
  Fault Module Name:                          ntdll.dll
  Fault Module Version:                        6.3.9600.17476
  Fault Module Timestamp:                  54516af9
  Exception Code:                                 
c000007b
  Exception Offset:                               
000a36e5
  OS Version:                                         
6.3.9600.2.0.0.272.7
  Locale ID:                                            
1033
  Additional Information 1:                  1abe
  Additional Information 2:                  1abee00edb3fc1158f9ad6f44f0f6be8
  Additional Information 3:                  1abe
  Additional Information 4:                  1abee00edb3fc1158f9ad6f44f0f6be8
We have done the following to resolve this without success:
Run a repair from the installation package
Uninstalled SSMS and reinstalled
Copied in another ntdll.dll

This what is generated in the log when trying to start the application:
Date,Source,Severity,Message,Category,Event,User,Computer
01/16/2015 09:39:58,Windows Error Reporting,Information,Fault bucket <c/> type 0<nl/>Event Name: APPCRASH<nl/>Response: Not available<nl/>Cab Id: 0<nl/><nl/>Problem signature:<nl/>P1: Ssms.exe<nl/>P2: 2011.110.3000.0<nl/>P3:
5081c1cd<nl/>P4: ntdll.dll<nl/>P5: 6.2.9200.17046<nl/>P6: 53b485c4<nl/>P7: c000007b<nl/>P8: 00078c9e<nl/>P9: <nl/>P10: <nl/><nl/>Attached files:<nl/><nl/>These files may be available here:<nl/>C:\Users\felgersma\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Ssms.exe_89a64aa0912742cdc59239b0e49f3eea1441adb7_93419cf8<nl/><nl/>Analysis
symbol: <nl/>Rechecking for solution: 0<nl/>Report Id: af322b86-9da6-11e4-9418-ac162d73da9f<nl/>Report Status: 2048<nl/>Hashed bucket:,(0),1001,,cvcnt42
01/16/2015 09:39:56,Application Error,Error,Windows cannot access the file  for one of the following reasons: there is a problem with the network connection<c/> the disk that the file is stored on<c/> or the storage drivers installed on this
computer; or the disk is missing. Windows closed the program SQL Server Management Studio because of this error.<nl/><nl/>Program: SQL Server Management Studio<nl/>File: <nl/><nl/>The error value is listed in the Additional Data
section.<nl/>User Action<nl/>1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.<nl/>2. If the file still cannot be accessed and<nl/>
- It is on the network<c/> your network administrator should verify that there is not a problem with the network and that the server can be contacted.<nl/>
- It is on a removable disk<c/> for example<c/> a floppy disk or CD-ROM<c/> verify that the disk is fully inserted into the computer.<nl/>3. Check and repair the file system by running CHKDSK. To run CHKDSK<c/> click Start<c/>
click Run<c/> type CMD<c/> and then click OK. At the command prompt<c/> type CHKDSK /F<c/> and then press ENTER.<nl/>4. If the problem persists<c/> restore the file from a backup copy.<nl/>5. Determine whether other
files on the same disk can be opened. If not<c/> the disk might be damaged. If it is a hard disk<c/> contact your administrator or computer hardware vendor for further assistance.<nl/><nl/>Additional Data<nl/>Error value: 00000000<nl/>Disk
type: 0,(100),1005,,cvcnt42
01/16/2015 09:39:56,Application Error,Error,Faulting application name: Ssms.exe<c/> version: 2011.110.3000.0<c/> time stamp: 0x5081c1cd<nl/>Faulting module name: ntdll.dll<c/> version: 6.2.9200.17046<c/> time stamp: 0x53b485c4<nl/>Exception
code: 0xc000007b<nl/>Fault offset: 0x00078c9e<nl/>Faulting process id: 0x2384<nl/>Faulting application start time: 0x01d031b36fa19f2f<nl/>Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Ssms.exe<nl/>Faulting
module path: C:\Windows\SYSTEM32\ntdll.dll<nl/>Report Id: af322b86-9da6-11e4-9418-ac162d73da9f<nl/>Faulting package full name: <nl/>Faulting package-relative application ID:,(100),1000,,cvcnt42
01/16/2015 09:35:02,Windows Error Reporting,Information,Fault bucket <c/> type 0<nl/>Event Name: APPCRASH<nl/>Response: Not available<nl/>Cab Id: 0<nl/><nl/>Problem signature:<nl/>P1: Ssms.exe<nl/>P2: 2011.110.3000.0<nl/>P3:
5081c1cd<nl/>P4: ntdll.dll<nl/>P5: 6.2.9200.17046<nl/>P6: 53b485c4<nl/>P7: c000007b<nl/>P8: 00078c9e<nl/>P9: <nl/>P10: <nl/><nl/>Attached files:<nl/><nl/>These files may be available here:<nl/>C:\Users\felgersma\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Ssms.exe_89a64aa0912742cdc59239b0e49f3eea1441adb7_9d291751<nl/><nl/>Analysis
symbol: <nl/>Rechecking for solution: 0<nl/>Report Id: fb97f994-9da5-11e4-9418-ac162d73da9f<nl/>Report Status: 2048<nl/>Hashed bucket:,(0),1001,,cvcnt42

Similar Messages

  • SQL Sever Management Studio intellisense issue in SQL Server 2008 R2 and in SQL Sever 2012

    Hi Team,
    Intellisense in sql server management studio is working fine when i am accessing the databases in my  local server.
    But Intellisense is not working when ever i am trying to connect to the remote servers with the client
    I tried different blogs and i tried to configure all the options i have upgraded to some patches upgraded for sql 2008 r2 client to sql 2012 client.
    But Intellisense is not working with the remote server databases in the sql management studio .
    Intellisense is working in the server but the same is not working when we are trying to access with client from our local machines.
    Please provide me help to fix this issue
    Regards
    Karthik Kattamudi

    Did you try to refresh the cache by hitting CTRL+SHIFT+R?
    Also, these remote servers, are they SQL Server 2008 R2 as well or different version?
    Please mark the answer as helpful if i have answered your query. Thanks and Regards, Kartar Rana

  • Can't add datasource for local SQL Server Express

    I can't get new datasource to connect to a local SQL Server Express (2008).
    On SSE, I enabled non-NTLM authentication, created an account specifically for CFServer, and was able to log into SQL Server through Management Studio. But the datasource still won't connect.
    When I enter computerName/SQLServerName for the Server, I get a message saying "...The requested instance is either invalid or not running."
    When I enter just SQLServerName, message says "Error establishing socket. Unknown host: SQLServerName."
    When I enter (local), I get a message saying "Error establishing socket. Unknown host: (local)"
    When I enter 127.0.0.1, message says "Error establishing socket to host and port: 127.0.0.1:1433. Reason: Connection refused: connect"
    I don't know why the first is considered invalid, or why the fourth is refusing connection. Am I forgetting something?

    I found the solution, which doesn't have to do with Coldfusion, but rather with configuring SQL Server for TCP/IP.  In case someone else ever stumbles upon this post with a similar problem, I wrote about it at http://forums.devshed.com/ms-sql-development-95/trying-to-connect-to-sql-server-on-localho st-1433t-958558.html.

  • SQL ENTERPRISE: The edition of Reporting Services that you are using requires that you use local SQL Server relational databases for report data sources and the report server database

    The error below makes absolutely no sense! I'm using Enterprise Core...yet I'm being told I can't use remote data sources:
    w3wp!library!8!03/05/2015-19:08:48:: i INFO: Catalog SQL Server Edition = EnterpriseCore
    w3wp!library!8!03/05/2015-19:08:48:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: , Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "The edition of Reporting
    Services that you are using requires that you use local SQL Server relational databases for report data sources and the report server database." is not supported in this edition of Reporting Services.;
    Really? This totally contradicts the documentation found here:
    https://msdn.microsoft.com/en-us/library/ms157285(v=sql.110).aspx
    That article says remote connections are completely supported.
    ARGH! Why does this have to be so difficult to setup?!?

    Hi jeffoliver1000,
    According to your description, you are using Enterprise Core edition and you are prompted that you can’t use remote data sources.
    In your scenario, we neither ignore your point nor be doubt with what you say. But actually we have met the case before that even though the SQL Server engine is Enterprise but the reporting services is still standard. So I would recommend you to find the
    actual edition of reporting services you are using. You can find Reporting Services starting SKU in the Reporting Service logs ( default location: C:\Program Files\Microsoft SQL Server\<instance name>\Reporting Services\LogFiles). For more information,
    please refer to the similar thread below:
    https://social.technet.microsoft.com/Forums/en-US/f98c2f3e-1a30-4993-ab41-acbc5014f92e/data-driven-subscription-button-not-displayed?forum=sqlreportingservices
    By the way, have you installed the other SQL Server edition before?
    Best regards,
    Qiuyun Yu
    Qiuyun Yu
    TechNet Community Support

  • No visibility of local SQL Server instance when configuring ODBC data source

    I am setting up an app. requiring ODBC access to a SQL Server DB using a Windows Server 2008 R2 OS on a VM, with a local SQL Server 2014 instance.  When configuring either a new user or system ODBC DSN, using the ODBC Driver 11 for SQL Server
    (version 2014.120.2008.08), the dropdown list of servers is empty.  How do I get it to see the local SQL Server instance?

    For the local default instance, just enter "." or "(local)" for the server name.  For a named instance, the SQL Server Browser service needs to be running to enumerate the named instances automatically but you can still type the
    instance name.
    Dan Guzman, SQL Server MVP, http://www.dbdelta.com

  • Get local sql server data in sharepoint online

    Hi
      Can anyone tell, how to  get local sql server data in SharePoint online.

    Hi Partha,
    Are you taking about local content db to SharePoint Online, if yes then there is not direct way to restore your local content db to online instead if you have small data then you can save your site as a template including content and the upload that template
    and create site on online using that template.
    Below mentioned link might also help:
    http://www.dos2web.com/Cloud/index.php/introducing-sharepoint-in-the-cloud/migrating-from-on-premises-to-sharepoint-online
    If want to display data from any SQL database into your online site, please follow the below link
    http://community.office365.com/en-us/f/148/t/178875.aspx
    https://nhutcmos.wordpress.com/tag/show-sql-data-to-sharepoint/
    Best Regards,
    Brij K

  • Connecting SnapManager to Local SQL server using command line

    Are there any commands (PowerShell preferably) that can be used to connect SnapManager to Local SQL Server and configure it with mostly default configuration? I tried the import-config command using SnapManager for PowerShell, it gives configuration successful import message but does not establish connection to SQL server. Running the new-backup or clone-database commands after importing gives the message that SQL server is not connected and configured.  

    After more investigation and even more chocolate, we've identified the problem and it's now working. For anyone else who strikes this problem in future, here's something to check/consider/try:
    Even though Squirrel SQL Client was connecting and working ok using the MS JDBC driver (v 3.0), it recorded this in its logs:
    Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the INTERSECT operation.
    We've found that the open source jTDS driver does not have the same issue as the Microsoft one.
    We've installed the current jTDS driver, recorded the driver name (net.sourceforge.jtds.jdbc.Driver) and the JDBC URL (jdbc:jtds:sqlserver://<hostname>:1433/<database>) and the connection is now working fine.
    Hope this helps other people...
    Thanks to those of you who offered suggestions and things to check...much appreciated.
    Robyn

  • SQL Server 2012 Management Studio Crashed when opening the application

    Hi,
    I had installed SharePoint 2013 with SQL Server 2012 on a single server environment a couple of months ago. Both the tools were working fine. But today morning i found that when opening SQL Server 2012 Management Studio it displays a pop-up message as attached
    below:
    Event Log:
    Faulting application name: Ssms.exe, version: 2011.110.3000.0, time stamp: 0x5081c1cd
    Faulting module name: Ssms.exe, version: 2011.110.3000.0, time stamp: 0x5081c1cd
    Exception code: 0xc0000005
    Fault offset: 0x00004b89
    Faulting process id: 0x2b0c
    Faulting application start time: 0x01cf54780a2efde8
    Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Ssms.exe
    Faulting module path: C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Ssms.exe
    Report Id: 47e02c36-c06b-11e3-946b-00155d040605
    Faulting package full name: 
    Faulting package-relative application ID: 
    Server Details:
    Windows Server 2012 Standard
    MS SharePoint 2013
    MS SQL Server 2012
    IIS 8.0
    If anyone has faced the same problem or has a workaround, please share!
    Thanks 

    Hello,
    Applying Service Pack 1 for SQL Server 2012 may solve this issue.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Management Studio Crashing When Adding SSIS Step to SQL Agent Job

    Hi
    I am running Windows Server 2012, SQL Server 2012 SP2 CU2, SQL Server Management Studio 2012 and Visual Studio 2012.
    I have existing SQL Agent Jobs that run SSIS packages and they all currently work. However, if I try to edit them or add a new job that uses a SSIS package Management Studio will crash.  I was having this problem a couple weeks ago when I was still
    on SQL Server 2012 SP1 CU9, so I updated to SQL Server 2012 SP2 CU2 and the problem went away for a couple weeks and I was able to add new SQL Agent jobs that run SSIS packages.  But now it issue is back and there are no new updates to try and fix it.
    Has anyone seen this before and found a reliable fix to it?
    Steps to cause crash:
    1) Open new SQL Agent Job
    2) Select Steps and add a New Step
    4) Change the job type to SQL Server Integration Services Package.
    5) SSMS Crashes
    Error Message Below:
    ===================================
    The type initializer for '<Module>' threw an exception. (SqlManagerUI)
    Program Location:
       at Microsoft.SqlServer.Management.SqlManagerUI.DTSJobSubSystemDefinition.Microsoft.SqlServer.Management.SqlManagerUI.IJobStepPropertiesControl.Load(JobStepData data)
       at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.UpdateJobStep()
       at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.typeList_SelectedIndexChanged(Object sender, EventArgs e)
       at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
       at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
       at System.Windows.Forms.ComboBox.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
       at System.Windows.Forms.UnsafeNativeMethods.SendMessage(HandleRef hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
       at System.Windows.Forms.Control.SendMessage(Int32 msg, IntPtr wparam, IntPtr lparam)
       at System.Windows.Forms.Control.ReflectMessageInternal(IntPtr hWnd, Message& m)
       at System.Windows.Forms.Control.WmCommand(Message& m)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
       at System.Windows.Forms.ContainerControl.WndProc(Message& m)
       at System.Windows.Forms.UserControl.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
       at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
       at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
       at System.Windows.Forms.Control.DefWndProc(Message& m)
       at System.Windows.Forms.Control.WmCommand(Message& m)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ComboBox.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
       at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
       at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
       at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
       at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
       at System.Windows.Forms.Application.RunDialog(Form form)
       at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
       at System.Windows.Forms.Form.ShowDialog()
       at Microsoft.SqlServer.Management.SqlManagerUI.JobSteps.newJobStep_Click(Object sender, EventArgs e)
       at System.Windows.Forms.Control.OnClick(EventArgs e)
       at System.Windows.Forms.Button.OnClick(EventArgs e)
       at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
       at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ButtonBase.WndProc(Message& m)
       at System.Windows.Forms.Button.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
       at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
       at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
       at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
       at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
       at System.Windows.Forms.Application.RunDialog(Form form)
       at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
       at System.Windows.Forms.Form.ShowDialog()
       at Microsoft.SqlServer.Management.SqlMgmt.RunningFormsTable.RunningFormsTableImpl.ThreadStarter.StartThread()
    ===================================
    The C++ module failed to load.
     (DTEParseMgd)
    Program Location:
       at <CrtImplementationDetails>.LanguageSupport.Initialize(LanguageSupport* )
       at .cctor()
    ===================================
    Index was outside the bounds of the array. (DTEParseMgd)
    Program Location:
       at _getFiberPtrId()
       at <CrtImplementationDetails>.LanguageSupport._Initialize(LanguageSupport* )
       at <CrtImplementationDetails>.LanguageSupport.Initialize(LanguageSupport* )
    Thanks,
    Anthony

    I ended up being able to work around this without having to recreate everything on a Windows Server 2008 R2. I did this by setting up an azure point to site VPN from
    my computer to the Windows Server 2012 hosted on azure.  I was then able to connect SSMS from my computer to the Azure VM allowing me to create and edit new SQL Agent jobs that run SSIS packages. Here are the steps to do this
    1) Connect to the VPN from another machine besides the server.
    2) Open SSMS using the runas.exe command with the Domain\User Name of a Windows account on the server.
    - Ex. Runas.exe /netonly /user:DOMAIN\USER "C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Ssms.exe"
    2) Connect to the VM's Database Engine using its internal IP address and the port that SQL Server is listening on (default is 1433) and a SQL Login
    setup on the server.
    -Ex IP, 10.0.0.1,1433
    3) Create a new job with the type SQL Server Integration
    Services Package. Select the package source (SSIS Catalog). I could not get the server to be automatically discovered here so enter the server’s internal IP address and select the package you want to run.
    4) Right click the new SQL Agent Job and choose Script Job As, CREATE To, New Query Window. This is the script to create the
    SQL Agent Job and it needs to be edited to contain the Name of the server on the internal IP address that was used earlier.
    5) Edit the @command= line of the script to use the server name. Change the highlighted part below to the server name.
    - Ex . @command=N'/ISSERVER "\"\SSISDB\PACKAGELOCATION\"" /SERVER
    "\"10.0.0.1\"" /Par "\"$ServerOption::LOGGING_LEVEL(Int16)\"";1 /Par "\"$ServerOption::SYNCHRONIZED(Boolean)\"";True /CALLERINFO SQLAGENT /REPORTING E',
                - Change to this
                            - @command=N'/ISSERVER "\"\SSISDB\PACKAGELOCATION\""
    /SERVER SERVERNAME /Par "\"$ServerOption::LOGGING_LEVEL(Int16)\"";1 /Par "\"$ServerOption::SYNCHRONIZED(Boolean)\"";True /CALLERINFO SQLAGENT /REPORTING E',
    6) Now change the name of the package in the script and run it. Now the new package can be edited in the GUI to change things like the schedule and alerts. Also you
    can edit any existing packages.

  • SQL Management Studio crashes with DataTools installed

    This error seems to be very random but once it occurs I can no longer connect to a server in SQL Server Management Studio.   It was happening in Management Studio 2012 as well:
    I have Visual Studio Premium 2013 with Update 3 installed.
    SQL Server Data Tools for Visual Studio 2013 
    SQL Server Management Studio 2014
    I can't verify this but it seems to happen after Windows Updates have been applied.   I have to restart my computer in order to connect to a server again.
    Application: devenv.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.TypeInitializationException
    Stack:
       at Microsoft.SqlServer.Management.SqlParser.MetadataProvider.MetadataProviderBase..ctor(Microsoft.SqlServer.Management.SqlParser.MetadataProvider.IBuiltInFunctionLookup, Microsoft.SqlServer.Management.SqlParser.MetadataProvider.ICollationLookup,
    Microsoft.SqlServer.Management.SqlParser.MetadataProvider.ISystemDataTypeLookup, Microsoft.SqlServer.Management.SqlParser.MetadataProvider.IMetadataFactory)
       at Microsoft.Data.Tools.Schema.MetadataProvider.Features.ProjectMetadataInfo.AsyncCreateMetadataProvider()
       at Microsoft.Data.Tools.Schema.MetadataProvider.Features.ProjectMetadataInfo+<>c__DisplayClass3.<BeginAsyncMetadataCreation>b__2()
       at Microsoft.VisualStudio.Data.Tools.SqlEditor.DataModel.BaseMetadataProviderProvider+BinderQueueImpl.ProcessJobs()
       at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr, System.Object[], System.Object, System.Object[] ByRef)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessageSink)
       at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBack(System.Object)
       at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
       at System.Threading.ThreadPoolWorkQueue.Dispatch()
       at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

    Hi ScottWeeden,
    The SQL Server Data Tools for SQL Server 2014 is available, and this update is available for Visual Studio 2012 and 2013. According to your description, when you installed SQL Server Data Tools for Visual Studio 2013, the SQL Server Management Studio 2014
    crashes. In theory , this version of SQL Server Data Tools  is fully compatible with SQL Server 2014. Personally, I recommend you install the latest cumulative update or service pack for SQL Server 2014/2012, and install the latest cumulative
    update for VS 2013. For more information, see:
    http://blogs.msdn.com/b/ssdt/archive/2014/03/25/sql-server-data-tools-for-sql-server-2014-is-available.aspx 
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Authentication on local SQL Server 2008 R2 Express server fails after Lan Manager authentication level changed to "Send NTLMv2 response only\refuse LM & NTLM"

    I'm upgrading my organisation's Active Directory environment and I've created a replica of our environment in a test lab.
    One medium-priority application uses a SQL server express installation on the same server that the application itself sits on.
    The application itself recently broke after I changed the following setting in group policy:
    "Send LM & NTLM - use NTLMv2 session security if negotiated"
    to
    "Send NTLMv2 response only\refuse LM & NTLM"
    The main intent was to determine which applications will break if any - I was very surprised when troubleshooting this particular application to find that the issue was actually with SQL Server express itself.
    The errors I get are as follows (note that there are hundreds of them, all the same two):
    Log Name:      Application
     Source:        MSSQL$SQLEXPRESS
     Date:          1/19/2015 2:53:28 PM
     Event ID:      18452
     Task Category: Logon
     Level:         Information
     Keywords:      Classic,Audit Failure
     User:          N/A
     Computer:      APP1.test.dev
     Description:
     Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: 127.0.0.1]
     Event Xml:
     <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
       <System>
         <Provider Name="MSSQL$SQLEXPRESS" />
         <EventID Qualifiers="49152">18452</EventID>
         <Level>0</Level>
         <Task>4</Task>
         <Keywords>0x90000000000000</Keywords>
         <TimeCreated SystemTime="2015-01-19T22:53:28.000000000Z" />
         <EventRecordID>37088</EventRecordID>
         <Channel>Application</Channel>
         <Computer>APP1.test.dev</Computer>
         <Security />
       </System>
       <EventData>
         <Data> [CLIENT: 127.0.0.1]</Data>
         <Binary>144800000E00000017000000570053004C004400430054004D00540052004D0053005C00530051004C0045005800500052004500530053000000070000006D00610073007400650072000000</Binary>
       </EventData>
     </Event>
    Log Name:      Application
     Source:        MSSQL$SQLEXPRESS
     Date:          1/19/2015 2:53:29 PM
     Event ID:      17806
     Task Category: Logon
     Level:         Error
     Keywords:      Classic
     User:          N/A
     Computer:      APP1.test.dev
     Description:
     SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure.  [CLIENT:
    127.0.0.1].
    Event Xml:
     <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
       <System>
         <Provider Name="MSSQL$SQLEXPRESS" />
         <EventID Qualifiers="49152">17806</EventID>
         <Level>2</Level>
         <Task>4</Task>
         <Keywords>0x80000000000000</Keywords>
         <TimeCreated SystemTime="2015-01-19T22:53:29.000000000Z" />
         <EventRecordID>37089</EventRecordID>
         <Channel>Application</Channel>
         <Computer>APP1.test.dev</Computer>
         <Security />
       </System>
       <EventData>
         <Data>8009030c</Data>
         <Data>14</Data>
         <Data>AcceptSecurityContext failed. The Windows error code indicates the cause of failure.</Data>
         <Data> [CLIENT: 127.0.0.1]</Data>
         <Binary>8E4500001400000017000000570053004C004400430054004D00540052004D0053005C00530051004C004500580050005200450053005300000000000000</Binary>
       </EventData>
     </Event>
    All of the documentation that I have followed suggests that the errors are caused by incorrect SPN configuration- I figured that they were never correct and it has always failed over to NTLM in the test environment (I can't look at production - we couldn't
    replicate the setup due to special hardware and also RAM considerations), but only NTLMv2 has issues.
    So I spent some time troubleshooting this.  We have a 2003 forest/domain functional level, so our service accounts can't automatically register the SPN.  I delegated the write/read service principle name ACEs in Active Directory.  SQL Server
    confirms that it is able to register the SPN.
    So next I researched more into what is needed for Kerberos to work, and it seems that Kerberos is not used when authenticating with a resource on the same computer:
    http://msdn.microsoft.com/en-us/library/ms191153.aspx
    In any scenario that the correct username is supplied, "Local connections use NTLM, remote connections use Kerberos".  So the above errors are not Kerberos (since it is a local connection it will use NTLM).  It makes sense I guess - since
    it worked in the past when LM/NTLM were allowed, I don't see how changing the Lan Manager settings would affect Kerberos.
    So I guess my question is:
    What can I do to fix this? It looks like the SQL server is misconfigured for NTLMv2 (I really doubt it's a problem with the protocol itself...).  I have reset the SQL service or the server a number of times.  Also - all of my other SQL applications
    in the environment work.  This specific case where the application is authenticating to a local SQL installation is where I get the failure - works with LAN Manager authentication set to "Send LM & NTLM - use NTLMv2 session security if negotiated",
    but not "Send NTLMv2 response only\refuse LM & NTLM".
    Note also - this behaviour is identical whether I set the Lan Manager authentication level at the domain or domain controller level in Active Directory - I did initially figure I had set up some kind of mismatch where neither would agree on the authentication
    protocol to use but this isn't the case.

    Maybe your application doesn't support "Send NTLMv2 response only. Refuse LM & NTLM".
    https://support.software.dell.com/zh-cn/foglight/kb/133971

  • Set SPN for a local SQL Server 2008 R2 Express database used for local "Offline Mode" application

    Hi - I have tried searching the web for tips on this situation. Basically, I am trying to recreate a previous employee's client Image. This image is used for one of our companies client application that features and "Offline Mode" where it connects
    (Using Kerberos) to the local DB instead of the central DB server.
    The custom image connects without issue. I cannot seem to recreate his configuration. I am sure of these things:
    - Both images are using the same SQL Server 2008 R2 Express version.
    - Both images have the same user accounts setup.
    - Both images have "Remote Connections" setup with TCP/IP enabled in the Configuration Manager.
    - Both images are joined to the same Domain server currently.
    - Both images has the SQLServer service set to use "NETWORK SERVICE" account.
    This is the error message I get when SQL starts up for the non-working image:
    The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, 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.
    Thank you for any assistance given.

    Hi Gribbled,
    Could you please change the SQL Server Service to run under 'LocalSystem' account and restart SQL Server? Then check if the error still occurs. When the SQL Server service account is configured to use the LocalSystem account, the server will automatically
    publish the SPN.
    Alternatively, to work around this issue, you can manually create the SPN for the SQL Server Service account  using the SETSPN tool. For more details, please review this
    blog.
    Thanks,
    Lydia Zhang

  • Connecting to a local SQL server .mdf file

    Hi all,
    In doing some prototyping of my database I started working with a local copy of an SQL Server database since it so conveniently integrated with the Visual Studio .NET tools I use. Now that I have spent far too much time working on a local prototype, I would very much like to migrate it to our in-house database rather than rewrite the whole thing (it is quite large in terms of tables and constraints and none of our in-house tools generate code from ER diagrams).
    Seeing that SQL Developer had a migration utility I pounced at a chance to use it. I installed it as well as the recommended JDBC driver; however, it occurs to me that I have no idea how to connect to a local database file using the host name and port fields given to me. Is there some convenient way to configure SQL Server 2005 to forward this file to some kind of local host? Or is there any other driver for use with a local .mdf file? Help would be greatly appreciated.

    While it does come with a copy of SQL Server with it, visual studio suspiciously just asks for a file name, so I would assume it reads directly from the .mdf
    I have a copy of SQL Server 05 on the machine, but I haven't done anything in the way of server side configuration before, so I can't even guess how to direct it to serve the file.
    All software packages involved are:
    Windows XP
    SQL Server 2005
    Visual Studio .NET 2005
    SQL Developer 1.5.1
    Oracle client 10g connecting to an Oracle 9i release 2 server
    Any pointers to the right direction or alternate migration solutions would be great.
    Edit: I am highly suspicious that Visual Studio was connecting to this file through SQL Server Express and not my standard edition copy, and it is therefore not attached to the database, the solution is not looking entirely easy, so an alternate migration may be a better choice. Thanks in advance for any help.
    Edit: Well my suspicions were confirmed. I attempted several solutions. First of which being the MS SQL Express publishing wizard so that I could publish to SQL and run the script via Toad or SQL Plus; however, it only targets MS SQL Server 2000 or 2005 which would result in a lot of hand editing in terms of migration. Attempting to find a script converter did not help as they all either failed outright or demanded a connection to the datbase via ODBC or JDBC (which doesn't support SQL Express' less than clever attach on connection ideas). This led me to the alternate solution of trying to attach the file to my main database and connect to it; however, the SQL Server command prompt has some sort of permissions issue with my office security setting (though I can edit files fine) and results in failure.
    I think it is about time to throw in the towel and just work it out by hand. This would be greatly expedited by any visual database tools that generate code from ER diagrams if you happen to know of a freeware solution. We lack an internal copy of Oracle Designer and the free license only permits a single prototype. So any suggestions on the front of freebie visual object relational tools and alternate migration ideas would be of great help. Until then I'll be grinding through it with moderate dissatisfaction.
    Thanks again.

  • I need to add a new report to the application that is done using visual studio and SSRS and SQL Server 2008

    I have an application that is done using SSRS on visual studio and it connects to the report server on SQL server 2008 environment.
    I've been changing the existing reports using visual studio 2008 and modifying the reports on the report server. How do I add a new report to the application ? I created a new report and deployed it on the report server but it didn't show up in the application.
    I can access the application source code on visual studio 2010 and TFS (Team Foundation). Thanks. 

    Hi,
    I have a question. This application retrieves SSRS reports from the report sever. When I download the reports
    from the SQL Server I can open them in visual studio 2008 but they don't open in visual studio 2010. I can access the application files on visual studio 2010 and team foundation server 2010. I was unable to open team foundation server 2008 on visual studio
    2008. The issue is that I am unable to add a report with a new name to the application. I use visual studio 2008 to deploy the reports on the report server but it has to be the same name to be able to run the report from the application. I can deploy any report
    on the report server but I can't access it from the application unless it has to be the same name as the present reports. If I keep the report the same name then it will replace the old report and the new report will run from the application. But only if it's
     the same name. I guess when I add a new report to the application with a new name I am supposed to add a definition in the application C sharp files  on visual studio 2010 so that the new report will show in the application. What's your opinion
    ? I have attached 2 images of the application and team foundation server 2010 and the report server.
    Thanks. 

  • CFMX7 and Local SQL Server Connections

    I recently upgraded from CF5 to CFMX7. All went well, but I
    am now not able to access SQL Server DBs on the local Machine.
    When I Verify the Datasource via CF Admin, I am getting the
    following error.
    Connection verification failed for data source: lo_db_laptop
    java.sql.SQLException: [Macromedia][SQLServer JDBC
    Driver]Error establishing socket. Connection refused: connect
    The root cause was that: java.sql.SQLException:
    [Macromedia][SQLServer JDBC Driver]Error establishing socket.
    Connection refused: connect
    These Datasources were working fine in CF5, and have not been
    changed since migration.
    Has anyone experienced similar issues? Any suggestions as to
    what may be causing this?
    Many Thanks in advance

    Hi dimaint, thanks for your reply.
    The datasources are created via ODBC Administrator as a
    System DSN. They are working fine via ODBC Data Source
    Administrator. And they were fine via CF5 before upgrading to MX7.
    This is the case for Datasources that existed prior to
    upgrade, as well as any created post upgrade.
    I'm not specifying the username and password when creating or
    connecting to the Data Sources. Datasources are configured with
    Windows Authentication.
    Thanks again

Maybe you are looking for