scheduler brings down the system?

I am hoping this is something simple, a security piece I've messed up.

When I run my dts package manually I get no errors and sucessful completion of each step. So I set my SQL Agent to run thepackage 15 minutes after every hour between 5am and 5pm, these being 15 minutes after the times the new data files are dropped to me.

But instead of running the package it disconnects all the remote desktop users and fails. When remote users can get back on we are faced with a system has recovered from a serious error message. The error message posted to the event logs is empty though.

Any one have any ideas?

We are running MS Server 2003 and SQL Server 2000

Thanks,

Carrie

It is not clear what is happening. When you say remote desktop users are you referring to RDP connections or Terminal Server sessions to your Windows Server. If so then it is not clear how this is a SQL Server issue.

If you are referring to SQL Server users then does the SQL Server service crash when you run the package?

Did you check the SQL Server error logs, windows eventlogs and SQL Server log directory for dump files?

Can you also repro the problem on another SQL Server with your database and package? If it is specific to this server, did you check for database corruptions or other hardware related issues?

Do you have the latest service pack installed on the SQL Server? If not, you should install it on a repro system and test your package again. If the problem doesn't happen then the bug you encountered has been fixed in a later service pack or hotfix.

If you are running the latest service pack and you can repro this problem on other SQL Servers with same package/database then it is a bug in SQL Server. You can file one with the repro details at http://connect.microsoft.com.

Scheduled Notifications

Hi , I'm having one code for Scheduled Notification services, it's running without errors but there is no output

<SubscriptionClasses>
<SubscriptionClass>
<SubscriptionClassName>ScheduledSubscriptions</SubscriptionClassName>
<Schema>
<Field>
<FieldName>DeviceName</FieldName>
<FieldType>nvarchar(255)</FieldType>
</Field>
<Field>
<FieldName>SubscriberLocale</FieldName>
<FieldType>nvarchar(5)</FieldType>
</Field>
<Field>
<FieldName>Prescriptionid</FieldName>
<FieldType>int</FieldType>
</Field>
<Field>
<FieldName>status</FieldName>
<FieldType>nvarchar(50)</FieldType>
</Field>
</Schema>
<FileGroup>DEFAULT</FileGroup>
<ScheduledRules>
<ScheduledRule>
<RuleName>ScheduledSubscriptionsRule</RuleName>
<Action>

INSERT INTO SchedPrescriptionNotifications
( SubscriberId,DeviceName,SubscriberLocale,Prescriptionid,status )
SELECT S.SubscriberId, S.DeviceName,
S.SubscriberLocale, C.Prescriptionid, C.status
FROM SchedPrescriptionSubscriptions S , ScheduledEventsChron C
WHERE C.Prescriptionid= S.Prescriptionid
AND C.status = S.status

INSERT SchedSubscriptionChron
(SubscriberId, Prescriptionid, status)
SELECT S.SubscriberId, S.Prescriptionid, C.status
FROM SchedPrescriptionSubscriptions S JOIN ScheduledEventsChron C
ON S.Prescriptionid= C.Prescriptionid
</Action>
<ActionTimeout>PT30M</ActionTimeout>
</ScheduledRule>
</ScheduledRules>
</SubscriptionClass>
</SubscriptionClasses>
and

my C#.net coding is

if (nsSubscription.HasTimedRule)

{

nsSubscription.ScheduleRecurrence = "FREQ=DAILY;";

nsSubscription.ScheduleStart="20070326T072720";

}

i need to know whther the format of Schedulestart property is correct...

Hi , I'm having one code for Scheduled Notification services, it's running without errors but i don't get any output

<SubscriptionClasses>
<SubscriptionClass>
<SubscriptionClassName>ScheduledSubscriptions</SubscriptionClassName>
<Schema>
<Field>
<FieldName>DeviceName</FieldName>
<FieldType>nvarchar(255)</FieldType>
</Field>
<Field>
<FieldName>SubscriberLocale</FieldName>
<FieldType>nvarchar(5)</FieldType>
</Field>
<Field>
<FieldName>Prescriptionid</FieldName>
<FieldType>int</FieldType>
</Field>
<Field>
<FieldName>status</FieldName>
<FieldType>nvarchar(50)</FieldType>
</Field>
</Schema>
<FileGroup>DEFAULT</FileGroup>
<ScheduledRules>
<ScheduledRule>
<RuleName>ScheduledSubscriptionsRule</RuleName>
<Action>

