Member Login

Username
Password
Forget Password
New Sign Up
Search Forum

Buy Support
Incidents

If you can't find your answer in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us private or confidential information:

Click Here
If you can't login and post questions or you are having trouble viewing forum posts:
Click Here
Callback
Support

If you live in USA, UK, Canada, Australia or New Zealand, you can leave us details on your question and request us to call you back and discuss them with you personally  (charges apply).

Click Here
 
Buy Support
Incidents
If you can't find your answer in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us private or confidential information:
Click Here

Forum : SQL Integration Package not running as part of a SQL Server jobSearch Forum

Forum Home > QODBC - ODBC Driver for QuickBooks > QODBC v8 Forum

 New Topic 
 
 Post Reply 
[1]  
 SQL Integration Package not running as part of a SQL Server job 
 Author   Message 
  ATGoss 
  
 Group: Members 
 Posts: 22 
 Joined: 2007-06-30 
 Profile
 Posted : 2008-02-02 04:09:05
Now that we upgrated to QuickBooks Enterprise 8.0, when we manually run a QODBC query as part of an SQL Integration Package in SQL Server 2005, it runs fine, but if the package runs as part of a job, it fails with the following error:  "Description: System.Data.Odbc.OdbcException: ERROR [00000] [QODBC] QB Begin Session Failed. Error = 80040408, Could not start QuickBooks."

I had QuickBooks open as Admin when I tried running the job. QuickBooks did not prompt for allowing access (as it should already allow packages to run).

(My theory is that running an Integration Package directly executes at the logged in user [Administrator] while the job tries to run the package as the user SYSTEM, though I'm not sure why it would stop working when we upgraded.)

Any help is greatly appreciated! So far the upgrade to Enterprise has not be a pleasant experience. 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2008-02-02 10:58:21
When the package is run as part of a job it runs as a system service, which means QuickBooks must not be running already and your company file must work in unattended mode as per: How do I setup QODBC to auto-login into QuickBooks and start it if it's not running?  

  Top 
  ATGoss 
  
 Group: Members 
 Posts: 22 
 Joined: 2007-06-30 
 Profile
 Posted : 2008-02-05 11:20:58
I went through your 17-step process to get unattended mode working, and I successfully ran my Integration Package in unattended mode, but it still fails with the same error when I run the job that executes my package. Seems there is something deeper causing this problem. Please help! 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2008-02-05 12:57:19
The job must execute locally on the SQL Server 2005 with QuickBooks on it and a Windows Service requires the QODBC Server Edition and the QODBC DCOMs to be configured as per: Does QODBC work with MS SQL Server 2005 Linked Tables?  

  Top 
  ATGoss 
  
 Group: Members 
 Posts: 22 
 Joined: 2007-06-30 
 Profile
 Posted : 2008-03-05 07:23:46
Since we do not have the server edition of QODBC, we tried running our SQL Integration Packages using the "dtexec" command in a batch file and scheduling it to run each evening. This works great, but when it runs automatically (but not if I run it when logged in to the server) I get the following messages over and over (50-100 times for each package run) in the event log:

Event Type:    Information
Event Source:    HHCTRL
Event Category:    None
Event ID:    1903
Date:        3/4/2008
Time:        12:24:18 AM
User:        N/A
Computer:    ####
Description:
The description for Event ID ( 1903 ) in Source ( HHCTRL ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: http://go.microsoft.com/fwlink?LinkID=45839.

Any idea what is happening? The packages complete just fine, but it is very annoying to have the application event log flooded with these messages every day. 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2008-03-05 07:45:21
QuickBooks doesn't run as a Windows service, so you always need to be logged into the server console so QuickBooks can run there when called by QODBC. 

  Top 
 New Topic 
 
 Post Reply 
[1]  

Jump to