Native 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 informatica sql server message 5701 changed database context to between SQL Server and the Microsoft Dynamics GP application, you might have noticed
[microsoft][odbc Sql Server Driver][sql Server]changed Database Context To
messages with errors 5701 and 5703 being reported. See the example below: /*/* Date: 08/10/2009 Time: 20:09:49 SQLSTATE:(01000) Native sqlstate 01000 Err:(5701) stmt(0):*/[Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context 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 atNew? 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 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 https://blogs.msdn.microsoft.com/developingfordynamicsgp/2009/08/11/what-are-errors-5701-and-5703-that-show-in-the-dexsql-log/ 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 #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 http://forums.databasejournal.com/showthread.php?28183-5701-Changed-database-context-to-using-SQL-7-Stored-Proc's 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 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
SQL Server experts to answer whatever question you can come up with. Our new SQL Server Forums are live! http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=37549 Come on over! We've restricted the ability to create new threads on these forums. SQL Server Forums Profile | ActiveTopics | Members | Search | ForumFAQ Register Now and get http://www.eonesolutions.com/discussion/duplicate-key-error-in-dexsql-log-when-opening-smart-list-after-upgraded-from-gp10-to-2013/ your question answered! Username: Password: Save Password Forgot your Password? All Forums Old Forums CLOSED - General SQL Server Connection Errors? Forum Locked Printer Friendly Author Topic G. Michael sql server Starting Member 31 Posts Posted-07/15/2004: 19:59:00 Hi, I'm a newbie to SQL Server, and have finally traced some errors I'm experiencing when using a stored procedure with an ASP page (VBScript)... If you can shed any insight into my problem, please let me know what I can do about it.. It seems the errors are occuring about 65 seconds after changed database context the first initial load of the page. When I reload after approx 65 seconds, I get these errors. objCnn.Errors.Count =2 Database Connection Object Error No: 0 Description: [Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to 'ScottsDB'. Source: Microsoft OLE DB Provider for ODBC Drivers SQLState: 01000 NativeError: 5701 Error No: 0 Description: [Microsoft][ODBC SQL Server Driver][SQL Server]Changed language setting to us_english. Source: Microsoft OLE DB Provider for ODBC Drivers SQLState: 01000 NativeError: 5703 Thanks, Geoff G. Michael Starting Member 31 Posts Posted-07/15/2004: 20:48:32 I found the problem identified on the MS site!http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q197/4/59.asp&NoWebContent=1ThanksGeoff Kristen Test United Kingdom 22859 Posts Posted-07/16/2004: 00:44:58 The messages look "normal" to me (or perhaps I should say "informative" rather than "error")Kristen Topic Forum Locked Printer Friendly Jump To: Select Forum General SQL Server Forums New to SQL Server Programming New to SQL Server Administration Script Library Data Corruption Issues Database Design and Application Architecture SQL Server 2012 Forums Transact-SQL (2012) SQL Server Administration (2012) SSIS and Import/Export (2012) Analysis Server and Reporting Services (2012) Replication (2012) Availability Groups and DR (2012) Other S
Partners Shop Events Blog Downloads SIGN IN Search Cart FORUM Duplicate Key error in DexSQL log when Opening Smart list after upgraded from GP10 to 2013 Vote Up 0 Vote Down resolved eOne Forum // SmartList Builder Questions Follow May asked May 15, 2014 at 3:55pm Hi, We are testing GP 2013 and found out that it is really slow to open the windows for a user that have quite a few smart list reminders. By looking at the DexSQL log, there are lots of records that saying duplicate key row in a table. Not sure if that is related to the speed issue?How to fix the erros, please? The log detail as below: /* Date: 05/15/2014 Time: 14:25:48 stmt(99999024):*/ select count(*) from DYNAMICS..ASIEXP81 where ASI_Favorite_Dict_ID = 3107 and ASI_Favorite_Type = 3 and ASI_Favorite_Save_Level = 0 /* /* Date: 05/15/2014 Time: 14:25:48 SQLSTATE:(01000) Native Err:(5701) stmt(0):*/ [Microsoft][SQL Server Native Client 11.0][SQL Server]Changed database context to 'master'.*/ /* /* Date: 05/15/2014 Time: 14:25:48 SQLSTATE:(01000) Native Err:(5703) stmt(0):*/ [Microsoft][SQL Server Native Client 11.0][SQL Server]Changed language setting to us_english.*/ /* /* Date: 05/15/2014 Time: 14:25:48 SQLSTATE:(00000) Native Err:(5703) stmt(0):*/ */ /* /* Date: 05/15/2014 Time: 14:25:48 SQLSTATE:(00000) Native Err:(5703) status(0):*/ SWSTATUS DUMP*/ /* Date: 05/15/2014 Time: 14:25:48 stmt(99987712):*/ BEGIN SET DATEFORMAT ymd SET NOCOUNT ON SET CURSOR_CLOSE_ON_COMMIT OFF SET ANSI_NULLS ON SET ANSI_WARNINGS OFF SET ANSI_NULL_DFLT_ON ON SET ANSI_PADDING ON SET NUMERIC_ROUNDABORT OFF END /* Date: 05/15/2014 Time: 14:25:48 stmt(99999024):*/ update DYNAMICS..ASIEXP81 set ASI_Favorite_Name = 'RMA Tracking and Processing Header' where ASI_Favorite_Dict_ID = 3107 and ASI_Favorite_Type = 3 and ASI_Favorite_Save_Level = 0 /* Date: 05/15/2014 Time: 14:25:48 stmt(99986096):*/ { CALL PROD.dbo.zDP_EXT20200SS_1 ( 'CK RMA' ) } /* Date: 05/15/2014 Time: 14:25:48 stmt(99986096):*/ { CALL PROD.dbo.zDP_EXT20200SS_1 ( 'CK RMA' ) } /* Date: 05/15/2014 Time: 14:25:48 stmt(99964640):*/ {CALL DYNAMICS.dbo.zDP_ASIEXP86L_1(3107,3,0,0,'','','',-32768,3107,3,0,0,'','','',32767)} /* D