INSERT INTO SchedPrescriptionNotifications
( SubscriberId,DeviceName,SubscriberLocale,Prescriptionid,status )
SELECT S.SubscriberId, S.DeviceName,
S.SubscriberLocale, C.Prescriptionid, C.status
FROM SchedPrescriptionSubscriptions S , ScheduledEventsChron C
WHERE C.Prescriptionid= S.Prescriptionid
AND C.status = S.status

INSERT SchedSubscriptionChron
(SubscriberId, Prescriptionid, status)
SELECT S.SubscriberId, S.Prescriptionid, C.status
FROM SchedPrescriptionSubscriptions S JOIN ScheduledEventsChron C
ON S.Prescriptionid= C.Prescriptionid
</Action>
<ActionTimeout>PT30M</ActionTimeout>
</ScheduledRule>
</ScheduledRules>
</SubscriptionClass>
</SubscriptionClasses>
and

my C#.net coding is

if (nsSubscription.HasTimedRule)

{

nsSubscription.ScheduleRecurrence = "FREQ=DAILY;";

nsSubscription.ScheduleStart="20070326T072720";

}

i need to know whther the format of ScheduleStart property is correct...

|||Hi Subathra -

Here's a link that may help. Look at the timezone component.

http://msdn2.microsoft.com/en-us/library/ms171385.aspx

I'm not sure I follow the match rule logic so I cannot comment on that part. You can do more investigation by looking into the underlying tables to see if notifications were actually produced but just not delivered.

HTH...

Joe

Scheduled Job Running MS Access in Background not Foreground

