I have a New default instance of SQL2k5 installed and i am trying to setup access to the this via a vpn.
The VPN is setup and allows access to the server and can T/S to the server and perform everything all ok.
When trying to connect over the VPN with SSMS installed on my laptop I am able to connect using Windows authentication only by using Named Pipes. To accomplish this i perform a Net Use ..... and everything works fine.
However if i specify in the connection tab to use TCP/IP it fails with an unknown username or password. The Event Viewer on the server shows this and for what ever reason the username / pwd is that of my laptop and not of the account used in the VPN setup or the net use.
Also if i try to connect to the SQL Server over the VPN using VS 2005 it also gives the same issue.
I need to get this sorted so that TCP is able to be used.
I am trying to establish a OLEDB connection for a db2 server from SSMS adn some one tell me the settings. I haver tried different options but failed. This is my connection string from SSIS "Data Source=DB2W;User ID=myid;Provider=IBMDADB2.1;Persist Security Info=True;"
I gave Linked Server: DB2W Provider: IBM OLEDB provider for DB2 Product name: ??? DataSource: ??? Provider string:??? Location: ???
One of the instance is hosted in a cluster node with 128GB of ram and 80 processors allocated to this instance...And last week, we had an issue with temp DB as it was full.We increased the drive space over the weekend.
Now whenever we connect this instance from other server through remote SSMS, we see, refreshing the object including connecting to this instance is very very slow...It takes more than 10 sec. Initially this was not the case. Even hear from end user that the application is performing gradually slow.
I check the network, fregmentation, settings across this instance, and all looks good.
I used the selfssl.exe tool to generate a certificate on my db server, successfully added to Personal Certificates in MMC, added R/W permissions for the service account to the cert, selected the new certificate in the protocols for mssql and restarted the service. So far so good, however when trying to connect from SSMS with encryption check box checked I get the following error:
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.) (Microsoft SQL Server, Error: -2146893019)
The certificate chain was issued by an authority that is not trusted.
When I look in MMC, the only intended purpose for the certificate is "Server authentication" and I'm not able to add "Client authentication". Does selfssl.exe not support client authentication?
suddenly I'm getting a connect to server error dialogue box that says...
Cannot connect to serverinstance name Additional information The operation could not be completed. (WinMgmt)
...when trying to connect to RS2005 Server in Management Studio. I can reach Reporting Manager thru IE and run my reports.
Is it possible that my setting IIS to basic authentication (and turning off Windows Integrated) might be preventing me from connecting in MS, perhaps because MS has to go thru the RS service and doesnt know what basic auth is?
I'm temporarily unable to set IIS back to Windows Auth cuz the server is being used by users to test reports.
connecting to a SQL Server Instance. I have a SQL server DB on a server having an Instance not running on the default port. Let's say ServerAInstanceA has the services exposed on Port 12345. When I'm trying to connect to ServerAInstanceA without specifying the port number, while I can connect from one client machine (ClientA), I am unable to connect from a different client machine (ClientB).On a side note, when I provide the port number, I can connect both from clients A and B. My question is, when I do not provide the port number, why is one client machine able to connect while the other isn't?
I have several users with an unusual problem with SSMS 2012. When they attempt to connect to a database using the "Connect to Server" dialog box, the connection just hangs. Sometimes after about 15 minutes the connection will be successful. Other attempts simply spin seemingly endlessly. Users experiencing this issue are both running SSMS 2012 on Win 7 Pro (64 bit). The following troubleshooting steps have been tried:
1. When the user runs SSMS "As Administrator" the connections work almost instantly. (Elevating privileges is not a solution in our environment) 2. Wireshark shows that SSMS does not try to hit the SQL server when the user experiencing this issue clicks connect. 3. I can create a new virgin user on the PC and that login experiences the same problem. 4. A complete rip and re-install of SSMS 2012 does not resolve the issue.
I added a connection (ADO.NET) object by name testCon in the connection manager - I wanted to programmatically supply the connection string. So I used the "Expressions" property of the connection object and set the connectionstring to one DTS variable. The idea is to supply the connection string value to the variable - so that the connection object uses my connection string.
Then I added a "Backup Database Task" to my package with the name BkpTask. Now whenever I try to set the connection property of BkpTask to the testCon connection object, by typing testCon, it automatically gets cleared. I am not able to set the connection value.
Then after spending several hours I found that this is because I have customized the connection string in testCon. If I don't customize the connection string, I am able to enter the "testCon" value in the connection property of the BkpTask.
I installed Visual Studio over a year and a half ago when I became a Microsoft ISV. I have done all of my SQL Server work from within the Visual Studio framework and UI. I recently was asked to document how a customer's users would set up the customer's system using SQL Server 2005, but not having Visual Studio. I got the book Beginning SQL Server 2005 for Developers and immediately ran into a wall. Dewson (the author) talks about the SQL Server Management Studio. He says you get to it by Start > Programs > Microsoft SQL Server 2005 > Sql Server Management Studio. When I tried, I went Start > All Programs > Microsoft SQL Server 2005 > Configuration Tools.
I have reinstalled my SQL Server 2005 Developer's edition and installed SQL Server 2005 Standard edition every way I can see, but I still can't get SSMS to come up. What am I doing wrong?
I am running XP Pro 2002 with SP 2. It is on a thinkpad with P4-M 1.8 ghz and 512 mb RAM. My Add/Remove programs says I have SQL Server 2005, SQL Server 2005 Backward Compatibility, SQL Server Native Client, SQL Server Setup Support Files, and SQL Server VSS Writer installed.
I installed Red Gate's SQL Search and now I have an Add-ins icon. From the Icon I got to a list of tools, one of which is SSC's script library.
When I downloaded it I got this file "SQLScripts.utmcsr&__utmv=-&__utmk=243779397" which did not trigger an installer when clicking on it. How do I add it.
I created a database on a remote server and trying to manage the database using a local SSMS. I am able to see the tables and other objects of the old databases residing on the same remote server, but not the new database. I have created the users similar to the other databases, have the exact same roles as the other databases.Not sure what I am missing here. Any suggestions??
Is there any way to use SQL Server Management Studio to manage a 7.0 database? I have a few old databases still in 7.0 and would really like to manage them through SMSS. Am I out of luck?
Just installed SQL Server 2005 Standard. When I attempt to connect using SSMS it just sits. No error comes up. The log seems to indicate everythings OK. SQLServer and SQLBrowser services are started. Here's the log:
2007-07-07 09:41:23.07 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2007-07-07 09:41:23.07 Server (c) 2005 Microsoft Corporation. 2007-07-07 09:41:23.07 Server All rights reserved. 2007-07-07 09:41:23.07 Server Server process ID is 2412. 2007-07-07 09:41:23.07 Server Authentication mode is WINDOWS-ONLY. 2007-07-07 09:41:23.07 Server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'. 2007-07-07 09:41:23.07 Server This instance of SQL Server last reported using a process ID of 1348 at 7/7/2007 9:35:40 AM (local) 7/7/2007 2:35:40 PM (UTC). This is an informational message only; no user action is required. 2007-07-07 09:41:23.07 Server Registry startup parameters: 2007-07-07 09:41:23.07 Server -d C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf 2007-07-07 09:41:23.07 Server -e C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG 2007-07-07 09:41:23.07 Server -l C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmastlog.ldf 2007-07-07 09:41:23.11 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2007-07-07 09:41:23.11 Server Detected 1 CPUs. This is an informational message; no user action is required. 2007-07-07 09:41:23.34 Server 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. 2007-07-07 09:41:23.36 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required. 2007-07-07 09:41:23.89 Server The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted. If you would like distributed transaction functionality, please start this service. 2007-07-07 09:41:23.89 Server Database mirroring has been enabled on this instance of SQL Server. 2007-07-07 09:41:23.90 spid5s Starting up database 'master'. 2007-07-07 09:41:24.20 spid5s SQL Trace ID 1 was started by login "sa". 2007-07-07 09:41:24.28 spid5s Starting up database 'mssqlsystemresource'. 2007-07-07 09:41:24.31 spid5s The resource database build version is 9.00.3042. This is an informational message only. No user action is required. 2007-07-07 09:41:25.65 Server A self-generated certificate was successfully loaded for encryption. 2007-07-07 09:41:25.67 Server Server local connection provider is ready to accept connection on [ \.pipeSQLLocalMSSQLSERVER ]. 2007-07-07 09:41:25.67 Server Server local connection provider is ready to accept connection on [ \.pipesqlquery ]. 2007-07-07 09:41:25.67 spid9s Starting up database 'model'. 2007-07-07 09:41:25.67 Server Server is listening on [ 127.0.0.1 <ipv4> 1434]. 2007-07-07 09:41:25.67 Server Dedicated admin connection support was established for listening locally on port 1434. 2007-07-07 09:41:25.68 Server SQL Server is now ready for client connections. This is an informational message; no user action is required. 2007-07-07 09:41:25.68 spid5s Server name is 'LAPTOP'. This is an informational message only. No user action is required. 2007-07-07 09:41:25.71 spid12s Starting up database 'msdb'. 2007-07-07 09:41:25.71 spid13s Starting up database 'ReportServer'. 2007-07-07 09:41:25.71 spid14s Starting up database 'ReportServerTempDB'. 2007-07-07 09:41:25.71 spid15s Starting up database 'testx'. 2007-07-07 09:41:27.45 spid9s Clearing tempdb database. 2007-07-07 09:41:28.65 spid9s Starting up database 'tempdb'. 2007-07-07 09:41:28.78 spid5s Recovery is complete. This is an informational message only. No user action is required. 2007-07-07 09:41:28.78 spid12s The Service Broker protocol transport is disabled or not configured. 2007-07-07 09:41:28.78 spid12s The Database Mirroring protocol transport is disabled or not configured. 2007-07-07 09:41:29.25 spid12s Service Broker manager has started. 2007-07-07 09:57:23.54 Server CPU time stamp frequency has changed from 117988 to 200203 ticks per millisecond. The new frequency will be used. 2007-07-07 10:09:23.85 Server CPU time stamp frequency has changed from 200203 to 242307 ticks per millisecond. The new frequency will be used. 2007-07-07 10:20:03.20 spid12s Service Broker manager has shut down. 2007-07-07 10:20:04.25 spid5s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required. 2007-07-07 10:20:04.25 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
I have SQL Server 2005 SP2 (developer edition) installed on my machine along with Visual C# 2005 express and Visual Web Developer 2005 express. I uninstalled the 2005 Visual tools and installed the 2008 versions which in turn installed .Net 3.5.
Now, when I right click on a table and select designer, I get the following error message.
TITLE: Microsoft SQL Server Management Studio ------------------------------ Class does not support aggregation (or class object is remote) (Exception from HRESULT: 0x80040110 (CLASS_E_NOAGGREGATION)) (Microsoft.SqlServer.SqlTools.VSIntegration) ------------------------------ BUTTONS: OK ------------------------------
Similarly, when I right click on the indexes folder under a table so that I can create an index, I get the same message but with more details (details are at the end of this post due to size). My research into this problem indicates that it is a problem with the .Net frameworks and I need to reinstall .Net 2.0. It appears that I would have to uninstall 3.5 to accomplish this.
I imagine that I can uninstall the 2008 Visual tools but I really don't want to go backwards. Does anyone know how I can fix the SS2005 instance or am I just going to have to tolerate the errors until I can get a copy of SS 2008?
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Runtime.InteropServices.COMException (0x80040110): Class does not support aggregation (or class object is remote) (Exception from HRESULT: 0x80040110 (CLASS_E_NOAGGREGATION)) at Microsoft.SqlServer.Management.UI.VSIntegration.ISqlToolsVSHlpFactory.CreateHierarchyWrapper(Guid& clsidInnerHier) at Microsoft.SqlServer.Management.UI.VSIntegration.SqlWorkbenchHierarchy.CreateHierarchyWrapper(Type typeToWrap, ILocalRegistry localReg) at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.ScriptFactory.get_SqlVirtualProject() at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.IndexMenuAccessHandler.Enabled(INodeInformation source) at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ToolsMenuItemBase.UpdateMenuCommandStatus(MenuCommand menuCommand) at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.DefaultMenuHandler.UpdateMenuCommandsStatus(MenuCommand menuCommand) at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.DefaultMenuHandler.GetMenuItems(ArrayList items) at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.DefaultMenuHandler.GetMenuItems() at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ExplorerHierarchyNode.ShowContextMenu(Point windowPos) at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.LazyTreeView.WmContextMenu(Message& m) at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.LazyTreeView.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.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Granted there are nearly 8000 tables in this particular database. What needs to be installed or what bit needs to be flipped so the user can see all tables in SSMS?
I have several views in a database that I need to edit in SSMS 2008.
If I right click on a view, I can select "Design" and do the changes and save. Everything saves ok.
However, I cannot enter comments that way. I have tried View Script As -> ALTER To -> New Query Editor Window but this method creates a new view e.g. SQLQuery1 i.e. I can't save the origial view name.
Is there a way to alter views in code and save them back into the database under their original view name?
I have just installed sql server 2005 enterprise edition. I am totally new to sqlserver. I want to create a database in sql server and access that from my VB.net application. I couldn't find sql server management studio to create a database. can somebody help me with this...
I'm in need of a source control system that integrates with the Management Studio so that every time i want to modify a table, view, procedure etc I have to check it out from the object explorer and then check it back in again. I have used Visual Source Safe before but never with a database...is it fully integrated with SSMS? What can I do to make this work as smoothly as possible?
Is there any other IDE that handles this better than SSMS?
-- Lumbago "Real programmers don't document, if it was hard to write it should be hard to understand"
