The database [name] is not accessible. (ObjectExplorer) After company changed server - sql-server

My company had a new server installed and now I can not access databases. This is the error message:
The database NewDatabase is not accessible. (ObjectExplorer)
and this is what it says under program location:
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.DatabaseNavigableItem.get_CanGetChildren()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItem.RequestChildren(IGetChildrenRequest request)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ExplorerHierarchyNode.BuildChildren(WaitHandle quitEvent)
I have already tried this solution
https://learn.microsoft.com/en-us/previous-versions/sql/sql-server-2012/dd207004(v=sql.110)?redirectedfrom=MSDN
but the step by step solution cant be followed because in step 2 under the server there is no SQL Server Configuration Manager option.
Is there another way to fix it?

Related

Failed to parse XML blob

I'm having problems authenticating against dbs on azure. All the details are right but when I click connect I get the following error:
TITLE: Microsoft SQL Server Management Studio
------------------------------
Error connecting to 'tcp:xyz.database.windows.net,1433'.
------------------------------
ADDITIONAL INFORMATION:
Failed to connect to server tcp:xyz.database.windows.net,1433. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
One or more errors occurred. (mscorlib)
------------------------------
One or more errors occurred. (mscorlib)
------------------------------
Failed to parse XML blob.
Reason: XML document must have a top level element.
Line: 0, Position: 0
Text: (null) (System.Data)
I already uninstalled everything related to SQL and SQL Management Studio and still no luck. I tried connecting with my account in other machine and works, so it seems is something on my machine.
Any suggestions?
UPDATE:
I tested another user on my machine and does work, so it must be something with my user on my machine!
Leaving this here as this SO article is the top result for "SSMS Failed to parse xml blob".
I got this error when I was capturing traffic with Fiddler 4 AND running SSMS at the same time. If you are running Fiddler 4, please close it and try again!
today I experienced the same error message and did a lot of trouble shooting. It turned out to be such a simple fix - my PC requires me to use the new password to log in after I changed it two weeks ago (it says the old password was expired). After I re-logged in, connected to VPN, then I got access back!
Ok after multiple attempts to sort this out, I finally got it fixed.
Follows the steps that worked for me:
Uninstall SQL and SQL Managment Studio
Delete SQL folders from Program Files
Open "regedit" and delete following entries:
HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server 2012 Redist
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server 2017 Redist
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server Native Client 11.0
Install CCleaner and run registry clean
Restart PC
Install SQL Managment Studio
I was facing this tonight. The connection worked while I was at the office but was failing when connected via the work VPN. I thought I'd have to go into the office. One of my teammates suggested I check and make sure my IP connectivity, and especially DNS, was set to automatic.
I disconnected from the VPN
Set IP & DNS to Automatic
Reconnected VPN
Connected to Azure SQL via SSMS successfully
I hope this helps someone else.

Why can't I connect to my local SQL Server database instance?

I installed SQL Server 2008 (not express) on my PC, but when tried to connect with SSMS, got this message:
A network-related or instance specific error occured while established
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: Named
Pipes Provider, error: 40- Could not open a connection to SQL Server)
(Misrosoft SQL Server, Error 2)
My connection dialog box to SSMS is:
Server type: Database Engine.
Server name: (local)
Authentication: Windows
What should I check? Where to start troubleshooting?
GO TO >> Run Command (Ctrl + r )
Type -- services.msc
go to SQL SERVER >> Right Click >> Click Start
Again Restart SQL SERVER Studio
Here are some troubleshooting tips that you can do:
Try to run your SSMS as admin
Make sure that you are using the correct server name and instance
Check if your sql server service is running by going to run -> services.msc -> Check SQL Server(Instance Name) service if it is running
Error 40 has many reasons, some of them are related to network configurations which are out of scope in your question. Other reasons which may cause this error and has possibility in your question are as follow:
Make sure that SQL SERVER(XXX) service is running by visiting sql server configuration manager section
Make sure that SQL Browser service is running by visiting sql server configuration manager section
Make sure you are using the correct instance name
Read more about this error
If your server is Local. Try to login with server name . or (local).
If you are still not able to login, check Check SQL Server Configuration Manager (Start>All Programs>MS SQL Server>Configuration Tools>Configuration Manager)

