Problem Scheduling Package in SQL 2005 |
Author |
Message |
|
Posted : 2007-08-23 13:03:23 |
I am having an interesting problem. I downloaded the trial, and set up an SSIS package to run on a schedule which worked great after i figured out how to set up a proxy. Now my trial ran out and i bought the read only version, as i dont need to write any data to QB, just pull it out with my scheduled package. Now the package refuses to run on a schedule. It acts just like it did before i set up the proxy. Is there something tied to the proxy that i set up? Or does it have something to do with the version i bought? I'm using QB Enterprise Retail Edition 7.0 and SQL 2005.... Any help would be much appreciated.
Thanks
Ben |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2007-08-23 19:54:36 |
|
|
|
|
Posted : 2007-08-24 00:14:52 |
Ok, so if i'm understanding this correctly.... Because SQL uses its own Windows service to schedule an SSIS package, i have to have the server edition with the DCOM? What if i only need the DCOM to be able to schedule to pull data from QB, is there a solution other then buying the $500 Server Edition because i will not ever be writing to QB? Maybe just a DCOM patch upgrade?
Thanks for your help
Ben |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2007-08-24 01:57:39 |
|
|
|
|
Posted : 2007-08-24 02:18:03 |
Ok, now we're seeing progress. Do i need to set up and funky security settings or anything (meaning do i need to set up a proxy account?) as i am just getting a failed package. The IBIZ integrator is showing this in the log: Client Connected, Client Disconnected, Client Connected, Client Disconnected... etc, you get the point. It seems to be reading it ok, as its showing something in the log... but just to make sure, i just need to leave it set to read from the localhost:2080 correct?
Thanks
Ben |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2007-08-24 06:41:30 |
Make sure everything works using VB Demo first, then move across to your SSIS package. |
|
|
|
|
Posted : 2007-08-24 08:29:09 |
I am receiving errors at any level i can think to test it. Any time i have the remote connector it errors out, from the VBDemo and from the QODBC Configuration screen when you "Test Connection to QB". The only way i can get it to work is if i turn the remote connector off, then it connects just fine, with both VBDemo and the Test connection. I have tried every setting i can find in the QODBC, but no luck.
What am i doing wrong? Ben |
|
|
|
|
Posted : 2007-08-24 14:13:49 |
Ok, after testing with every setting i could think of, i'm still getting errors in the VBDemo. Its saying "[QODBC] Only Licensed for use with Enterprise Version Please contact your dealer for an upgrade". I can get it to run without the remote connector, but then it won't schedule. Do i need an upgrade to make this work?
Ben |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2007-08-24 15:18:06 |
Sounds like you're running the QODBC Enterprise Edition? The QODBC Remote Connector requires the full version of QODBC. Please download and install the latest full version update.
See: How can I get the latest version of QODBC? |
|
|
|
|
Posted : 2007-08-25 00:47:34 |
Upgrade has been installed, but no change. From the beginning i've been under the impression that i had a full version... I just downloaded the trial, and then bought the Read Only version. The upgrade seemed to work just fine, downloaded and installed over my existing QODBC, and then had to re-set all of my preferences... but i'm still getting the Enterprise Version error when i try and connect with the VBDemo. I'm not sure where to go from here.......
Ben |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2007-09-25 10:35:46 |
Enterprise users are getting "[QODBC] Only Licensed for use with Enterprise Version Please contact your dealer for an upgrade" errors when they try to setup the QODBC Remote Connector. This has now been fixed by using QODBC v8.00.00.234 (or higher). See: How can I get the latest version of QODBC? |
|
|
|