| Author |
Topic |
|
trusted4u
Posting Yak Master
109 Posts |
 Posted - 2003-03-31 : 05:12:56
|
| Hi :I have a package which simply pulls the data from a txt file into my db. If the package is run manually it runs perfectly but when I create a job and schedule it, it shows successful in the Job History, whereas it didn't. Can anybody tell me what is the problem with it? Its very urgent..Thanks- Marjo. |
|
|
szakszi
Starting Member
9 Posts |
Posted - 2003-03-31 : 05:23:10
|
| Hi!What is in the package log?Regards,Szakszi |
 |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2003-03-31 : 05:25:13
|
| And why use dts to import a text file?==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
trusted4u
Posting Yak Master
109 Posts |
Posted - 2003-03-31 : 05:36:30
|
| Hi : Szakszi - how to check the package logs ? nr - These text files contains the attendance data which is sent by the attendance machines. So I have to schedule it. Actually, this package and job are already running on another server, but we want to discard it. So I have copied both to the new server and as I had mentioned, it runs perfectly when run manually but does not work if scheduled.- Marjo. |
|
|
|
szakszi
Starting Member
9 Posts |
Posted - 2003-03-31 : 05:43:45
|
| What do you use? SQL7 or 2K?Right click on your package -> View package log.Of course, first you have to "make" it. Design your package, open the general properties window, and on the third tab (i guess) you find the log options.regards,Szakszi |
|
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2003-03-31 : 05:48:45
|
| Strange. That's the second time today I've been told that an import needs to be in a package so it can be scheduled.Don't knokw where that idea comes from.Dts is a client application. When you run it manually you are running it on your machine under your user.When you schedule it it is run on the server.Quite often the server has a different version of mdac which causes problems.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
trusted4u
Posting Yak Master
109 Posts |
Posted - 2003-03-31 : 05:50:23
|
| I am using SQL 7. There is no view log option available on right click. Service pack - output of Select @@Version: Microsoft SQL Server 7.00 - 7.00.623 (Intel X86) Nov 27 1998 22:20:07 Copyright (c) 1988-1998 Microsoft Corporation Enterprise Edition on Windows NT 4.0 (Build 1381: Service Pack 6) |
|
|
|
trusted4u
Posting Yak Master
109 Posts |
Posted - 2003-03-31 : 05:56:12
|
| Hi nr, even I want to schedule it on the server. I am using SA login. |
|
|
|
szakszi
Starting Member
9 Posts |
Posted - 2003-03-31 : 06:03:34
|
| You can "make" package log on SQL7, too. See my previous comment. But the package log isn't stored in the MSDB, it will be a file on your disk.(Currently i can't open an EM, so it's not an exact description)SzaksziEdited by - szakszi on 03/31/2003 06:04:25 |
|
|
|
trusted4u
Posting Yak Master
109 Posts |
Posted - 2003-03-31 : 06:59:50
|
| This is what I recvd in the Logs when I executed the package manually :The description for Event ID ( 80 ) in Source ( DataTransformationServices ) 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: Package Name: Attendance MachinesPackage Description: Packege for Attendance MachinesPackage ID: {A10648DD-E079-4417-9EC6-C5AA011A20CF}Package Version: {082184F7-317B-4B14-8BD6-6533F6716CD0}Package Execution Lineage: {95E5AF7B-AEAC-44E9-8FB3-E36EF88D0A28}Executed On: SOFTWARE3Executed By: marjoExecution Started: 3/30/2003 3:48:56 PMExecution Completed: 3/30/2003 3:48:57 PMPackage Steps execution information:Step 'DTSStep_DTSActiveScriptTask_1' succeededStep 'DTSStep_DTSExecuteSQLTask_1' succeededStep 'DTSStep_DTSExecuteSQLTask_2' succeeded. |
|
|
|
szakszi
Starting Member
9 Posts |
Posted - 2003-03-31 : 08:02:53
|
quote:
This is what I recvd in the Logs when I executed the package manually :
great. what you recvd when it's scheduled?And do not forget NR's comments:quote:
Dts is a client application. When you run it manually you are running it on your machine under your user. When you schedule it it is run on the server. Szakszi:"Usually under SQLAgent user."Quite often the server has a different version of mdac which causes problems.
|
|
|
|
trusted4u
Posting Yak Master
109 Posts |
Posted - 2003-04-01 : 01:58:18
|
| Still Confused. I have again created the package and scheduled it, mind you - I am working on the Server, logged in as administrator . But still I am facing the same problem i.e. the package runs manually but does not run when scheduled. And there is no log information also. I have checked the ownership of both - package and job it shows DTC\ADMINISTRATOR [ The Admin login ]. Pls get me out of this hell like situation...- Marjo. |
|
|
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
Posted - 2003-04-01 : 04:39:41
|
| A couple of things:When you're job fails, have you set it to write to Windows App Log when failing ? See what is in there...Check out the SQL Agent Logs (right-click SQL Server Agent under Agent, and Display Error Log)...Check SQL Error Log's ....HTH*#&#* *#&#* *#&#* *#&#* Chaos, Disorder and Panic ... my work is done here! |
|
|
|
trusted4u
Posting Yak Master
109 Posts |
Posted - 2003-04-01 : 04:57:39
|
| Hi Wanderer : Yes I have checked out the log option but I didn't get any information now. Pls read the following :package name : AttendanceOwner : dtc/administratorjob created by package after I scheduled it : Attendance_JobOwner : SASqlServerAgent using the login : Local System AccountThis is the current scenario, now the problem is, when I schedule the package it says successful but does not execute the package at all. SA is sql server login and not win nt login. Since ystdy I am breaking my head after this problem. Is it becoz of the conflict between the job owner - SA and the SqlServerAgent - Local System account ???- Marjo. |
|
|
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
Posted - 2003-04-07 : 05:51:03
|
| Can't say I've got a real answer here...your job: Attendance_Job, try and add steps in it that write out to a text file - Insert steps before and after, just to try and confirm that steps are running (these are the steps you've added) just trying to track the process.I'm afraid you're definitely not in "quick fix" mode here ...sorry I can't be more helpful...*#&#* *#&#* *#&#* *#&#* Chaos, Disorder and Panic ... my work is done here! |
|
|
|
|
Job Not Executing