SQLSERVER 2008 Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection

I am using SQL SERVER 2008 R2 and I have a job which runs a DTS daily. When I try to execute the DTS package it works but when I try to use the scheduled job it returns the error:
Error:
-2147467259 (80004005); Provider Error: 18452 (4814) Error string: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0. Process Exit Code 1. The step failed.
How can I solve that?
Follow the below steps:
1. Start > Programs > Microsoft SQL Server 2008 > SQL Server Management Studio.
2. In the Object Explorer, right-click the Server and select Properties.
3. In the Server Properties dialog box select the Security page.
4. Under Server authentication, select SQL Server and Windows Authentication Mode.
Then restart the server.
For further reference check this.
I stumbled across this issue and spent lot of time.
Finally found the issue is not in any user settings but my publish settings are overriding my connection string.
In web deploy settings there is an option to override your web.config connection string. Either untick that option or place the correct connection string.
For more details see this post https://dba.stackexchange.com/a/141243
I am placing this answer in case anyone gets stuck like me. :)

SQL Server Express 2012 Error: Cannot connect to Local DB

I have installed Sql Express 2012 version. I installed Local Db separately. i can see its installed when I click on "Installed Sql Server discovery report". However, I cannot connect to it using Sql Server Management Studio or Microsoft Visual Studio 2012 Professional Edition. I get the error:
"The attempt to attach to the database failed with the following
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: 50 - Local Database Runtime
error occurred. Cannot create an automatic instance. See the Windows
Application event log for error details."
In Windows Event viewer I see several of following errors with different regsistry keys each time:
"The DataDirectory registry value is missing in the LocalDb instance registry key:{-----}"
I checked in regsitry values for local db in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MicrosoftSQL Server Local DB and there's only one entry "Installed Version".
I have gone through several posts which state solution for the above error and have done almost everything they have suggested but still can't get localDb to work.
I'd appreciate any help that one can provide in order to solve this issue.
UPDATE:
Using Command Line Interface I verified that localDb v11.0 is installed. However, the command sqlLocalDb info v11.0 gives error:"The automatic instance "v11.0" is not created. If I try to create one it gives another error:"Unexpected error occured inside a localDb instance API method call."
You may try to use SQL Server Authentication. Also make sure that your SQL service is running.
Also you may try to delete the following registry:
HKEY_USERS\.DEFAULT\Software\Microsoft\Microsoft SQL Server\UserInstances\[GUID_FROM_EVENT_LOG]
You may also check Getting Started with SQL Server 2012 Express LocalDB
You need to start the SQL service for the local system.
Start Button
Write "SQL Server Configuration Manager" and click on it
After opening "SQL Server Configuration Manager" you need to start the local system services which are may be stopped in it that why your local Database not connected.
After starting local services you just connect the local system database. It should connected successfully.

SQL Server Replication connection error

After I renamed my PC, I couldn't create new paublications, for database replication in SQL Server 2005.
I receive un error "SQL Server replication requires the actual server name to make connection to the server."
When I returned my old PC name, the problem solved. How could I make use of replication after renaming the PC?
The SQL Service itself still thinks it has the old server name, and since it has the habit of referring to itself in the third person, this causes problems when the underlying server name has changed. You need to take the following steps to correct it:
Run "Select ##ServerName" to verify the servername - it should be the old name.
sp_dropserver ‘OLDSERVERNAME’
sp_addserver ‘NEWSERVERNAME’, local
Restart both the SQL Service and the Agent Service
Run step 1 again to confirm that the server name is now correct

Resources