Odbc Error 5703
Contents |
and 5703 that show in the DEXSQL.LOG? ★★★★★★★★★★★★★★★ David Musgrave11 August 20093 Share 0 0 If you have looked a DEXSQL.LOG file to see the communication between SQL Server and the
Informatica Sql Server Message 5701 Changed Database Context To
Microsoft Dynamics GP application, you might have noticed messages with errors 5701 and 5703 [microsoft][odbc sql server driver][sql server]changed database context to being reported. See the example below: /*/* Date: 08/10/2009 Time: 20:09:49 SQLSTATE:(01000) Native Err:(5701) stmt(0):*/[Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context
Sqlstate 01000
to ‘master'.*//*/* Date: 08/10/2009 Time: 20:09:49 SQLSTATE:(01000) Native Err:(5703) stmt(0):*/[Microsoft][ODBC SQL Server Driver][SQL Server]Changed language setting to us_english.*//* You mightwonder if these errors signify a problem. Well, you can relax as they are purely informational and can be ignored. The following comes from Microsoft Knowledge Base (KB) article 143339 (link below): SQL Server always issues at least two informational messages on a successful connection from any ODBC or DB-library client: A 5701 message, indicating which database on the server the user has been logged into, and a 5703 message, indicating what language the server is using. Applications can simply ignore these 5701 and 5703 messages, they are purely informational. The default database and language settings are controlled by the Login Properties for the user. From Microsoft SQL Server Management Studio, select the [Server] >> Security >> Logins >> [User], right click and select Properties. In the General page, you will find the Default database and Default language settings. The default database can be overridden using the ODBC (Open DataBase Connectivity) DSN (Data Source Name) setting for Default Database. If a default database is defined at the ODBC level it must be either the DYNAMICS or master database. Using any other database can cause issues, especially if the user does not have access to the database. For more information, please see the following Knowledge Base article: INF: ODBC Messages on SQL Server Connections (KB 143339) David
Tags Application SQL Comments (3) Cancel reply Name * Email * Website Janakiram M.P. says: 12 August 2009 at 08:31 David I always tell my clients' System Administrators to set up ODBC defaulting to DYNAMICS Database only. Reply David Musgrave says: 12 August 2009 at 23:10 Hi Janakiram Setting up the ODBC, you can use no default, default to master or default to DYNAMICS. All will work. What may not work is setting the defaultBI, Melbourne: Oct 23, FLBOUG, Clearwater: Oct 28, ASUG Northern California: Nov 2, ASUG Arizona Chapter: Nov 3, ASUG All Texas Chapter Meeting: Nov 11. Data Direct ODBC drivers not working with Data Services1 members found this topic helpful Search this topic...|Search DI: Installation, Administration, and Connectivities...|Search Box Select a search Explain These Choices... --------------------Recent Topics (All Forums) Unanswered Posts Register or Login to Post Forum Index -> Data Integrator -> DI: Installation, Administration, and Connectivities Author Message traviskSenior MemberJoined: 16 Jul 2008Posts: 89 Posted: Thu Apr 01, 2010 3:09 pmPost subject: Data https://blogs.msdn.microsoft.com/developingfordynamicsgp/2009/08/11/what-are-errors-5701-and-5703-that-show-in-the-dexsql-log/ Direct ODBC drivers not working with Data Services hello, I have a job that reads from a SQL database table and writes to a file on the data services job server. We are on XI 3.0. I have confirmed the data direct drivers are able to connect to our SQL Server 2000 database. We can see tables, even see data in the designer, and our DBA has http://www.forumtopics.com/busobj/viewtopic.php?p=714182 confirmed he saw our user log in when we execute a job. When we execute a job it gives us a generic Data Direct error message that means nothing to us: "SQL submitted to ODBC data source resulted in error <[DataDirect][ODBC SQL Server Driver]211132111321113211142111421114211152111521115>. The SQL submitted is ....." We have configured the odbc.ini in the dataservices /bin directory to point at our data direct installation: /opt/bo_odbc directory, and configured the odbc.ini in the /opt/bod_odbc directory to match our sql server database settings. Also, I would note that The job is able to connect, preview data in the tables, it's just not able to query the data in the tables through a regular query transform. Please advise of what's wrong... I saw another post on here somewhere that indicated that the data direct drivers provided by SAP are not compatable with BOE XIR3. I don't know if this means that they aren't compatable with BODI XIR3? Thanks for any info anyone can provide? Back to top manoj_dForum AddictJoined: 01 Jan 2009Posts: 2943 Posted: Thu Apr 01, 2010 4:35 pmPost subject: Re: Data Direct ODBC drivers not working with Data Services check the doc attached by Ben in the foll
New? Advanced Search Forum Miscellaneous Database Programming 5701 Changed database context to... using SQL 7 Stored Proc's If this is your first visit, be sure to check out the FAQ by clicking the link above. You http://forums.databasejournal.com/showthread.php?28183-5701-Changed-database-context-to-using-SQL-7-Stored-Proc's may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 3 of 3 Thread: 5701 Changed database context to... using SQL 7 Stored Proc's Tweet Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 02-27-2000,11:40 PM sql server #1 Neal Walters Guest 5701 Changed database context to... using SQL 7 Stored Proc's I'm trying to use SQL 7 stored procedures to implement something like example B7 where I allow users to signon and only show them to update records that they should be able to update. I first got the error in my B7 code, then I simplified down to a hardcoded simple ASP that tries to do a view (without all the changed database context logon stuff). ASP code set if SQL statement: mydb.SQL = "EXEC training_usp1 @parm1=abc" I also have: MyDB.dbDBType = "SQL" Listing of Stored Procedure: CREATE PROCEDURE training_usp1 @parm1 char(12) = NULL AS SELECT tr_exam, tr_classname, tr_city, tr_metroplex, tr_state, tr_country, tr_date_from, tr_date_to, tr_cost, trp_comp_name, tr_teacher from training, trprovider where tr_provider_id = trp_id and trp_userid = @parm1 I'm getting the following error: Error # = 0 Description = [Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to 'abcdefg'. Source = Microsoft OLE DB Provider for ODBC Drivers SQL State = 01000 NativeError = 5701 NOTE: "abcdefg" is my userid and database name. followed by Error # = 0 Description = [Microsoft][ODBC SQL Server Driver][SQL Server]Changed language setting to us_english. Source = Microsoft OLE DB Provider for ODBC Drivers SQL State = 01000 NativeError = 5703 Any ideas? Thanks in advance, Neal Walters http://ITCoolStuff.com Reply With Quote 02-29-2000,12:42 PM #2 Frank Guest 5701 Changed database context to... using SQL 7 Stored Proc's (reply) use the stored procedures properties when dealing with SPs and not dbSQL. dbStoredProc dbStoredProcCmdParams FK ------------ Neal Walters at 2/28/00 12:40:33 AM I'm trying to use SQL 7 stored procedures to implement something like example B7 where I allow users to signon and only show them to update records that they should be able to update. I first got the error in my B7 cod