We have a variety of SSIS solutions which we develop and test in Visual Studio 2019. We recently got a new development server installed (SQL 2016)
When we open a solution we now need to go through a process of testing the project connections before opening a package as otherwise the connections from the package show as offline.
The main problem is that although the 'test connection' works to our SQL server databases, packages will not run against the new development server. We just get an error
'[Execute SQL Task] Error: Failed to acquire connection "PKD-SQL-DEVDW_DW.AGIDU". Connection may not be configured correctly or you may not have the right permissions on this connection.'
Looking at the SQL profiler the test connects by doing a login using our windows login but when running a package there is nothing reaching the server - i.e. nothing showing any connection to the server at all.
We can run a package against the new development server if we call it from a SQL agent job, and we can run successfully against the live server.
Is there some configuration of our new development server/instance that needs tweaking to allow Visual Studio packages to connect. We are stumped by this problem. Any help/advice much appreciated
Thanks
Phil
The other week I installed the latest version of SQL Server and Management Studio. In the Server Name box was a long name made up of some path and other parts however it has now disappeared and reading all these answers has not helped. I downloaded two backups of databases from a live server and restored them down here. I could access them and everything was fine until the server name disappeared and I have no idea (none of the ones on here work) how to get it back.
If I try localhost, 127.1.1.0 or . as the server name it doesn't work the error I get is:
A network or instance-specific occurred whilst establishing connection to SQL Server....Provider: Named Pipes Provider, error 40- could not open connection to SQL Server
If I go into services I only have SQL Server Browser and SQL Server VSS Writer. Under Browser it is disabled. If I start it or tell it to start on delayed or manual or just start it, it starts okay and then two seconds later its stopped again with no error message.
If I got to CMD and type (under) I get (under that)
C:\Windows\system32>SQLCMD -L
Servers:
;UID:Login ID=?;PWD:Password=?;Trusted_Connection:Use Integrated Security=?;
*APP:AppName=?;*WSID:WorkStation ID=?;
No list of servers which another answer suggested.
I cannot find under services a MS SQL Service for some reason.
Everything was working fine the last time I came to do some work on this so I don't know if some virus was detected that removed the service or something.
I had two databases to connect to and run queries against and try to get a Windows Service working again locally but I can't get the DB to work.
I am on Windows 8.1 64bit laptop with enough diskspace.
If I go to C:\Program Files\Microsoft SQL Server\110\LocalDB\Binn and double click sqlservr.exe, I get the error
Your SQL Server Installation is either corrupt or has been tampered with (Error getting Instance ID from name) Please uninstall then re-run setup to correct this problem.
Is it a case of me having to uninstall Management Studio and restarting again? I don't know what could have corrupted it but I need it working.
Should I just use the SQL Server 2017 Configuration Server to see if that can fix it or do I need to delete whole directories or "uninstall" from "programs and features" and try to install it again?
Still have no scooby to why the server name disappeared in the first place. Anyone got a clue?
SQL Server should appear in Services (you should not start it by double-clicking sqlservr.exe). If it doesn't appear anymore, you should reinstall SQL Server. After that you may attach the MDF and LDF files of your user databases, if they are still available (but in your case, you can also restore the backups again).
It seems your SQL server is not installed properly or corrupted now.
If the SQL Server installs on any machine there is a service named 'Sql Server(MSSQLSERVER)' or similar must be there and in 'Running' mode to connect to the database.
I installed VS2013, VS2010 Shell (for the BI-Tools) and SQL Server 2012 on Windows 8.1 Pro. I configured the SQL Server and attached the AdventureWork2012 database successfully.
I created datasource > dataview > cube from the db above.
However, I got an error saying
"The project could not be deployed to the 'XX\DBT2' server because of
the following connectivity problems: A connection cannot be made to
redirector. Ensure that 'SQL Browser' service is running. TO verify or
update the name of the target server..."
I've checked the SQL Server and SQL Server Browser and both are running. (checked from SQL Server Configuration Manger)
I also checked the db connection I set up on the VB project. It said Test connection succeeded.
I think I missing some user permission thing but not sure which one is it so here is a little more info about the user right. The user I am using is the account that setup with the windows installation. I also followed some other article online that they said added a few more admin right (user, group) will solve this issue which it didn't for this case.
I also go into the SQL Server Management Studio and check the database permission. And the user right as well but I can't seem to find any problem.
So I've been doing a project at my university with BIDS and a database on their servers. I've managed to back up the database and put it on my local machine.
Problem right now is I've installed SQL Server 2008 + BIDS through SQL Server 2008 Express Edition. Now I've heard it doesn't include SQL Server Analysis Service, meaning I can't deploy the cube.
I've tried deploying the project on my home computer but it gives me the error.
Error 23 The project could not be deployed to the 'my computer
name\SQLEXPRESS' server because of the following connectivity problems :
A connection cannot be made to redirector. Ensure that 'SQL Browser' service
is running. To verify or update the name of the target server, right-click on
the project in Solution Explorer, select Project Properties, click on the
Deployment tab, and then enter the name of the server.
I've checked and SQL browser service is definitely running so I'm not sure what else to try. Is there any way for me to successfully deploy the cube?
I think its authentication issue for your current user connecting to SQLEXPRESS. Try using "Runas /user:[domain]\[user] "Path to BIDS" to run BIDS as privileged user and try windows authentication.
I am working with SQL Server 2008 R2. I am unable to connect to my database remotely. I got the following error.
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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I have checked the SQL Server properties and I enable the Allow remote connections.
I have checked the Service manager and SQL Server service are running.
I have checked the configuration manager, I can't see any services under SQL Server Services
and it shows Remote Procedure call failed
So please guide me.
Open Control Panel > Administrative Tools > Services > Select Standard services tab (under the bottom) > Find start SQL Server Agent
Right Click and select properties,
Startup Type : Automatic,
Apply, Ok.
Done.
I just had the same issue and was able to solve it by installing Service Pack 1.
This error occurs only after I have installed the Microsoft Visual Studio 2012 setup in my work machine.
Since it is being a WMI error, I recompiled the MOF file –> mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"
I also un-registered and re-registered the sql provider DLL –> regsvr32 "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmprovider.dll" but issue not resolved.
Solution:
I have applied SQL Server 2008 R2 SP2 on my SQL 2008 R2 instance and that fixed the issue with Sql Server Configuration Manager. You can download setup from here... http://www.microsoft.com/en-us/download/details.aspx?id=30437 .
After trying everything between Stackoverflow and Google, I finally found a solution : http://blogs.lessthandot.com/index.php/datamgmt/dbadmin/remote-procedure-call-failed/
TL;DR :
If you are (or were) running multiple versions of SQL Server on your machine, that Configuration Manager shortcut on your start menu might be pointing to an older version, which it shouldn't be. It was pointing to an old Sql Server 2008 instance in my case.
The solution was to :
Go to either C:\Windows\SysWOW64 or C:\Windows\System32, depending on your system.
Look for an executable called SQLServerManagerXX.msc, and run the latest version if you have multiple ones. In my case, I had both SQLServerManager11.msc and SQLServerManager10.msc, where the 10th gave the error, and the 11th worked perfectly.
I can't comment yet, but make sure you made all the checks in this quide: How to enable remote connections in SQL Server 2008? It should work fine if all steps are made.
Upgrade your SQL Server to SP3
You can install it from:
http://www.microsoft.com/en-us/download/details.aspx?id=27594
This error appears to happen when .mof files (Managed Object Format (MOF)) don’t get installed and registered correctly during set-up. To resolve this issue, I executed the following mofcomp command in command prompt to re-register the *.mof files:
mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"
This one worked for me
start SQL Server Agent from the command prompt using:
SQLAGENT90 -C -V>C:\SQLAGENT.OUT
You might need to install SQL Server 2008 SP3.
SQL Server 2008 Service Pack 3
SQL Server 2012 Configuration Manager WMI Error – Remote Procedure call failed [0x800706be]
I got the samilar issue, while both SQLServer and SQLServerAgent services are running. The error is fixed by a restart of services.
Server Manager > Service >
SQL Server > Stop
SQL Server > Start
SQL Server Agent > Start
Open Control Panel
Administrative Tools
Services
Select Extended services tab
Find SQL Server(MSSQLSERVER) & SQL Server(SQLEXPRESS)
Stop these services and Start again (from the start & stop button displayed above)
Done.