Packages Error Or Hang In SQL Agent But Not In BI IDE
Jul 31, 2006
Hi ,
I have an issues that worries me alot. I have SSIS packages scheduled in SQL Agent and they sometime error out or hang in Agent but never when i run them in BI IDE (Visual studio). There are two particular packages that always hang, alway in Agent but when i run them in BI IDE, they run just fine. Im was running them under in Agent under type= Sql server intergration services and also tried running under type = Operating System (CmdExec). Both types have the same problem. The packages hang. The log files dont say much, because the packages hang, no logging is doing so i dont get any infomation to determin what is going on. Can someone please help me ou.
We have initiated reinitialize subscription by which snapshot agent is started and hanged at 26%.We have a publication of 6 articles, transactional replication, using SQL Server 2008R2.
Below the Error Log Reported in SQL Agent (64 bit SQLServer 2008R2 Enterprise Edition Service pack 2 ,32Core CPU Numa Node and 64GB Ram
[298] SQLServer Error: 10054, TCP Provider: An existing connection was forcibly closed by the remote host. [SQLSTATE 08S01] [298] SQLServer Error: 10054, Communication link failure [SQLSTATE 08S01] [165] ODBC Error: 0, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001] [382] Logon to server '(local)' failed (ConnUpdateStartExecutionDate)
We are just migrating to sql servr 2005. I have created ssis pkg that runs fine when run mnaulli under BI. However, when I setup the ssis pkg to run as a SQL job. It errors out. Err is listed below. Seems like it is running the job under the SQL Agent account which does not have permissions to access the server i am pulling data from. Can u assit. 1984-2005. All rights reserved. Started: 1:30:51 PM Progress: 2008-02-22 13:30:57.55 Source: DTSTask_DTSDataPumpTask_1 Validating: 0% complete End Progress Error: 2008-02-22 13:30:58.33 Code: 0xC0202009 Source: Laser- Connection manager "FTWSQL" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80040E4D Description: "Login failed for user 'CFC 0SQLA'.". End Error Error: 2008-02-22 13:30:58.33 Code: 0xC020801C Source: DTSTask_DTSDataPumpTask_1 OLE DB Source [1] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "FTWSQL" failed with error code 0xC0202009. There m... The package execution fa... The step failed.
Details:MS SQL 2000 dual Intel 1.2 GHz processors.1 GB RAM2.1 GB dBDynamic Memory Managment.No other apps running on this server.First question:Since I have Dynamic Memory Managment setup, Is it usuall that thesqlsrv.exe process on the server steadily climbs and is in the 800 to900 MB range. There is only about 20 MB free. In theory this is howDMM can work, but do people really see it work this way.Second question:I had users complaining about lockups in the app I have to supportthat connects to this dB. At first I thought it was the large use ofmemory, but once I was able to see in Enterprise Manager that therewas process blocking several other processes. EM then locked up and Icouldn't get to the details of what the exact process was that wasdoing the blocking. After restarting SQL services things were fine.When I checked the logs there was nothing there about a hung process.The logs seemed very sparse. Why would there not be anything in thelogs about it. The logs actually seem very thin on any information.Thanks,T.
I have a meaty job that currently runs as a set of sql scripts under sql agent and I'm transferring this job to run as a SSIS package. I have managed to set it up so that it runs as a sql job (cheers guys!), and I'm watching the job run now, maxing out the CPU usage as it tries to run 10 different tasks at the same time . great stuff!
However, I've been thinking about how to view the progress of this job/package (the job only has one step; "run SSIS package"). With the current job as single scripts, in SQL agent you can view which step of the job you are at.... is it possible to somehow view which package task you're at (ideally with nice shiny yellow green and red updates like in debugging), or do you have to output each step result into a log file?
Oh, and another question! If i have a checkpoint in a package, and the package falls over, when the job is rerun through SQL agent, will it start at the checkpoint, or run from the start?
if I have some packages (.dtsx) that are depolyed to Server A and I have SQL Agent installed on Server B - if I run a run a package from SQL Agent, does it run on Server A or Server B?
They wre runnning fine until 4/21/2008 then all SSIS packages started to fail.
Simple SQL jobs are still running fine thouhgt and reporting success.
Unable to start execution of step 1 (reason: The SSIS subsystem failed to load [see the SQLAGENT.OUT file for details]; The job has been suspended). The step failed.
I'm having an issue in SQL Server 2005 with jobs that execute SSIS packages. The jobs run fine for a week or so, then I'll come to find that four or five (of the ten or so jobs) are hung in "executing" status. They seem to hang indefinitely (as some have been "executing" for hours with no end. The schedules of the hung jobs are all different, varying from every 10 minutes to nightly. The packages perform completely diffent tasks, as well. I can't seem to find any common thread with the jobs that get hung, other than they are all executing SSIS packages.
I've tried manually stopping the jobs and restarting the agent and SQL Server but the jobs hang again on there next scheduled run. The only thing that fixes the issue is rebooting the box, and then the jobs hang again in a week or so. Could some sort of memory leak be consuming resources throughout the week and be causing the jobs to eventually hang? I just rebooted the box and the sqlagent90.exe process is currently using about 7mb of memory. I'll keep an eye on it. Any other suggestions?
I've thought of creating another job that stops jobs that are hung, but what's to say that this job won't get hung as well? Plus this seems like a band-aid fix...
I don't recall having these problems until installing SQL Server 2005 SP2. Could this be related? I've searched like crazy and still can't find a resolution to this. It's becoming a big PITA...
Anyway, any suggestions would be very much appreciated!
I have SSIS Package that needs special permissions in network. I want to schedule SSIS running using SQL Agent. I don't want to other Jobs starts with special permissions. So, I decided to use proxy account to impersonate SSIS starting process by account with those permissions. I've perfomed following steps: 1. Create Login for the future proxy account and add it to sysadmins role. 2. Create Credential with account name and password information. 3. Create proxy account and give to it rights to run SSIS, CmdExec and ActiveX create. 4. Set Run as for step that starts my package to this proxy 5. Start my job. and I receive error "Process couldnot be created for step 1 job xxx. Reason: 1314" SQL Agent account and proxy accounts has also administrators rights on SQL Server computer and rights to login as service. When I change step configuration to run as SQL Agent account job completes succesfull. What do I do wrong?
I need some help from you on a problem with SQL Server Agent that I believe many of you have experienced. When searching on the web I find some loose answers, but it would not solve my problems. So here is my story.
1. I have created two SSIS packages, package 1 and package 2. Both packages have a Execute SQL Task making a select sql statement to a table, say Customer in AdventureWorks DB. Package1 also makes a Execute Pacakge Task to Package 2. Both packages have protectionlevel property set to EncryptSensitiveWithUserKey
2. Then I created two package configuration files per package, one indirect xml configuration and one xml configuration file. The former I created an environment variable called pack1, which was specifying the path and file name of second config file. Likewise, I did for package2. Maybe I could have reused thie first configuration file, but I am not sure since package1 calls package2.
3. Now I build and deploy my packages. Then I run my manifest file, going through the deployment wizard setting the necceccary properties like server name, user, password, I have also create the same environment variables on the deployment machine. I ensure that the package1 and package2 can be run under integration services (file system). And both package works. So far so good
4. Now I want to create a SQL server agent job that runs package1 and package2. Here I found an article that decribed How to Schedule and Run a SSIS package ( DTS ) Job in SQL Server 2005 http://www.codeproject.com/useritems/Schedule__Run__SSIS__DTS.asp
5. I created a job executor account and then Create SQL proxy account and associate proxy account with job executor account as described. I created a new ssis job, specifying type ssis integration services, run as proxy, setting package source to SSIS package store, naming the server and package name (package2).
6. Now, I try running job1 which runs package2. ANd it works. I was aware if I needed to give file permission on users (read and execute) on my dtsx/dtsconfig/log files. So far so good
7. Now, I try to run job test which runs package1 (which also runs package2). But now the job fails :-(. The job runs for some seconds, but fails. I have to say that I have some script tasks with message boxes inside!!! hope this doesn't matter. I have created all neccessary accounts, proxies, credentials and so on. here is the view history
Date 17.10.2006 00:50:53 Log Job History (test)
Step ID 1 Server ABEO-GEIR Job Name test Step Name test Duration 00:00:07 Sql Severity 0 Sql Message ID 0 Operator Emailed Operator Net sent Operator Paged Retries Attempted 0
Message Executed as user: abeo-geir as_jobuser. The package execution failed. The step failed.
Continue: This error is well known for you. It has been mentioned in many postings. Well, how do I go from here. Setting logging on the job results in only this information
PackageStart,ABEO-GEIR,ABEO-GEIR as_jobuser,Package1,{3F5BD166-D24B-4838-B3F1-018B6C2C7523},{8E1B8E45-7F1D-4C24-852C-2694F993E6D2},17.10.2006 00:59:40,17.10.2006 00:59:40,0,0x,Beginning of package execution.
PackageEnd,ABEO-GEIR,ABEO-GEIR as_jobuser,Package1,{3F5BD166-D24B-4838-B3F1-018B6C2C7523},{8E1B8E45-7F1D-4C24-852C-2694F993E6D2},17.10.2006 00:59:41,17.10.2006 00:59:41,1,0x,End of package execution.
Well, I read some place that I could run the job as type operating system (cmdexec). Here i could not choose Run as, but had to select SQL SErver agent account. NOw I got this message
Date 17.10.2006 01:05:21 Log Job History (test)
Step ID 0 Server ABEO-GEIR Job Name test Step Name (Job outcome) Duration 00:00:00 Sql Severity 0 Sql Message ID 0 Operator Emailed Operator Net sent Operator Paged Retries Attempted 0
Message The job failed. The Job was invoked by User sa. The last step to run was step 1 (test).
As you see, I can't come any further. I NEED HELP FROM YOU. I AM STUCK. I know many of you have solved this and I hope you can guide me through thise. I don't know how many hours or days I have used on this.
I have a requirement of logging the failure and the error of a job executing a SSIS package to text file. However, when I go to job step -> Advanced, in the section "SQL Server Integration Services Package" where that info to setup logging is, it is blank and just says:
"There are no options for this command type"
Any ideas?
I thought that this might not be supported in Standard Edition as I am running standard edition. Then I checked on two other servers, where I have Enterprise edition with SP2. On one of the installations, I am able to give the log file, the other one still shows,
"There are no options for this command type"
What is the problem? Both of them I am using the sysadmin role account. I have proxy account created on both the SQL instances. I don't think this is the problem, but still I checked this.
I have a ssis package that has multiple large lookups without memory restriction. When running the package manually from SSMS on the same server it runs on when running automatically under the job agent, the package errors out when the server memory gets depleted by the loading of the large lookup reference data. One of the messages I get is "An out-of-memory condition prevented the creation of the buffer object. "
Anyway, the package runs successfully when it runs automatically under the job agent.
I was curious as to why the above happens. Is that a bug or is the run time behavior different under these 2 environments by design.
I have a MASTER package containing multiple packages using execute package task in SSIS.When am running this MASTER Package in Sql server agent in SSMS, am getting error as below.
steps how to run this and let me know what information am missing to run the Master package.
ERROR :Failed to decrypt protected XML node “DTS: Password” with error 0x8009000B “Keynot valid for use in specified state”. You may not be authorized to access this information.
This error occurs when there is cryptographic error. Verify that the correct key is available.
I have stumbled on a problem with running a large number of SSIS packages in parallel, using the dtexec? command from inside an SQL Server job.
Ive described the environment, the goal and the problem below. Sorry if its a bit too long, but I tried to be as clear as possible.
The environment: Windows Server 2003 Enterprise x64 Edition, SQL Server 2005 32bit Enterprise Edition SP2.
The goal: We have a large number of text files that were loading into a staging area of a data warehouse (based on SQL Server 2k5, as said above).
We have one main? SSIS package that takes a list of files to load from an XML file, loops through that list and for each file in the list starts an SSIS package by using dtexec? command. The command is started asynchronously by using system.diagnostics.process.start() method. This means that a large number of SSIS packages are started in parallel. These packages perform the actual loading (with BULK insert).
I have successfully run the loading process from the command prompt (using the dtexec command to start the main package) a number of times.
In order to move the loading to a production environment and schedule it, we have set up an SQL Server Agent job. Weve created a proxy user with the necessary rights (the same user that runs the job from command prompt), created an the SQL Agent job (there is one step of type cmdexec? that runs the main? SSIS package with the dtexec? command).
If the input XML file for the main package contains a small number of files (for example 10), the SQL Server Agent job works fine the SSIS packages are started in parallel and they finish work successfully.
The problem: When the number of the concurrently started SSIS packages gets too big, the packages start to fail. When a large number of SSIS package executions are already taking place, the new dtexec commands fail after 0 seconds of work with an empty error message.
Please bear in mind that the same loading still works perfectly from command prompt on the same server with the same user. It only fails when run from the SQL Agent Job.
Ive tried to understand the limit, when do the packages start to fail, and I believe that the threshold is 80 parallel executions (I understand that it might not be desirable to start so many SSIS packages at once, but Id like to do it despite this).
Additional information:
The dtexec utility provides an error message where the package variables are shown and the fact that the package ran 0 seconds, but the Message? is empty (Message: ). Turning the logging on in all the packages does not provide an error message either, just a lot of run-time information. The try-catch block around the process.start() script in the main packages script task also does not reveal any errors. Ive increased the max worker threads? number for the cmdexec subsystem in the msdb.dbo.syssubsystems table to a safely high number and restarted the SQL Server, but this had no effect either.
The request:
Can anyone give ideas what could be the cause of the problem? If you have any ideas about how to further debug the problem, they are also very welcome. Thanks in advance!
Hi guys can you help me out---I have developed some SSIS packages in BIDs that use use the Microsoft OLE DB Provider for Oracle for OLE DB - (OLE DB Connection source) and are deploying to a windows2003 x64 server
Q1: How can my package run under 32 bit so it can pick up correct driver msdaora.dll --here "C:Program Files (x86)Common FilesSystemOle DB" folder rather than "C:Program FilesCommon FilesSystemOle DB" folder which is 64 bit and of course has no msdaora.dll in that location
Q2: How can I set up SQL Server Agent to run these packages under 32 bit mode At the moment I use the SQL Server Agent GUI and run as SQL Server Integration Services Package\\File System\\ and package path ie E:ComponentsWarehouse.ETLLoadGroup_Daily.dtsx
I am running a parent SSIS package (running sp2, 9.0.3042) that calls several child packages.
On our development server, we now cannot run this because we get 1 or more of these errors:
"Error 0x80004003 while preparing to load the package. Invalid pointer . " "Error 0xC0011008 while preparing to load the package. Error loading from XML. No further detailed error information can be specified for this problem because no Events object was passed where detailed error information can be stored. . "
It is not occuring on the same packages. It varies every time it is run.
I can run every one of the child packages individually, using the same login ID that the parent is executed under.
The parent package works fine on my local machine and other servers running the same version of SSIS. Just not on this server.
I have a really odd one here. We have a production server which is running SQL 2000 Enterprise Edition SP3. It has a number of databases which are backed up nightly. Last night all of the back-up jobs failed with the following error: -
Msg 913, Sev 16: Could not find database ID ##. Database may not be activated yet or may be in transition. [SQLSTATE 42000]
The databases are in good shape - no issues to report. When I run the Agent Job code within a Query Analyser session it works fine.
When I try and re-start the back-up from the Agent Job it continues to fail with the same error.
I am running the following TSQL command and it hangs. These commands are running from SQL 2000 server and it is querying information for SQL20005 database.
Running simple EXEC command work fine but running using Insert hangs.
Hi Everyone, I'm having a bit of a dispute with one of my clients' software developers. This client has a server, installed by us (Windows 2003 Std. SP1/ SQL 2000 SP3a) (Dual Xeon 2.8, 4GB RAM) They are having performance issues with the software developers application, which is based on SQL. I'm having trouble believing the issues are caused by the server, but the software dev's blaming us for the problems.
Yesterday i got a mail from them that a specific SQL query "hangs" upon execution and this is likely caused by a bad install of the server or SQL (yeah right). This query is: select * from table, wich hangs the server upon running. Theyt say a select row(item) from table does work (duh). Now i know a bit of SQL and i'm thinking this select all from that table query locking up the server is most likely caused by a table that has grown so big that it just locks up.
Am i right thinking this has nothing to do with the hardware/software (sbs/sql), but is merely caused by bad programming and/or lack of SQL knowledge at the dev's side? Especially since last year the DB grew to about 40 GB and i had to tell them to think about putting it in simple mode to make it smaller. Something they'd never heared about...
Any ideas would be very welcome. I don't want to go throw mud around with us blaming them and them blaming us and the client being the one with the problems. I just want to make a well thought out statement to the software dev. and then try to find the right solution.
I had 5 servers hang all on the same day, all within about 5 mins of each other scattered across 4 corners of the UK. Our support team tell me that it has something to do with SQL Server, but cannot say what. I can see looking at the error log of one of the servers, that there are about4 entries everyday since startup, and this continues right up until the night before the freeze.
At 22:00 the night before the freeze, a load of entries are written (Iv'e cut down the list to make it easier to read). then at around 4am the servers all froze. Could someone take a sneaky peak at these logs and tell me in your own opinion what caused this to happen.
The first section, is what I believe to be normal
2006-11-28 20:52:53.68 server Copyright (C) 1988-2002 Microsoft Corporation. 2006-11-28 20:52:53.68 server All rights reserved. 2006-11-28 20:52:53.68 server Server Process ID is 952. 2006-11-28 20:52:53.68 server Logging SQL Server messages in file 'D:Program FilesMicrosoft SQL ServerMSSQLlogERRORLOG'. 2006-11-28 20:52:53.73 server SQL Server is starting at priority class 'normal'(1 CPU detected). 2006-11-28 20:52:54.75 server Working Set size set to 409600 kilobytes. 2006-11-28 20:52:54.90 server SQL Server configured for thread mode processing. 2006-11-28 20:52:54.90 server Processor affinity turned ON, processor mask 0x1 2006-11-28 20:52:54.92 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks. 2006-11-28 20:52:55.20 server Attempting to initialize Distributed Transaction Coordinator. 2006-11-28 20:52:57.20 server Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b 2006-11-28 20:52:57.53 spid3 Starting up database 'master'. 2006-11-28 20:52:59.31 spid3 Server name is 'SN047483'. 2006-11-28 20:52:59.31 server Using 'SSNETLIB.DLL' version '8.0.760'. 2006-11-28 20:52:59.31 spid5 Starting up database 'model'. 2006-11-28 20:52:59.50 spid8 Starting up database 'msdb'. 2006-11-28 20:52:59.50 spid9 Starting up database 'pubs'. 2006-11-28 20:52:59.53 spid10 Starting up database 'udb'. 2006-11-28 20:52:59.64 spid11 Starting up database 'vgold'. 2006-11-28 20:53:00.07 server SQL server listening on 155.202.58.53: 1433. 2006-11-28 20:53:00.07 server SQL server listening on 127.0.0.1: 1433. 2006-11-28 20:53:00.29 spid5 Clearing tempdb database. 2006-11-28 20:53:00.64 server SQL server listening on TCP, Shared Memory, Named Pipes. 2006-11-28 20:53:00.64 server SQL Server is ready for client connections 2006-11-28 20:53:00.71 spid9 Starting up database 'dbs'. 2006-11-28 20:53:01.01 spid8 Recovery is checkpointing database 'msdb' (4) 2006-11-28 20:53:01.50 spid5 Starting up database 'tempdb'. 2006-11-28 20:53:53.78 spid3 Recovery complete. 2006-11-28 20:53:53.78 spid3 SQL global counter collection task is created. 2006-11-28 20:53:54.32 spid59 Using 'xpsqlbot.dll' version '2000.80.194' to execute extended stored procedure 'xp_qv'. 2006-11-29 00:00:01.10 spid69 Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'xp_instance_regread'. 2006-11-29 02:00:01.54 spid69 Using 'xplog70.dll' version '2000.80.760' to execute extended stored procedure 'xp_cmdshell'. 2006-11-29 02:00:09.31 backup Database backed up: Database: master, creation date(time): 2006/11/28(20:52:57), pages dumped: 1907, first LSN: 159:245:1, last LSN: 159:247:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'QMBACKDEVICE'}). 2006-11-29 02:00:11.46 backup Database backed up: Database: msdb, creation date(time): 2000/08/06(01:40:56), pages dumped: 1667, first LSN: 397:332:1, last LSN: 397:335:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'QMBACKDEVICE'}). 2006-11-29 02:01:58.10 backup Database backed up: Database: dbs, creation date(time): 2004/10/05(08:00:04), pages dumped: 94467, first LSN: 114:53199:1, last LSN: 114:53203:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'QMBACKDEVICE'}). 2006-11-29 02:01:58.20 backup Database log truncated: Database: dbs. 2006-11-29 10:51:33.43 spid62 Using 'odsole70.dll' version '2000.80.760' to execute extended stored procedure 'sp_OACreate'. 2006-11-30 02:00:04.34 backup Database backed up: Database: master, creation date(time): 2006/11/28(20:52:57), pages dumped: 1907, first LSN: 159:260:1, last LSN: 159:262:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'QMBACKDEVICE'}). 2006-11-30 02:00:06.57 backup Database backed up: Database: msdb, creation date(time): 2000/08/06(01:40:56), pages dumped: 1667, first LSN: 398:26:1, last LSN: 398:29:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'QMBACKDEVICE'}). 2006-11-30 02:01:53.84 backup Database backed up: Database: dbs, creation date(time): 2004/10/05(08:00:04), pages dumped: 94467, first LSN: 114:54895:1, last LSN: 114:54899:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'QMBACKDEVICE'}). 2006-11-30 02:01:53.93 backup Database log truncated: Database: dbs. 2006-11-30 13:10:09.96 spid67 Error: 60002, Severity: 15, State: 1 2006-11-30 13:10:09.96 spid67 PBX login_id 5592 already exists in user id 379. Proc Name: um_user_insert. 2006-12-01 02:00:04.51 backup Database backed up: Database: master, creation date(time): 2006/11/28(20:52:57), pages dumped: 1907, first LSN: 159:275:1, last LSN: 159:277:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'QMBACKDEVICE'}). 2006-12-01 02:00:06.76 backup Database backed up: Database: msdb, creation date(time): 2000/08/06(01:40:56), pages dumped: 1667, first LSN: 398:408:1, last LSN: 398:411:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'QMBACKDEVICE'}). 2006-12-01 02:01:52.31 backup Database backed up: Database: dbs, creation date(time): 2004/10/05(08:00:04), pages dumped: 94515, first LSN: 114:55915:1, last LSN: 114:55923:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'QMBACKDEVICE'}). 2006-12-01 02:01:52.39 backup Database log truncated: Database: dbs.
This second section then has around a good few hundred entries.
2006-12-01 22:00:01.98 spid67 Error: 60132, Severity: 15, State: 1 2006-12-01 22:00:01.98 spid67 Folder 7 is not assigned to user 11 Proc Name: ags_workflow_sess_count. 2006-12-01 22:00:02.04 spid67 Error: 60132, Severity: 15, State: 1 2006-12-01 22:00:02.04 spid67 Folder 7 is not assigned to user 11 Proc Name: ags_workflow_sess_count. 2006-12-01 22:18:02.57 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 22:18:02.57 spid66 Folder 7 is not assigned to user 63 Proc Name: ags_workflow_sess_count. 2006-12-01 22:43:37.42 spid67 Error: 60132, Severity: 15, State: 1 2006-12-01 22:43:37.42 spid67 Folder 7 is not assigned to user 493 Proc Name: ags_workflow_sess_count. 2006-12-01 22:43:37.43 spid67 Error: 60132, Severity: 15, State: 1 2006-12-01 22:43:37.43 spid67 Folder 7 is not assigned to user 493 Proc Name: ags_workflow_sess_count. 2006-12-01 22:44:37.51 spid58 Error: 60132, Severity: 15, State: 1 2006-12-01 22:44:37.51 spid58 Folder 7 is not assigned to user 613 Proc Name: ags_workflow_sess_count. 2006-12-01 22:46:07.00 spid67 Error: 60132, Severity: 15, State: 1 2006-12-01 22:46:07.00 spid67 Folder 7 is not assigned to user 660 Proc Name: ags_workflow_sess_count. 2006-12-01 23:00:20.65 spid58 Error: 60132, Severity: 15, State: 1 2006-12-01 23:00:20.65 spid58 Folder 7 is not assigned to user 949 Proc Name: ags_workflow_sess_count. 2006-12-01 23:00:20.67 spid58 Error: 60132, Severity: 15, State: 1 2006-12-01 23:00:20.67 spid58 Folder 7 is not assigned to user 973 Proc Name: ags_workflow_sess_count. 2006-12-01 23:02:33.07 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:02:33.07 spid66 Folder 7 is not assigned to user 1010 Proc Name: ags_workflow_sess_count. 2006-12-01 23:04:38.10 spid58 Error: 60132, Severity: 15, State: 1 2006-12-01 23:04:38.10 spid58 Folder 7 is not assigned to user 1247 Proc Name: ags_workflow_sess_count. 2006-12-01 23:04:38.12 spid58 Error: 60132, Severity: 15, State: 1 2006-12-01 23:04:38.12 spid58 Folder 7 is not assigned to user 1266 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.59 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.59 spid66 Folder 7 is not assigned to user 1659 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.59 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.59 spid66 Folder 7 is not assigned to user 1812 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.59 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.59 spid66 Folder 7 is not assigned to user 1812 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.60 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.60 spid66 Folder 7 is not assigned to user 1812 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.60 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.60 spid66 Folder 7 is not assigned to user 1812 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.62 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.62 spid66 Folder 7 is not assigned to user 1812 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.62 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.62 spid66 Folder 7 is not assigned to user 1812 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.62 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.62 spid66 Folder 7 is not assigned to user 1812 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.62 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.62 spid66 Folder 7 is not assigned to user 1812 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.64 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.64 spid66 Folder 7 is not assigned to user 1812 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.64 spid66 Error: 60132, Severity: 15, State: 1
This section shows from 4am onwards
2007-01-13 04:05:09.87 spid71 Error: 60132, Severity: 15, State: 1 2007-01-13 04:05:09.87 spid71 Folder 7 is not assigned to user 613 Proc Name: ags_workflow_sess_count. 2007-01-13 04:05:13.40 spid75 Error: 60132, Severity: 15, State: 1 2007-01-13 04:05:13.40 spid75 Folder 7 is not assigned to user 660 Proc Name: ags_workflow_sess_count. 2007-01-13 04:05:16.15 spid77 Error: 60132, Severity: 15, State: 1 2007-01-13 04:05:16.15 spid77 Folder 7 is not assigned to user 660 Proc Name: ags_workflow_sess_count. 2007-01-13 04:05:17.29 spid61 Error: 60132, Severity: 15, State: 1 2007-01-13 04:05:17.29 spid61 Folder 7 is not assigned to user 660 Proc Name: ags_workflow_sess_count. 2007-01-13 04:05:18.12 spid69 Error: 60132, Severity: 15, State: 1 2007-01-13 04:05:18.12 spid69 Folder 7 is not assigned to user 63 Proc Name: ags_workflow_sess_count. 2007-01-13 04:10:28.81 spid51 Unable to load OLE/DB initialization service. 2007-01-13 04:58:12.21 server Error: 17883, Severity: 1, State: 0 2007-01-13 04:58:12.21 server The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x250A5C68. 2007-01-13 04:59:12.21 server Error: 17883, Severity: 1, State: 0 2007-01-13 04:59:12.21 server The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x250A5C68. 2007-01-13 05:00:12.21 server Error: 17883, Severity: 1, State: 0 2007-01-13 05:00:12.21 server The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x250A5C68. 2007-01-13 05:01:12.21 server Error: 17883, Severity: 1, State: 0 2007-01-13 05:01:12.21 server The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x250A5C68. 2007-01-13 05:02:12.21 server Error: 17883, Severity: 1, State: 0 2007-01-13 05:02:12.21 server The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x250A5C68. 2007-01-13 05:03:12.21 server Error: 17883, Severity: 1, State: 0
Hi Guru,Our HR sql 2000 production server is 800.760 built (SP3a) with 2GB ofRAM and 2 CPU hiper threading. This server is very low activity whereprocessor runs average 1-3 during the day. However, in the last twomonths, I've seen the following message occurred a few times on thisserver.Error: 17883, Severity: 1, State: 0The Scheduler 2 appears to be hung. SPID 0, ECID 0, UMS Context0x0381F660.I did extensive research and read both KB 815056 and 10885 but I couldnot correlate these KBs in to my issue. The reason is, I don't thinkour server is very busy to cause the checkpoint process to be delayed.The database keeps growing only 5-10MB in a week and I allocated thespace during off hour.What is the solution to fix this issue? Will I fix this issue byapplying the hotfix MS03-031?Thanks so much,Silaphet,
hi,everyone!I meet strange thing when I create a maintance job for backup alldatabase.and this backup job just stands "Executing job step '(step 1)'" for averylong time .SQL server startup account is this account for network bakcupafter I issue sp_databases sp, I found my full database size only 1GB,and I found my backupfile is complete.I view event log and Sql server Log and no found error!why do it take so long time, but stands 'executing ' status and neverfinish.help me!best regards!
My SQL CE Replication is hanging during a full CreateDatabase download. My SDF file is around 13 MB loaded onto an SDIO card. I need to be able to blow away the SDF file and fully reload from remote locations.
I get all of the table 'upload' and 'download' async events and it appears to be working but then just hangs until I guess the device runs out of memory. I get several beeps and then the hourglass. After a reboot, the DB file is not usable.
I've been using SQL CE 3.0 for awhile and it has worked ok in the past. I upgraded to SQL CE 3.5 but I see the same behavior.
My replication data consists of about 30K inserts across about 30 tables.
Any ideas on how to debug a problem like this? I'm really stuck with this bug.
I have a job that FTP's a backup file offsite daily. Sometime the job hangs (for undetermined reason). The job never terminates. Is there ar way to force termination of the job after so many minutes? This is a Operating System command job.
I see the parameter "Shutdown Timeout Interval" in SQL Server Agent - currently set to 15 seconds. This apparently is not used or not working, as my job was hung for several days and it was not detected. The job runs daly. Since the prior run was "still running - hung", it didn't start, causing my offsite backups to fail following the job hang.
How can I force termination of a job if it doesn't complete in so many minutes?
When I attempt to move a package to another server, or sometimes just try to open it on another server, I get the useless message "The parameter is incorrect". All of my connections are valid on the new machine, and even if they weren't I should be able to correct them in design mode on the new server. This is REALLY making it difficult to design a package on the development server, then move it into production.
Could someone please tell me what to do with it and what might be causing it? The packages were fine yesterday.
Here is the error message:
[Script Component 1 1 [3941]] Error: System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {A138CF39-2CAE-42C2-ADB3-022658D79F2F} failed due to the following error: 80040154. at Microsoft.VisualBasic.Vsa.VsaEngine.CreateEngine() at Microsoft.VisualBasic.Vsa.VsaEngine.CheckEngine() at Microsoft.VisualBasic.Vsa.VsaEngine.set_RootMoniker(String value) at Microsoft.SqlServer.VSAHosting.Runtime.CreateVsaEngine() at Microsoft.SqlServer.Dts.Pipeline.ScriptRuntime..ctor(String projectName, String moniker, String language, Boolean showErrorUI) at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.CreateUserComponent()
Hi, excuse me if this problem has been discussed before!
We handle the addmittance in our university with IIS 4.0 and MS SQL Server 6.5 ... a group of 12 operators keep the server busy entering the information about students... I run backup of the hole database on every 1 hour in order to have a recent copy of the date base in case the disk fail (we had bad luck with a quantum HDD few weeks ago). The problems begun when the data base got to 18 MEGs and at about 32 connections to the SQL server when the dump finish the server goes out...
Anyone heard about this before and how to handle it? Yours truly WarJo