We had a scheduled job, within it a step would run an Access app. Before Access would pop up, and if it errors out it will shut itself down and the job would see it as an error and try and rerun the Access app.
After migrating to a new server (install is identical except for hardware), the Access app when called from a job will run in the background, meaning you can only see that it's running by going into the Task Manager and going into the Processes tab. Also
now when Access errors out, (in the background there is a dialog box indicating an error in Access and someone has to go and click ok, which can't be done, since Access is running as a background process) it will sit there waiting for someone to click OK
on the error dialog box. The scheduled job will just hang there since the job thinks Access is still running.
Does anyone know how to get the job to NOT run the Access app in the background and to know when Access errors out?
Can't you just write code to catch the error in the Access database?
"ckaneko" <anonymous@.discussions.microsoft.com> wrote in message
news:DB4CB092-B1B9-4388-9780-EFDCFC9052DB@.microsoft.com...
> We had a scheduled job, within it a step would run an Access app. Before
Access would pop up, and if it errors out it will shut itself down and the
job would see it as an error and try and rerun the Access app.
> After migrating to a new server (install is identical except for
hardware), the Access app when called from a job will run in the background,
meaning you can only see that it's running by going into the Task Manager
and going into the Processes tab. Also now when Access errors out, (in the
background there is a dialog box indicating an error in Access and someone
has to go and click ok, which can't be done, since Access is running as a
background process) it will sit there waiting for someone to click OK on the
error dialog box. The scheduled job will just hang there since the job
thinks Access is still running.
> Does anyone know how to get the job to NOT run the Access app in the
background and to know when Access errors out?

Scheduled Job Running MS Access in Background not Foreground

We had a scheduled job, within it a step would run an Access app. Before Ac
cess would pop up, and if it errors out it will shut itself down and the job
would see it as an error and try and rerun the Access app.
After migrating to a new server (install is identical except for hardware),
the Access app when called from a job will run in the background, meaning yo
u can only see that it's running by going into the Task Manager and going in
to the Processes tab. Also
now when Access errors out, (in the background there is a dialog box indicat
ing an error in Access and someone has to go and click ok, which can't be do
ne, since Access is running as a background process) it will sit there waiti
ng for someone to click OK
on the error dialog box. The scheduled job will just hang there since the j
ob thinks Access is still running.
Does anyone know how to get the job to NOT run the Access app in the backgro
und and to know when Access errors out?Can't you just write code to catch the error in the Access database?
"ckaneko" <anonymous@.discussions.microsoft.com> wrote in message
news:DB4CB092-B1B9-4388-9780-EFDCFC9052DB@.microsoft.com...
> We had a scheduled job, within it a step would run an Access app. Before
Access would pop up, and if it errors out it will shut itself down and the
job would see it as an error and try and rerun the Access app.
> After migrating to a new server (install is identical except for
hardware), the Access app when called from a job will run in the background,
meaning you can only see that it's running by going into the Task Manager
and going into the Processes tab. Also now when Access errors out, (in the
background there is a dialog box indicating an error in Access and someone
has to go and click ok, which can't be done, since Access is running as a
background process) it will sit there waiting for someone to click OK on the
error dialog box. The scheduled job will just hang there since the job
thinks Access is still running.
> Does anyone know how to get the job to NOT run the Access app in the
background and to know when Access errors out?

Scheduled Job Running MS Access in Background not Foreground

We had a scheduled job, within it a step would run an Access app. Before Access would pop up, and if it errors out it will shut itself down and the job would see it as an error and try and rerun the Access app
After migrating to a new server (install is identical except for hardware), the Access app when called from a job will run in the background, meaning you can only see that it's running by going into the Task Manager and going into the Processes tab. Also now when Access errors out, (in the background there is a dialog box indicating an error in Access and someone has to go and click ok, which can't be done, since Access is running as a background process) it will sit there waiting for someone to click OK on the error dialog box. The scheduled job will just hang there since the job thinks Access is still running
Does anyone know how to get the job to NOT run the Access app in the background and to know when Access errors out?Can't you just write code to catch the error in the Access database?
"ckaneko" <anonymous@.discussions.microsoft.com> wrote in message
news:DB4CB092-B1B9-4388-9780-EFDCFC9052DB@.microsoft.com...
> We had a scheduled job, within it a step would run an Access app. Before
Access would pop up, and if it errors out it will shut itself down and the
job would see it as an error and try and rerun the Access app.
> After migrating to a new server (install is identical except for
hardware), the Access app when called from a job will run in the background,
meaning you can only see that it's running by going into the Task Manager
and going into the Processes tab. Also now when Access errors out, (in the
background there is a dialog box indicating an error in Access and someone
has to go and click ok, which can't be done, since Access is running as a
background process) it will sit there waiting for someone to click OK on the
error dialog box. The scheduled job will just hang there since the job
thinks Access is still running.
> Does anyone know how to get the job to NOT run the Access app in the
background and to know when Access errors out?

Schedule and Delivery Processor errors

Hi all,

We're running into some random errors on our reporting server (Windows Server 2003, SQL Server 2000 Enterprise). In the application logs, we're seeing several Schedule and Delivery Processor errors (ID 108)...one for each processing extension (FileShare, Excel, HTML, etc.). In the security logs, at the same time of day, are several failure audits with the following info:

EventID: 680
User: NT AUTHORITY\SYSTEM
Description: Logon attempt by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0. Logon account: sqluser.

The odd thing is that the schedules that are failing run perfectly about 98% of the time. Once every few weeks we have a situation like this and all of our reports (approximately 200 of them...mostly Excel, all of them sent via E-Mail) fail.

Any ideas as to what might be causing this, and why it would only happen occasionally? Any help would be appreciated! Thanks!

-Brian
http://searchwindowssecurity.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid45_gci1007131_tax299886,00.html?bucket=ETA&topic=299886|||Thanks Greg, however this link seems to relate to making sure the ASP.NET account has the appropriate permissions on both the web server and the database. In my situation, the account (sqluser) has the correct permissions for the database. The database and report server/IIS are both on the same box if that matters.

In fact, and this is what is really confusing me, everything works just fine for weeks on end...then without warning I start getting these errors and the jobs fail. Same account, same reports, same schedules, same recipients...nothing has changed, yet something has caused these errors. Any other thoughts?
|||

Do you think it could be a DOS attack?

Is it happening the same day of the week? Same time of day?

How many "accounts" are accessing the server? Some versions of SQL have a max amount of connections before it denies access.