I have a problem. I am trying to local export from excel to .mdf (SQL Server), and I keep getting this error:
[DBNETLIB][ConnectionOpen (Connect()).] SQL Server does not exist or access denied.
I searched different articles, and I tried everything. I installed again my SQL Server, but it still doesn't work. I checked Configuration Manager, but everything looks fine. Does anyane have any idea what else can cause it?
The error explains that you did not specify the right database name, or the right ODBC name, or if you did you did not specify the right user/pwd combination to get access. You would need to get into those details to find the solution.
Did you try to import Excel from MS-SQLserver, which requires no configuration, and has no authorisation limiations (unless hte excel file is encrypted)?
Related
I am trying to generate a report by using SQL Server 2008 R2 File Stream and WCF Service. I am able to generate reports if the service is hosted in the same server which database is located i.e. Database and service is hosted in the same server.
If I hosted the service in different server I am getting the "System.ComponentModel.Win32Exception (0x80004005): The system cannot find the path specified" exception. I have given all the necessary permissions to the SQL FileStream share location like IIS_User, Everyone etc and I am able to access the share path from the new server also. Still getting the same error.
When I am checking EventViewer in server it is throwing, System can not find the specified path
\\Machine_Name\FolderName\v1\DBNAme\dbo\TableName\ColumName\06E9456C-A090-24Ge-9C35-25FDG54FE78RR25
\\Machine_Name\FolderName\ this one is SQL FileStream share path.
Please help me to get out this.
It seems that the issues like this are related to any of the following need to be looked at:
firewall settings from the web server to the database server.
connection string errors.
enable the appropriate protocol pipes/ tcp-ip.
You could refer to the following article to troubleshoot Connecting to the SQL Server Database Engine:
http://social.technet.microsoft.com/wiki/contents/articles/2102.how-to-troubleshoot-connecting-to-the-sql-server-database-engine.aspx
This content comes from this link.
In my opinion, this is likely to be caused by a connection string error, you need to check your connection string.
I am trying to migrate a vb.NET project from an MS Access database to MS SQL Server, and have been following a tutorial I found here to do so. I did this, but got a problem where I could read data from the SQL Server database when running my project, but could not insert/edit data using the project.
Any data I tried to manipulate only worked on the Access database, and didn't have any affect on the SQL Server data (I also tried vice-versa, adding data using SQL Server but this couldn't been seen in my project).
So I decided to try again, deleting the Access and SQL Server databases, and using the backup database to import the data from. However, this now is not working, and I'm getting the following error message
Error 0xc020801c: Source - ~TMPCLP123581 1: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "SourceConnectionOLEDB" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
(SQL Server Import and Export Wizard)
Exception from HRESULT: 0xC020801C (Microsoft.SqlServer.DTSPipelineWrap)
Does anybody know a fix for this? Or why I can no longer import data into SQL Server? (The image below shows the result of what processes were/weren't carried out)
I've fixed the issue now, guys.
I migrated it over using Microsoft SQL Server Migration Assistant for Access, and then changed the connection path and settings in my .ini file.
Then I created a new connection string, using string variables for each of the settings in the .ini file, and this replaced the initial Access database connection string.
I have the following situation:
A sql server 2014 is installed
While the server was shutdown the hard drive the databases were on had troubles which resulted in the loss of these files
So now I have the situation that the server has databases configured to be existing where the files don't exist any longer.
When I now try to start the sql server via the configuration tools it does not start and in the log files I see that he throws an error that he doesn't find the database files. When I tried to copy the same files there from another server I still had the same problem but the error message was now "access denied" (as naturally they had different users).
So my question is: What (aside from a reinstall) can I do to get the sql server up and running again?
Change the database file permissions to allow access for SQL Server. Look at an existing file to see what permissions must be configured.
I am just trying to copy a database from one server to another one... on the same domain. I use the Copy DB Wizard and set up everything correctly but it keeps failing.
Is something wrong with the Wizard or just me missing something?
If you have such a problem it's a good idea to provide information about the settings you made for instance on the priviledges on the remote server.
I would check the following:
Do you have the right permissions to be able to create the database on the other server i.e. dbcreator.
If you're not a sysadmin try to specify a SQL AGent Proxy that has acces to the SSIS execution system.
Make sure no active sessions exist on the database because the wizard will nog execute.
Can you provide an error message?
I have a developer that is having trouble connecting to a SQL Server instance by entering the server name (local)\HIS_SERVER_INSTANCE into Visual Studio->Server Explorer. If he replaces (local) with his machine name, it connects fine. I have had similar issues before but they seemed to fix themselves. Does anyone know a fix for this?
EDIT:
We cannot use the machine name because our app contains connection strings with (local) in them.
Also, I've noticed something weird about his SQL Server install. Everyone else seems to get the SQL Server Service Manager showing in the lower right corner. I looked for this app in his startup folder and nothing was there. I then looked for the app on the system (C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmangr.exe) and it doesn't exist. Maybe his system has bigger issues??
You can use .\HIS_SERVER_INSTANCE to get the same effect as using (local).