Error 7399 Msdasql
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: MSDASQL Linked Server error microsoft sql server error 7399 linked server SQL Server > SQL Server Express Question 0 Sign in to sql server error 7399 access denied vote Hi all, I have created a System DSN to a MYOB database file. I msg 7399 level 16 state 1 line 1 access denied have SQL 2000 and 2005 Express editions installed on the same machine. I am logged in to PC as Local Admin. I am also logged into 2005
Microsoft Sql Server Error 7399 Invalid Authorization Specification
Express using 'sa' to avoid any security problems. Creating a New Linked Server using SQL 2000 works fine using the System DSN I created, however, If I use exactly the same settings (Microsoft OLE DB Provider for ODBC) I get an error message. "The OLE Provider "MSDASQL" for linked server "sname" reported an microsoft sql server error 7303 linked server error. The provider did not give an information about the error." "Cannot initilize the data source object of OLE DB Provider "MSDASQL" for Linked Server "name". (Microsoft SQL Server, Error: 7399)" I have installed SL 2005 Express SP2. As another test I created a data source using the same System DSN in Excel. It worked fine and queries the MYOB database file. Any ideas to assist me?? Thanks. Alan Monday, January 07, 2008 9:56 AM Reply | Quote Answers 0 Sign in to vote HI Refer the below link, this may help you. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=614402&SiteID=1 Monday, January 07, 2008 11:40 AM Reply | Quote Moderator All replies 0 Sign in to vote HI Refer the below link, this may help you. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=614402&SiteID=1 Monday, January 07, 2008 11:40 AM Reply | Quote Moderator 0 Sign in to vote Thank you Vidhya. I re-installed SQL 2005 Express SP2 and created another Instance (just in case). Create a New Linked
Side ScriptingLoginCancel changesDiscard all changes?NoYesClose MessagesTroubleshooting Linked Server18667 viewsNumber:KB0538992 Troubleshooting linked server ProblemThis article guides you through the process of troubleshooting linked server issues. It provides steps to help eliminate common causes for your problems by verifying that the configuration of your networking is correct. SymptomsSymptoms may include: Some properties are not editable during configuration. There are msg 7330, level 16, state 2, line 1 error messages received when running queries. The queries against the linked server
Msg 7303, Level 16, State 1, Line 1
timeout. The user cannot create a linked server. The user cannot query the linked server. The connector timed
Cannot Create An Instance Of Ole Db Provider Msdasql For Linked Server
out when trying to run a scheduled job. ResolutionDetermine whether any of the troubleshooting steps below are true for the environment. The steps provide links to articles that help https://social.msdn.microsoft.com/Forums/sqlserver/en-US/6cb98544-5fec-4885-9d42-13009aa47332/msdasql-linked-server-error?forum=sqlexpress eliminate possible causes and take corrective action as necessary. Verify that MS SQL Server Management Studio is running as an administrator. For more information, see this Microsoft article. When testing the connection, it works properly, but when running queries, this error message is received:Msg 7399, Level 16, State 1, Line 1The OLE DB provider "MSDASQL" for linked server " SERVICENOW" https://hi.service-now.com/kb_view.do?sysparm_article=KB0538992 reported an error. Access denied.Msg 7350, Level 16, State 2, Line 1Cannot get the column information from OLE DB provider "MSDASQL" for linked server "SERVICENOW" Microsoft Data Access Components (MDAC) may not be working properly. For more information, see thisMicrosoft article. When running queries against the linked server, this error message is received:OLE DB provider "MSDASQL" for linked server "SERVICENOW" returned message "[DataDirect][ODBC OpenAccess SDK driver][OpenAccess SDK SQL Engine]java.net.SocketTimeoutException: connect timed out[1001]".Msg 7303, Level 16, State 1, Line 1Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "SERVICENOW"A firewall may be blocking traffic. Verify firewall settings. When trying to query the linked server, this error message is received:OLE DB provider "MSDASQL" for linked server " SERVICENOW" returned message "[DataDirect][ODBC OpenAccess SDK driver][OpenAccess SDK Client]Cannot open the configuration file.".Msg 7303, Level 16, State 1, Line 1Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "`SERVICENOW".The user may not have the privileges to set up the linked server. For more information, see this Microsoft articleor watch this video tutorialon trouble
database SQL Server error 7399 when linking to remote Pervasive SQL v11 database Last post 08-30-2012 2:43 AM by Han Schouten. 10 replies. Page 1 of 1 (11 items) Sort http://cs.pervasive.com/forums/p/14797/51338.aspx Posts: Oldest to newest Newest to oldest Previous Next 08-16-2012 8:52 AM Han Schouten Joined on 04-25-2009 Posts 9 SQL Server error 7399 when linking to remote Pervasive SQL v11 database Reply Contact Until recently, I hada MS SQL Server 2005application running under MS Windows 2003 SBS and Pervasive SQL v10. I have just upgraded to a new server running Microsoft Windows 2008 R2 Server, error 7399 MS SQL Server 2008and Pervasive SQL v11. Queries succeed. The first update in my program gives the following error message: Msg 7399, Level 16, State 1, Line 1The OLE DB provider "MSDASQL" for linked server "sunclasssonnevijver" reported an error. The provider reported an unexpected catastrophic failure. I have played around with the logon properties of the SQL Server Service (Built-in account: Local system and various other sql server error local and domain accounts), without success. Does anybody know a way to get over this barrier? Thanks, Han Schouten 08-16-2012 9:35 AM In reply to Linda84 Joined on 07-10-2007 Posts 768 Re: SQL Server error 7399 when linking to remote Pervasive SQL v11 database Reply Contact Is your Pervasive PSQ v11 a 64-bit engine? Can you try a test using ODBC instead of OLE DB? 08-16-2012 9:40 AM In reply to Mirtheil Joined on 07-09-2007 Posts 4,733 Re: SQL Server error 7399 when linking to remote Pervasive SQL v11 database Reply Contact Can you run the same basic update statement from the PCC? Does it return an error? Just to be clear, the PSQL server engine, MS SQL server engine, and PSQL data files are all on the same machine. Correct? 08-17-2012 3:21 AM In reply to Han Schouten Joined on 04-25-2009 Posts 9 Re: SQL Server error 7399 when linking to remote Pervasive SQL v11 database Reply Contact Thanks for your prompt reaction! Indeed, all MS SQL and PSQL files reside on one 64 bit server, called WIN11. Initially, I have been confused about which ODBC administrator to use: the one in system 32