I suspect it may be a security/permissions issue. Have you checked the event logs?
How have you got security set up for the connection? When you run the job manually the job will Be probably using your credentials, when you run as agent job it may be running as a service account? Just a thought.... > -----Original Message----- > From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- > boun...@listserver.u2ug.org] On Behalf Of John J. Wahl > Sent: Friday, 15 January 2010 6:16 a.m. > To: U2 Users List > Subject: [U2] Speaking of MsSQL 2008 ... > > > Not to tread over the same path for a thousandth time (oh this > poor path), but has anyone actually been able to get SQL Server 2005 or > 2008 to actually do a linked server directly to UniVerse and still get > that link to work when setting up SQL Agent jobs on the Microsoft SQL > Server to run at night? I had one working on a test server for a > while, but it would only run in the Management Studio when I manually > ran the SQL, it would never work at night using Jobs in the SQL Server > Agent, so I gave up. I've never gotten SQL Server to directly connect > in my office, so they still have their half dozen work-arounds here, > all using things like Microsoft Access and Linked Tables, then finally > linking those Access Databases to SQL Server. I've tried to make > changes to some of their very duct-tape like solutions, but I too > failed to get their UniVerse system to be read by SQL Server using any > connection type for that matter, including Mecki's SSIS concept. > > I have one machine here that is running SQL Server 2005 Developer > edition, which seems to have far more Providers and has had more luck > connecting to UniVerse in my tests, but once I try to do anything via a > nightly job, the same queries that may have worked for me manually > would fail to execute. > > Of the 3 servers I have two running Windows Server 2003, and one > is 2008 Std 32-bit. The 2008 box is also the UniVerse machine, which > runs 10.2.x. I'm fairly certain if the Linked Server idea would work, > it's an issue w/ either using the wrong provider or having a bad string > for the Connection, but everything I have personally read has failed > (at least for UniVerse). > > Anyone run into this type of headache in the past? > > > ------------------------------------ > John J. Wahl > Employee Owner (and U2 convert, yes I was an Microsoft only guy once > *cry*) > Programmer / Analyst > Tel: (330) 528-0091 Ext. 118 > Fax: (330) 655-8458 > Email: jw...@joseph.com > Web: http://www.Joseph.com/ > > -------- Original-Nachricht -------- > > Datum: Thu, 14 Jan 2010 08:43:06 -0500 > > Von: "Lettau, Jeff" <jlet...@polkaudio.com> > > An: U2 Users List <u2-users@listserver.u2ug.org> > > Betreff: Re: [U2] Error connecting to UD 5.2 from SQL Server 2008 > SSIS > > [ad] > > > You may not want to do this due to volume of data your trying to > pull, > > but... > > > > Have you tried setting up your UD5.2 server as a linked server in > SQL, > > then creating views to your linked server. Then use SSIS to pull > from > > the views, that way it doesn't know it isn't a SQL data source? > > > > Performance isn't bad if your limiting your I-desc and keep the data > > to single files in UD. Also use indexes in your UD views to limit > your data. > > You can't pass variables for data selection this way. You can limit > > data by day using @date-99 type i-descriptors or just write a quick > > program to pull your data to a temp file, then pull the file for > > updating things incrementally for Cognos. > > > > Jeffrey Lettau > > -- > GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users > _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
