When I change the SA password on my server the current Scheduled SQL Jobs no longer work. If I run DTS packages by themselves and not from the Scheduled job window they work fine. I am using the sa as the Owner of the jobs and my SQL Agents services use a Domain Account. If I rebuild the jobs after the sa password is change they work fine. However, I don't want to rebuild 100 jobs every time I change my SA password.How can I fix or get around this problem without rebuilding my jobs?
Does anyone has a script or knows how to find out whether the schedule job completed or not? If I schedule the job to backup all databases on server and e-mail me when job completes. But one time the job got stuck and somehow never completed. Is there a way I can schedule the job to see whether the other job completed or not?
I have a very peculiar problem. I have few CommandExec jobs on SQL Server 7.0 which has been scheduled to execute at a specific time. The jobs are executing properly but, the problem is they stop after the completion. i.e after finishing the jobs they still flash a message "Executing the job" they don't flash the message "Not Running" this is happening only to commandExec jobs, I have also few TSQL jobs which are working properly. I tried even giving the duration (start and stop time) but no use. Has anyone encountered this problem? If you have a solution PLS pass it on to me. I am in a very desparate situation.
When I create a DTS to import data from Visual FoxPro it will work if I run immeadiately, but when I schedule it to run at a specific time it will Fail. Any ideas why??
I have a section of about 6 DTS packages that started failing recently. They all write to a network share using a UNC path. The failure coincides with a change to the account SQL Server and SQL Agent run under. I know security context is very important and I have verified the new service account they run under is a Domain account that can execute the DTS packages and has full permissions to the network share.
But when the Agent Job tries to run it fails everytime. Two of us have been looking at this and can't find the issue.
NOTE: I also made the service accout a Server Administrator (fixed server role) to make sure it wasn't a SQL permissions issue.
Hi all. We recently migrated to SQL Server '05 from 2000 and I'm trying to learn SSIS by crash course.
I just wrote an SSIS for one of our nightly processes in Studio 2005. It built with no errors, and the solution and resulting package are saved on the server housing SQL Server.
I ran the package in debug and it completed 100% with no errors. However, when I scheduled the package in SQL Server, it starts and fails.
Now, I'm very new to SQL '05 and I'm trying to figure out how to log the SSIS jobs, but is there any way to find out why the scheduled packages fail?
I'm desperately needing help on this, and any help would be greatly appreciated!
I have 3 SSIS packages I had in a project and exported and scheduled via an SQL Agent job. 2 are working great and one is failing. I have noticed on this one its also having issues in BIDS. It runs sucessfully once then next day when I go in it fails. If I just go into the Data flow and open up the SQL Destimation and then hit ok and try re-running it works. It is like there is something that it doesn't remember.
Same thing happens in SQL Agent if before I promote I go into SQl destination editor hit ok save then
create my build run it via agent job it works 1st time but fails on the following time. I don't see anything different between this SSIS and the others but there must be something.
All of these are simple copy data from as/400 to SQL server with some data conversions.
Here is the error msg I am receiving.
Message Executed as user: PERFORMANCEstacyadmin. ....3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 5:55:11 AM Error: 2008-04-08 05:56:00.88 Code: 0xC0202009 Source: Load WeeklySalesHistory Current Week WeeklySalesHistory [184] Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E14. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E14 Description: "Cannot fetch a row from OLE DB provider "BULK" for linked server "(null)".". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E14 Description: "The OLE DB provider "BULK" for linked server "(null)" reported an error. The provider did not give any information about the error.". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E14 Description: "Reading from DTS buffer timed out.". End Error Error: 2... The package execution fa... The step failed.
I have created a backup that does once weekly BAK and every night it does TRN backup. This is in the same maintaince plan, the jobs appear as seprate jobs as they should. I have noticed my TRN is always failing, after looking into the event logs i see this.
please note this is lastest time to early:
4:22pm this is the warning that the event log gives:
SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan 'xxxxxxxx TRN'' (0xB87B2FA07E4FB74CA01A1D38134C9C4F) - Status: Failed - Invoked on: 2007-03-09 16:19:40 - Message: The job failed. The Job was invoked by User domainAdministrator. The last step to run was step 1 (Step 1).
the next is 4:22pm 18265 : Log backed up: Database: Staging, creation date(time): 2007/01/30(09:35:34), first LSN: 24624:14008:1, last LSN: 24624:14021:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'f:program filesmicrosoft sql serverMSSQLBACKUPStagingStaging_tlog_200703091622.TRN'}).
last is 4:21pm 18264 : Database backed up: Database: Staging, creation date(time): 2007/01/30(09:35:34), pages dumped: 93982, first LSN: 24624:14008:2, last LSN: 24624:14018:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'f:program filesmicrosoft sql serverMSSQLBACKUPStagingStaging_db_200703091618.BAK'}).
So for some very strange reason its running a full backup then a Transactional, for this reason i would say its failing but why is it even doing this backup? the job is only for TRN????
I was hoping if someone can help me shed some light on the following error messages -
Some of the billing jobs in SQL are failing, here is the message from application log - This is happening on the production server.
"SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan 'DB Maintenance Plan3'' (0x8BCD2C33DF5EC447BC7F1228E2C455E4) - Status: Failed - Invoked on: 2007-12-20 06:00:01 - Message: The job failed. The Job was invoked by Schedule 54 (Schedule 1). The last step to run was step 1 (Step 1)."
Has anyone seen this message before, whats a way to fix this issue.
I'm thinking of using the SQL Agent Job Scheduler as part of a larger application and I'm wondering if anyone knows of a limit on how many schedules or jobs that can exist on a SQL Server at one time.
I am trying to figure out a way , looking at the tables in MSDB (SysJobHistory) that if a scheduled job is running and not completed yet , for how long it has been running. I have to look for all the jobs with run_status = 4 (in process). But what i figured out it no history is written till the job is finished or cancelled. Can anyone help me with this
I have a scheduled job that run one time a day at 10 pm. My problem is that if the job fail, i want that the job run 10 minutes after until it complete with success.
I am running a scheduled DTS which transfers all the rows in a production table to another server every 30 minutes,each time it truncates the table on the second server before transfer.It has been running fine for several days.Will there be any problem in this kind of backup strategy? Do I have to clear any history logs frequently?Or any other problem can happen? Can anyone suggest any precautions,as there will not be any down time allowed.Replication is also not acceptable by the client. Thanks.
I find some scheduled jobs are switching from an 'enabled' state to a 'disabled' state apparently for no good reason. The job itself still shows as being 'enabled', however the associated scheduled becomes 'disabled'. Does anyone why this would be? Is the problem associated with a paritcular service pack or anything??
I have a job that runs hourly every day from 7:00 to 19:00. I'd like to be able to detect the last run of the day. The problem is, I may change one (or both) or the scheduled run times, so I don't want to hard code 19:00 into my detection scheme.
I stumbled across the sysjobsschedules table in the msdb database, and I think the Next_Run_date and Next_Run_time fields will get me where I need to be.
I'm trying to build a second job that runs at 10 minutes after the hour, 24 hours a day that will somehow detect whether or not the primary job just finished it's last run of the day, and if so, insert some records into a table.
Here's what I have so far...
DECLARE @intFlg1 INTEGER SET @intFlg1= (SELECT CASE WHEN CONVERT(DATETIME, CAST(next_run_date AS CHAR(8)), 102) = Prod_Plan.dbo.RemoveTime(GETDATE()) THEN 1 ELSE 0 END FROM msdb.dbo.sysjobschedules WHERE (name = N'prodplan_importorders')) IF @intFlg1=0 INSERT INTO BLDOFF_INV_DAILY() SELECT GETDATE() AS Expr1, Product, Whse, Qty FROM BldOff_Inv_Hourly
The problem with this is that it will append records every hour after the last run until midnight. I only want it to append them once.
Its not possible to schedule jobs via Express is it? Like I have a process that connects to an Oracle system grabs the data... plays with it some and then inserts it into the MSSQL 2005 server... We need this process to run say every 2 hours... Express cant do that cant it?
I have a strange problem with a scheduled task failing with the following:
"Unable to send completion notification email to operator with email name '' for task 2780, 'Scheduled Update'"
This job is the same across several servers and the job runs on the other servers. This is a bit frustrating... I cannot seem to find the difference that is causing the problem.
The funny thing is that I am not using SQLMail or anything to notify anyone regardless if the job succeeds or fails.
I have created a package that extracts data from an Oracle 10g database into a database on SQL Server 2005 SP2.
This package run fine when run inside BIDS and also if run from DTExecUI or DTExec (This is done while logged in using the same domain account that runs both the SQL Service and the SQL Agent Service. This account is also a local admin on the box.)
When I try to schedule this with SQL Server Agent (running under the SQL Agent Service Account) it returns an MSDAORA error
"Oracle client and network components were not found"
The same error occurs if I try to use CmdExe step to try and execute the DTExec command.
The interesting part however is that I use a lower privaleged proxy account then
(a) Executing the package directly still fails but (b) Running a DTExec command will succed
Can anyone provide an explanation for this behaviour. While I can work around this "feature" by using the DTExec and a proxy account it does make the packages harder to configure/debug and defeats many of the configuration advantages provided by SSIS
I have created DTS packages to export data to text files....these packages are running...the jobs that are created to run these packages are failing ... both the SQL SERVER and the SQL SERVER AGENT are running administrator accounts ...if the job step is run on the command line it works..so basically some permission that invokes the the command shell is missing...jobs that run just T-SQL steps work fine too....what am i missing out?
I have a DB Maintenance plan created that performs optimizations, integrity checks, and a database backup. The optimizations and integrity checks work fine, but the backup job fails. The backup job is to write the .bak file to a network share. When I change the owner of the job to "sqluser", the job fails at step 0 withe the following error: The job failed. Unable to determine if the owner (rsnsqluser) of job DB Backup Job for DB Maintenance Plan 'Online Database Server Maintenance Plan' has server access (reason: Could not obtain information about Windows NT group/user 'rsnsqluser'. [SQLSTATE 42000] (Error 8198)). Checked with the system admin for this server and sqluser has priviledges to do everything, including write to the network share.
So, now I change the owner of the same maintenance job from sqluser to "sa". I now get this error: Executed as user: RSNsqluser. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
Checked the settings for MSSQLSERVER and SQLSERVERAGENT in Control Panel. Everything seems to be in order according to the other threads I have read.
For grins, I tried to ensure the sqluser password on the SQL Server Agent was correct. When I try to enter the new password I get this: sql server agent startup account could not be verified I click yes (it asks if I want to continue anyway). Is the password not being registered properly in the agent?
One other thing, the sqluser user is listed under Security|Logins as connecting with Windows Authentication. We have several other servers that are set up the same and work fine. What am I missing? I'm pulling my hair out! :eek:
I have this backup job created, this job is being called from VB once all the data is finished loading. You need to have SA permissions or be the database owner in order to run the jobs. How do I get around this, I don't want the user to be db owner or have sa privledges. Does anyone have any SP to get around this Thanks for any help
Hi all I'm stuck here, I hope someone else has come across a problem like this. About 12 scheduled jobs are running on SQL Server 7 (NT is the operating system) They are supposed to run under the security context of an account set up to run as a service for both SQL Server Agent and SQL scheduling Agent. This user account was given all the permissions that the person scheduling them has(that's me, also part of sysadmin role). Everything was running fine until one day the server crashed and after it came back up, nothing was working. The error I get is an odbc link error. I was even unable to open up the packages, so I had to recreate them from saved .dts files. I did come to find out that the NT domain admin password was changed as well, but why should that affect the user account under which these jobs run? Anyway, at the moment, nothing runs on the server and I can only manually execute them as packages from my local computer. Please help me to narrow down what could be the problem. The Agent service and sql server services are running so that's not the problem. thanks...
Had to rename a SQL 2000 box and now the scheduled maint jobs that were created under the previous name of the box cannot be deleted via EM. Can anyone offer help?
We have DTS Packages that are scheduled to run nightly and show up in EM under JOBS under SQL Server Agent. A password got changed and some of the nightly jobs blew up.
Went into the Packages and entered the new password and successfully executed the packages BUT when I go back to jobs under the SQL Server Agent, the jobs STILL will not run - they fail with a login failure - as if i never fixed the DTS package. HELP
Can anybody help me in solving this issue. We are currently facing an issue in our scheduled jobs. We have a job scheduled in SQL Server 7.0, which executes SPs one by one. The job makes the database to single user mode and starts the clean up job (execute SP, which deletes old records from specified tables). Once this is done, the database is again converted to multi use.Our database size is 8 GB, there is a huge volume of data. our client started the job on one weekend and it continued till tuesday after noon, on wednessday morning, the job got failed.
Please help me in solving this issue. why the job taking so much time to run and how it can be monitored and tuned to work properly.
My DTS Package work fine if I Execute it manually, but I need to do it automatically just after midnight. I defined my schedule and made sure the job was present in the SQL Server Agent>Jobs, but it fails and the Job History shows the following error:
DTSRun: Loading... DTSRun: Executing... DTSRun OnStart: DTSStep_DTSDataPumpTask_1 DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005) Error string: [Microsoft][ODBC Microsoft Access Driver] Cannot start your application. The workgroup information file is missing or opened exclusively by another user. Error source: Microsoft OLE DB Provider for ODBC Drivers Help file: Help context: 0 Error Detail Records: Error: -2147467259 (80004005); Provider Error: 1901 (76D) Error string: [Microsoft][ODBC Microsoft Access Driver] Cannot start your application. The workgroup information file is missing or opened exclusively by another user. Error source: Microsoft OLE DB Provider for ODBC Drivers Help file: Help context: 0 DTSRun OnFinish: DTSStep_DTSDataPumpTask_1 DTSRun: Package execution complete. Process Exit Code 1. The step failed.
I've just set up 2 new SQL 7.0 servers, and my new maintenance jobs - backups, optimisations, consistency check jobs etc - are all mysteriously failing. I've created them both with the Maintenance Wizard, and again by hand. I've attempted manual and scheduled runs. All to no avail. Nor do they populate the sysmainthistory table, although they're configured to do so. The mystery is that we have successfully installed some user DTS processes, and THEIR jobs work. In order to resolve the problem, I've:
(1) ensured the Agent service is running;
(2) ensured adequate space on the drive etc;
(3) verified that sqlmaint.exe exists in Mssqlinn;
(4) unchecked the 'attempt to repair minor errors' box (I read this was a known cause of the problem);
I've got some clues to go on, but nothing conclusive;
'sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.'
Executed as user: NT AUTHORITYSYSTEM. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
Additionally, both servers hold databases that I imported from another server-INCLUDING the msdb, and BOTH have the same problems and same error messages. This cannot be a coincidence.
I just had 2 DTS job fail, that had been running fine for weeks. Any ideas why these would fail when nothing about the jobs has changed ? Other jobs with the same owner ran OK.
Here's the message from DTS #1 Job History:
DTSRun: Loading... DTSRun: Executing... DTSRun OnStart: DTSStep_DTSDataPumpTask_1 DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005) Error string: Error opening datafile: The referenced account is currently locked out and may not be logged on to. Error source: Microsoft Data Transformation Services Flat File Rowset Provider Help file: DTSFFile.hlp Help context: 0 Error Detail Records: Error: 1909 (775); Provider Error: 1909 (775) Error string: Error opening datafile: The referenced account is currently locked out and may not be logged on to. Error source: Microsoft Data Transformation Services Flat File Rowset Provider Help file: DTSFFile.hlp Help context: 0 DTSRun OnFinish: DTSStep_DTSDataPumpTask_1 DTSRun: Package execution complete. Process Exit Code 1. The step failed.
And here's the message from DTS #2 job history:
... DTSRun: Executing... DTSRun OnStart: Delete from Table [TI].[dbo].[Sheet1$] Step DTSRun OnFinish: Delete from Table [TI].[dbo].[Sheet1$] Step DTSRun OnStart: Copy Data from Sheet1$ to [TI].[dbo].[Sheet1$] Step DTSRun OnProgress: Copy Data from Sheet1$ to [TI].[dbo].[Sheet1$] Step; 117 Rows have been transformed or copied.; PercentComplete = 0; ProgressCount = 117 DTSRun OnFinish: Copy Data from Sheet1$ to [TI].[dbo].[Sheet1$] Step DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_2 DTSRun OnError: DTSStep_DTSExecuteSQLTask_2, Error = -2147467259 (80004005) Error string: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error Detail Records: Error: -2147467259 (80004005); Provider Error: 18452 (... Process Exit Code 1. The step failed.
Hi Guys, I'm Hoping some one could help me out, I'm in need of creating a web interface to monitor scheduled SQL Jobs, both on sql 2000 & 2005. I'm new to asp, Can anyone point me in the right direction.Really appreciate it. Regards
i have a package scheduled in sql server..... if i change something in the package and save the change... will the scheduled job then reflect that change? or does the scheduled job have to be deleted and the package re-scheduled in order for the change to take affect? (for example....i have a scheduled package which pulls some data from an oracle server and populates a sql server tabel. well....the oracle server has changed. so if i open my package and change the oracle server connection and save it, will the scheduled job have this change?)
Getting this message when running a dtsrun step in a scheduled job;
DTSRun: Loading... DTSRun: Executing... Error: -2147220499 (800403ED); Provider Error: 0 (0) Error string: No Steps have been defined for the transformation Package. Error source: Microsoft Data Transformation Services (DTS) Package Help file: sqldts.hlp Help context: 700. Process Exit Code 1. The step failed.
This just started today.. These jobs have been running for months with no problems.
We have scheduled jobs, which run every 2 minutes. If the job runs at 1:59am, the next run time is set to 2:01 am. If at 2:00am, the clock is rolled back to 1:00, my scheduled run time is still 2:01am. In this situalion, my 2 minute job will not run until 1 hour and 1 minute later, at 2:01am.
Any suggestions for reseting the next run times on the jobs to the next interval after the clock roles back to 1:00am.
