Showing posts with label time. Show all posts
Showing posts with label time. Show all posts

Thursday, March 29, 2012

Error 18456 Login failed for user 'distributor_admin'

Hello,
Each time I try to configure my SQL 2000 server as a distributor using the
Wizard I get the following error message:
Error 18456 Login failed for user 'distributor_admin'
Can anyone help with this?
Regards
Dave
are you using a remote distributor?
If do your Publisher has the incorrect administrative link password. Connect
to your Publisher in EM. Go to Tools, replication, configure publishers,
Subscribers, and distributor, and click on the Publisher's tab. In the
Administrative link password dialog enter the administrative link password.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Dave" <dave.cartlidge@.gmail.com> wrote in message
news:9401f534.0407170459.625c7ba7@.posting.google.c om...
> Hello,
> Each time I try to configure my SQL 2000 server as a distributor using the
> Wizard I get the following error message:
> Error 18456 Login failed for user 'distributor_admin'
> Can anyone help with this?
> Regards
> Dave
|||Check to make sure that the computer you are trying to access which has the
group 'distributor_admin' actually has the administrative access it
requires, both in the security file for the server and in the user security
for the individual database. If you play with file permissions, you may
want to check those as well. If you don't work with the file permissions
forget I added this. If you are on a network and the network administrator
has not enabled the administrator rights for the 'distributor_admin' group,
you may need to ask the administrator to grant the permission over the
network.
Giac
"Dave" <dave.cartlidge@.gmail.com> wrote in message
news:9401f534.0407170459.625c7ba7@.posting.google.c om...
> Hello,
> Each time I try to configure my SQL 2000 server as a distributor using the
> Wizard I get the following error message:
> Error 18456 Login failed for user 'distributor_admin'
> Can anyone help with this?
> Regards
> Dave
|||Sorry, I should have given a bit more info. I'm trying to set up one
machine to replicate the contents of one table to a second machine
(not located in the same place)
I figured I needed to set Machine A up as a distibutor and then allow
Machine B to have a subscription.
I don't have the 'Publisher's tab' as I have not configured it to be a
publisher yet, this I can't do as I get the aforementioned error.
I can't see a login 'distributor_admin' in Ent Mgr.
I was assuming (maybe incorrectly) that I don't need to do anything on
Machine B in order to be able to set up the publishing side on Machine
A.
Hope this helps you to help me
Dave
|||Dave,
You're in over my head, but it sounds like a permissions error.
If you go to services and select the properties of your server, you'll see
the account that the machine starts in. Check to see that account is
someone who is in the 'distributor_admin' group. You can browse for it
there - and both sides need to be members of that group since it appears to
have the permission to run the transaction.
Hope this helps.
Giac
"Dave" <dave.cartlidge@.gmail.com> wrote in message
news:9401f534.0407180039.1d325c91@.posting.google.c om...
> Sorry, I should have given a bit more info. I'm trying to set up one
> machine to replicate the contents of one table to a second machine
> (not located in the same place)
> I figured I needed to set Machine A up as a distibutor and then allow
> Machine B to have a subscription.
> I don't have the 'Publisher's tab' as I have not configured it to be a
> publisher yet, this I can't do as I get the aforementioned error.
> I can't see a login 'distributor_admin' in Ent Mgr.
> I was assuming (maybe incorrectly) that I don't need to do anything on
> Machine B in order to be able to set up the publishing side on Machine
> A.
> Hope this helps you to help me
> Dave
|||"Giacomo" <anonymous@.msnewsgroups.com> wrote in message news:<#HHn#qLbEHA.3792@.TK2MSFTNGP09.phx.gbl>...
> Dave,
> You're in over my head, but it sounds like a permissions error.
> If you go to services and select the properties of your server, you'll see
> the account that the machine starts in. Check to see that account is
> someone who is in the 'distributor_admin' group. You can browse for it
> there - and both sides need to be members of that group since it appears to
> have the permission to run the transaction.
> Hope this helps.
> Giac
I don't have a 'distributor_admin' group in either Ent Mgr or Computer Manager.
|||Dave,
see if this link applies to you - there are 2 workarounds suggested, one of
which is the same as Hilary's first reply.
http://support.microsoft.com/default...;en-us;Q225129
HTH,
Paul Ibison
|||Thanks for the suggestions. I had set up an alias sql server as the
default had been set up as (local) which would not work.
In the end I just removed and re-added the only registration so that
it had the same name as the server and all worked fine.
Thanks again
sql

Tuesday, March 27, 2012

Error 17883 The Scheduler 0 appears to be hung

I get this message every time i try to take a backup. Both manually and via
the Scheduler. What is the problem?
--
Best wishesSee if these help:
http://support.microsoft.com/kb/815056
http://support.microsoft.com/kb/810885
-oj
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:289BEB45-7BDF-47DD-937F-0425DB689549@.microsoft.com...
>I get this message every time i try to take a backup. Both manually and via
> the Scheduler. What is the problem?
> --
> Best wishes|||Well I do not know. The funny thing is that I get the same message if I
reboot the system ansd take a manual backup. The system get stuck takes
almost all of the processor power. I have then to kill enterprise manager.
Then the process lies there with the backup and I can not kill it. It
diseappears only with reboot.The reboot at that time is also extremely
difficult you have to shut off by the power button as the whole machine is
stucked. I then see the message in the error log.
If I take the backup via the scheduler nothing happends it only adds
processes until next reboot and then I see the message.
The system ran fine for over a month and then this suddenly happened. The
machine by the way is a two processor Dell.
"oj" wrote:

> See if these help:
> http://support.microsoft.com/kb/815056
> http://support.microsoft.com/kb/810885
>
> --
> -oj
>
> "Mats" <Mats@.discussions.microsoft.com> wrote in message
> news:289BEB45-7BDF-47DD-937F-0425DB689549@.microsoft.com...
>
>|||Backups should not spike your CPUs. My guess is that you have another
problem on this server and it's hanging SQL. You should engage MS support
and have them review 17883 minidumps. You need to be on build 818 (MS03-031
patch) or higher to generate good minidumps.
Adrian
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:3EB13F27-EDF3-47E6-9CBB-94A8960CAC20@.microsoft.com...[vbcol=seagreen]
> Well I do not know. The funny thing is that I get the same message if I
> reboot the system ansd take a manual backup. The system get stuck takes
> almost all of the processor power. I have then to kill enterprise manager.
> Then the process lies there with the backup and I can not kill it. It
> diseappears only with reboot.The reboot at that time is also extremely
> difficult you have to shut off by the power button as the whole machine is
> stucked. I then see the message in the error log.
> If I take the backup via the scheduler nothing happends it only adds
> processes until next reboot and then I see the message.
> The system ran fine for over a month and then this suddenly happened. The
> machine by the way is a two processor Dell.
> "oj" wrote:
>|||I have just installed 818. How do I do a minidump then?
"Adrian Zajkeskovic" wrote:

> Backups should not spike your CPUs. My guess is that you have another
> problem on this server and it's hanging SQL. You should engage MS support
> and have them review 17883 minidumps. You need to be on build 818 (MS03-03
1
> patch) or higher to generate good minidumps.
> Adrian
>
> "Mats" <Mats@.discussions.microsoft.com> wrote in message
> news:3EB13F27-EDF3-47E6-9CBB-94A8960CAC20@.microsoft.com...
>
>|||Backups should not cause this but could trigger behavior that you don't
expect.
Perhaps this will help.
The 17883 is a generic message (often referred to as the service engine
light) indicating that the UMS scheduling mechanism has detected a
worker that is not properly yielding to other workers within SQL Server.
The message was added in SQL 2000 SP3 but a later build (8.00.818
Security patch) is required to get extended diags. When the error is
first encountered a mini-dump is generated capturing the state of the
non-yielding thread. The mini-dump can be used by SQL support to
determine where in the code the SQL Server is non-yielding.
Since SP3 Microsoft has corrected or protected the engine in approx 25
places in the SQL Server code base that may not yield to other workers
properly, diminishing concurrency of the database engine. That is why
you find so many references to upgrade to a later QFE. I generally
recommend going to 8.00.997 to obtain the majority of these corrections
if you have encountered the 17883 on SP3 (8.00.760) where the mini dump
is not generated so the cause can not be determined.
Future versions of SQL Server are working to make these mini-dumps
Watson enabled so they can be directly submitted to the Watson site and
automated responses generated.
The problems have ranged from SQL Server bugs to getting stuck in API
calls that should return quickly but from time to time do not. For
example if we make a call to a security API and the PDC/BDC does not
return a response for 60 seconds (unusual and unexpected) the worker
ties up the specific UMS scheduler.
Do not be mislead, the worker is still an NT thread or fiber and must
honor NT scheduling. The design of SQL Server (UMS scheduling) is such
that only a single worker on a given scheduler can be scheduled by the
OS at any point in time. As each completes major phases or work
(natural yield points) the UMS scheduler coordinates the scheduling of
another worker on the same scheduler. It is rather simple, each worker
does a WaitForSingleObject with in INFINITE timeout so NT does not see
them as a viable worker to schedule. When a the active worker finishes
the unit of work it signals the next worker and waits on its event and
the cycle continues. Without going into more detail in this thread it
is a very simplistic non-preemptive system inside the SQL Server setup
to maximize resource usage and increase scalability. There is not need
for a lock waiter to do anything until the lock owner signals it to
execute so use the CPU for something more meaningful.
Bob Dorr
Microsoft SQL Server Escalation Support - Senior EE
*** Sent via Developersdex http://www.codecomments.com ***sql

Error 17883 The Scheduler 0 appears to be hung

I get this message every time i try to take a backup. Both manually and via
the Scheduler. What is the problem?
--
Best wishesSee if these help:
http://support.microsoft.com/kb/815056
http://support.microsoft.com/kb/810885
-oj
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:289BEB45-7BDF-47DD-937F-0425DB689549@.microsoft.com...
>I get this message every time i try to take a backup. Both manually and via
> the Scheduler. What is the problem?
> --
> Best wishes|||Well I do not know. The funny thing is that I get the same message if I
reboot the system ansd take a manual backup. The system get stuck takes
almost all of the processor power. I have then to kill enterprise manager.
Then the process lies there with the backup and I can not kill it. It
diseappears only with reboot.The reboot at that time is also extremely
difficult you have to shut off by the power button as the whole machine is
stucked. I then see the message in the error log.
If I take the backup via the scheduler nothing happends it only adds
processes until next reboot and then I see the message.
The system ran fine for over a month and then this suddenly happened. The
machine by the way is a two processor Dell.
"oj" wrote:
> See if these help:
> http://support.microsoft.com/kb/815056
> http://support.microsoft.com/kb/810885
>
> --
> -oj
>
> "Mats" <Mats@.discussions.microsoft.com> wrote in message
> news:289BEB45-7BDF-47DD-937F-0425DB689549@.microsoft.com...
> >I get this message every time i try to take a backup. Both manually and via
> > the Scheduler. What is the problem?
> > --
> > Best wishes
>
>|||Backups should not spike your CPUs. My guess is that you have another
problem on this server and it's hanging SQL. You should engage MS support
and have them review 17883 minidumps. You need to be on build 818 (MS03-031
patch) or higher to generate good minidumps.
Adrian
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:3EB13F27-EDF3-47E6-9CBB-94A8960CAC20@.microsoft.com...
> Well I do not know. The funny thing is that I get the same message if I
> reboot the system ansd take a manual backup. The system get stuck takes
> almost all of the processor power. I have then to kill enterprise manager.
> Then the process lies there with the backup and I can not kill it. It
> diseappears only with reboot.The reboot at that time is also extremely
> difficult you have to shut off by the power button as the whole machine is
> stucked. I then see the message in the error log.
> If I take the backup via the scheduler nothing happends it only adds
> processes until next reboot and then I see the message.
> The system ran fine for over a month and then this suddenly happened. The
> machine by the way is a two processor Dell.
> "oj" wrote:
>> See if these help:
>> http://support.microsoft.com/kb/815056
>> http://support.microsoft.com/kb/810885
>>
>> --
>> -oj
>>
>> "Mats" <Mats@.discussions.microsoft.com> wrote in message
>> news:289BEB45-7BDF-47DD-937F-0425DB689549@.microsoft.com...
>> >I get this message every time i try to take a backup. Both manually and
>> >via
>> > the Scheduler. What is the problem?
>> > --
>> > Best wishes
>>

Error 17883 The Scheduler 0 appears to be hung

I get this message every time i try to take a backup. Both manually and via
the Scheduler. What is the problem?
Best wishes
See if these help:
http://support.microsoft.com/kb/815056
http://support.microsoft.com/kb/810885
-oj
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:289BEB45-7BDF-47DD-937F-0425DB689549@.microsoft.com...
>I get this message every time i try to take a backup. Both manually and via
> the Scheduler. What is the problem?
> --
> Best wishes
|||Well I do not know. The funny thing is that I get the same message if I
reboot the system ansd take a manual backup. The system get stuck takes
almost all of the processor power. I have then to kill enterprise manager.
Then the process lies there with the backup and I can not kill it. It
diseappears only with reboot.The reboot at that time is also extremely
difficult you have to shut off by the power button as the whole machine is
stucked. I then see the message in the error log.
If I take the backup via the scheduler nothing happends it only adds
processes until next reboot and then I see the message.
The system ran fine for over a month and then this suddenly happened. The
machine by the way is a two processor Dell.
"oj" wrote:

> See if these help:
> http://support.microsoft.com/kb/815056
> http://support.microsoft.com/kb/810885
>
> --
> -oj
>
> "Mats" <Mats@.discussions.microsoft.com> wrote in message
> news:289BEB45-7BDF-47DD-937F-0425DB689549@.microsoft.com...
>
>
|||Backups should not spike your CPUs. My guess is that you have another
problem on this server and it's hanging SQL. You should engage MS support
and have them review 17883 minidumps. You need to be on build 818 (MS03-031
patch) or higher to generate good minidumps.
Adrian
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:3EB13F27-EDF3-47E6-9CBB-94A8960CAC20@.microsoft.com...[vbcol=seagreen]
> Well I do not know. The funny thing is that I get the same message if I
> reboot the system ansd take a manual backup. The system get stuck takes
> almost all of the processor power. I have then to kill enterprise manager.
> Then the process lies there with the backup and I can not kill it. It
> diseappears only with reboot.The reboot at that time is also extremely
> difficult you have to shut off by the power button as the whole machine is
> stucked. I then see the message in the error log.
> If I take the backup via the scheduler nothing happends it only adds
> processes until next reboot and then I see the message.
> The system ran fine for over a month and then this suddenly happened. The
> machine by the way is a two processor Dell.
> "oj" wrote:
|||I have just installed 818. How do I do a minidump then?
"Adrian Zajkeskovic" wrote:

> Backups should not spike your CPUs. My guess is that you have another
> problem on this server and it's hanging SQL. You should engage MS support
> and have them review 17883 minidumps. You need to be on build 818 (MS03-031
> patch) or higher to generate good minidumps.
> Adrian
>
> "Mats" <Mats@.discussions.microsoft.com> wrote in message
> news:3EB13F27-EDF3-47E6-9CBB-94A8960CAC20@.microsoft.com...
>
>
|||Backups should not cause this but could trigger behavior that you don't
expect.
Perhaps this will help.
The 17883 is a generic message (often referred to as the service engine
light) indicating that the UMS scheduling mechanism has detected a
worker that is not properly yielding to other workers within SQL Server.
The message was added in SQL 2000 SP3 but a later build (8.00.818
Security patch) is required to get extended diags. When the error is
first encountered a mini-dump is generated capturing the state of the
non-yielding thread. The mini-dump can be used by SQL support to
determine where in the code the SQL Server is non-yielding.
Since SP3 Microsoft has corrected or protected the engine in approx 25
places in the SQL Server code base that may not yield to other workers
properly, diminishing concurrency of the database engine. That is why
you find so many references to upgrade to a later QFE. I generally
recommend going to 8.00.997 to obtain the majority of these corrections
if you have encountered the 17883 on SP3 (8.00.760) where the mini dump
is not generated so the cause can not be determined.
Future versions of SQL Server are working to make these mini-dumps
Watson enabled so they can be directly submitted to the Watson site and
automated responses generated.
The problems have ranged from SQL Server bugs to getting stuck in API
calls that should return quickly but from time to time do not. For
example if we make a call to a security API and the PDC/BDC does not
return a response for 60 seconds (unusual and unexpected) the worker
ties up the specific UMS scheduler.
Do not be mislead, the worker is still an NT thread or fiber and must
honor NT scheduling. The design of SQL Server (UMS scheduling) is such
that only a single worker on a given scheduler can be scheduled by the
OS at any point in time. As each completes major phases or work
(natural yield points) the UMS scheduler coordinates the scheduling of
another worker on the same scheduler. It is rather simple, each worker
does a WaitForSingleObject with in INFINITE timeout so NT does not see
them as a viable worker to schedule. When a the active worker finishes
the unit of work it signals the next worker and waits on its event and
the cycle continues. Without going into more detail in this thread it
is a very simplistic non-preemptive system inside the SQL Server setup
to maximize resource usage and increase scalability. There is not need
for a lock waiter to do anything until the lock owner signals it to
execute so use the CPU for something more meaningful.
Bob Dorr
Microsoft SQL Server Escalation Support - Senior EE
*** Sent via Developersdex http://www.codecomments.com ***

Wednesday, March 21, 2012

Error 14266 - Is 11:59:59 PM not a valid time?

Hi,
I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
could not save the schedule.
An error "Error 14266: The specified '@.active_end_time' is invalid (valid
values are: before or after @.active_start_time). The job was not saved."
I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
11:59:59 PM not ?
Please help,
It sounds like this is from what you are selecting in the
daily frequency section when you schedule the job.
Without the details of this, I'd guess you are selecting
something like "occurs every 24 hours" with "starting at
11:59:59 PM" and "ending at 11:59:59 PM". That will give the
error you have.
If you want the job to run daily at 11:59:59 PM, select the
"occurs once at " option (the first one in the daily
frequency section). It will run once a day (or at whatever
interval you have set or want set in the Occurs section) at
11:59:59 PM.
-Sue
On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
<Julia@.discussions.microsoft.com> wrote:

>Hi,
>I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
>could not save the schedule.
>An error "Error 14266: The specified '@.active_end_time' is invalid (valid
>values are: before or after @.active_start_time). The job was not saved."
>I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
>11:59:59 PM not ?
>Please help,
|||Selecting "Occurrs Once At:" with a time of 11:59:59 PM will not work.
The scheduling wizard assumes that the end time is 11:59:59 PM. This is
why you get the error 14266. Enter any other time and it will work.
You can easily verify this by entering a different time and saving it.
Then right click on the associated job. Select "All Tasks > Generate
SQL Script...
A dialog box will appear "Generate SQL Script - SERVER NAME/JOB NAME"
Click on the preview button. Click on the copy button and paste into a
text editor. Search for "@.active_end_time"
you will see that it is set to 235959.
Sue Hoegemeier Wrote:[vbcol=seagreen]
> It sounds like this is from what you are selecting in the
> daily frequency section when you schedule the job.
> Without the details of this, I'd guess you are selecting
> something like "occurs every 24 hours" with "starting at
> 11:59:59 PM" and "ending at 11:59:59 PM". That will give the
> error you have.
> If you want the job to run daily at 11:59:59 PM, select the
> "occurs once at " option (the first one in the daily
> frequency section). It will run once a day (or at whatever
> interval you have set or want set in the Occurs section) at
> 11:59:59 PM.
> -Sue
> On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
> <Julia@.discussions.microsoft.com> wrote:
> PM. I
> (valid
> saved."
bdatch
bdatch's Profile: http://www.msusenet.com/member.php?userid=675
View this thread: http://www.msusenet.com/t-3298150

Error 14266 - Is 11:59:59 PM not a valid time?

Hi,
I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
could not save the schedule.
An error "Error 14266: The specified '@.active_end_time' is invalid (valid
values are: before or after @.active_start_time). The job was not saved."
I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
11:59:59 PM not ?
Please help,It sounds like this is from what you are selecting in the
daily frequency section when you schedule the job.
Without the details of this, I'd guess you are selecting
something like "occurs every 24 hours" with "starting at
11:59:59 PM" and "ending at 11:59:59 PM". That will give the
error you have.
If you want the job to run daily at 11:59:59 PM, select the
"occurs once at " option (the first one in the daily
frequency section). It will run once a day (or at whatever
interval you have set or want set in the Occurs section) at
11:59:59 PM.
-Sue
On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
<Julia@.discussions.microsoft.com> wrote:

>Hi,
>I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
>could not save the schedule.
>An error "Error 14266: The specified '@.active_end_time' is invalid (valid
>values are: before or after @.active_start_time). The job was not saved."
>I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
>11:59:59 PM not ?
>Please help,|||Selecting "Occurrs Once At:" with a time of 11:59:59 PM will not work.
The scheduling wizard assumes that the end time is 11:59:59 PM. This is
why you get the error 14266. Enter any other time and it will work.
You can easily verify this by entering a different time and saving it.
Then right click on the associated job. Select "All Tasks > Generate
SQL Script...
A dialog box will appear "Generate SQL Script - SERVER NAME/JOB NAME"
Click on the preview button. Click on the copy button and paste into a
text editor. Search for "@.active_end_time"
you will see that it is set to 235959.
Sue Hoegemeier Wrote:[vbcol=seagreen]
> It sounds like this is from what you are selecting in the
> daily frequency section when you schedule the job.
> Without the details of this, I'd guess you are selecting
> something like "occurs every 24 hours" with "starting at
> 11:59:59 PM" and "ending at 11:59:59 PM". That will give the
> error you have.
> If you want the job to run daily at 11:59:59 PM, select the
> "occurs once at " option (the first one in the daily
> frequency section). It will run once a day (or at whatever
> interval you have set or want set in the Occurs section) at
> 11:59:59 PM.
> -Sue
> On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
> <Julia@.discussions.microsoft.com> wrote:
>
> PM. I
> (valid
> saved."
bdatch
---
bdatch's Profile: http://www.msmcse.ms/member.php?userid=675
View this thread: http://www.msmcse.ms/t-3298150

Error 14266 - Is 11:59:59 PM not a valid time?

Hi,
I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
could not save the schedule.
An error "Error 14266: The specified '@.active_end_time' is invalid (valid
values are: before or after @.active_start_time). The job was not saved."
I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
11:59:59 PM not ?
Please help,It sounds like this is from what you are selecting in the
daily frequency section when you schedule the job.
Without the details of this, I'd guess you are selecting
something like "occurs every 24 hours" with "starting at
11:59:59 PM" and "ending at 11:59:59 PM". That will give the
error you have.
If you want the job to run daily at 11:59:59 PM, select the
"occurs once at " option (the first one in the daily
frequency section). It will run once a day (or at whatever
interval you have set or want set in the Occurs section) at
11:59:59 PM.
-Sue
On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
<Julia@.discussions.microsoft.com> wrote:
>Hi,
>I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
>could not save the schedule.
>An error "Error 14266: The specified '@.active_end_time' is invalid (valid
>values are: before or after @.active_start_time). The job was not saved."
>I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
>11:59:59 PM not ?
>Please help,|||Selecting "Occurrs Once At:" with a time of 11:59:59 PM will not work
The scheduling wizard assumes that the end time is 11:59:59 PM. This i
why you get the error 14266. Enter any other time and it will work.
You can easily verify this by entering a different time and saving it
Then right click on the associated job. Select "All Tasks > Generat
SQL Script...
A dialog box will appear "Generate SQL Script - SERVER NAME/JOB NAME"
Click on the preview button. Click on the copy button and paste into
text editor. Search for "@.active_end_time"
you will see that it is set to 235959.
Sue Hoegemeier Wrote:
> It sounds like this is from what you are selecting in the
> daily frequency section when you schedule the job.
> Without the details of this, I'd guess you are selecting
> something like "occurs every 24 hours" with "starting at
> 11:59:59 PM" and "ending at 11:59:59 PM". That will give the
> error you have.
> If you want the job to run daily at 11:59:59 PM, select the
> "occurs once at " option (the first one in the daily
> frequency section). It will run once a day (or at whatever
> interval you have set or want set in the Occurs section) at
> 11:59:59 PM.
> -Sue
> On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
> <Julia@.discussions.microsoft.com> wrote:
> >Hi,
> >
> >I created a DTS package and wanted to schedule it to run at 11:59:5
> PM. I
> >could not save the schedule.
> >
> >An error "Error 14266: The specified '@.active_end_time' is invali
> (valid
> >values are: before or after @.active_start_time). The job was no
> saved."
> >
> >I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
> >11:59:59 PM not ?
> >
> >Please help
--
bdatc
----
bdatch's Profile: http://www.msusenet.com/member.php?userid=67
View this thread: http://www.msusenet.com/t-329815sql

Monday, March 19, 2012

Error 1222: Lock request time out period exceeded & SP4 ?

Hi,
After Spl Server 2000 w/ 16 G memory was applied SP4 and hotfix for AWE, it
got an error "Error 1222: Lock request time out period exceeded." while
running a stored procedure. It hung the process for much longer than normal.
It worked fine with SP3a. Is this error associated with SP4? Thanks.
Chuck
Check this KB http://support.microsoft.com/?kbid=888799
There are couple of fixes related to timing /performance issues
Thanks & Rate the Postings.
-Ravi-
"Chuck" wrote:

> Hi,
> After Spl Server 2000 w/ 16 G memory was applied SP4 and hotfix for AWE, it
> got an error "Error 1222: Lock request time out period exceeded." while
> running a stored procedure. It hung the process for much longer than normal.
> It worked fine with SP3a. Is this error associated with SP4? Thanks.
>
> Chuck

Error 1222: Lock request time out period exceeded & SP4 ?

Hi,
After Spl Server 2000 w/ 16 G memory was applied SP4 and hotfix for AWE, it
got an error "Error 1222: Lock request time out period exceeded." while
running a stored procedure. It hung the process for much longer than normal.
It worked fine with SP3a. Is this error associated with SP4? Thanks.
ChuckCheck this KB http://support.microsoft.com/?kbid=888799
There are couple of fixes related to timing /performance issues
--
Thanks & Rate the Postings.
-Ravi-
"Chuck" wrote:
> Hi,
> After Spl Server 2000 w/ 16 G memory was applied SP4 and hotfix for AWE, it
> got an error "Error 1222: Lock request time out period exceeded." while
> running a stored procedure. It hung the process for much longer than normal.
> It worked fine with SP3a. Is this error associated with SP4? Thanks.
>
> Chuck

Error 1222: Lock request time out period exceeded & SP4 ?

Hi,
After Spl Server 2000 w/ 16 G memory was applied SP4 and hotfix for AWE, it
got an error "Error 1222: Lock request time out period exceeded." while
running a stored procedure. It hung the process for much longer than normal.
It worked fine with SP3a. Is this error associated with SP4? Thanks.
ChuckCheck this KB http://support.microsoft.com/?kbid=888799
There are couple of fixes related to timing /performance issues
Thanks & Rate the Postings.
-Ravi-
"Chuck" wrote:

> Hi,
> After Spl Server 2000 w/ 16 G memory was applied SP4 and hotfix for AWE, i
t
> got an error "Error 1222: Lock request time out period exceeded." while
> running a stored procedure. It hung the process for much longer than norma
l.
> It worked fine with SP3a. Is this error associated with SP4? Thanks.
>
> Chuck

Error 1222 Lock Request time out period exceed

Hi, I'm getting this error when I tried to click on the Current Activity in
the Enterprise Manager. This is a SQL2000 running on Windows2000. Does
anyone know what causes this and how to fix it? I also get this error
sometimes when I run a crystal report in my C# application.
Thanks,
AlphaA transaction is being blocked to acquire a lock because another transaction
already locked the resource.
See "Customizing the Lock Time-out" in BOL.
AMB
"Alpha" wrote:
> Hi, I'm getting this error when I tried to click on the Current Activity in
> the Enterprise Manager. This is a SQL2000 running on Windows2000. Does
> anyone know what causes this and how to fix it? I also get this error
> sometimes when I run a crystal report in my C# application.
> Thanks,
> Alpha|||Do not use the GUI. Instead, get used to sp_who, sp_who2 or sp_who1 in Query
Analyzer.
"Alpha" <Alpha@.discussions.microsoft.com> wrote in message
news:16FC85B9-57C8-4906-AC47-3B9E826D9A79@.microsoft.com...
> Hi, I'm getting this error when I tried to click on the Current Activity
> in
> the Enterprise Manager. This is a SQL2000 running on Windows2000. Does
> anyone know what causes this and how to fix it? I also get this error
> sometimes when I run a crystal report in my C# application.
> Thanks,
> Alpha|||Thank you. That was very helpful.
"Alejandro Mesa" wrote:
> A transaction is being blocked to acquire a lock because another transaction
> already locked the resource.
> See "Customizing the Lock Time-out" in BOL.
>
> AMB
> "Alpha" wrote:
> > Hi, I'm getting this error when I tried to click on the Current Activity in
> > the Enterprise Manager. This is a SQL2000 running on Windows2000. Does
> > anyone know what causes this and how to fix it? I also get this error
> > sometimes when I run a crystal report in my C# application.
> >
> > Thanks,
> > Alpha

Error 1222 Lock request

I received the Error 1222 lock request time out period
when trying to open SQL Server Current Activity folder
under the Management folder to display locks.
This was caused by several locks.
This made it very difficult to resolve the locks without
the GUI.
What would cause the SQL Server GUI to be unable to
display the locks?
Thank You,
Mickey Autry
mautry@.ev1.netThat's know to happen when you have a lot of locks. You can
use Query Analyzer to execute sql statments and system
stored procedures to view the same info you look at in the
Current Activity part of Enterprise Manager. Check books
online for more information on sp_lock, sp_who, sp_who2 and
the sysprocesses table.
-Sue
On Tue, 23 Sep 2003 15:41:17 -0700, "Mickey"
<mautry@.ev1.net> wrote:
>I received the Error 1222 lock request time out period
>when trying to open SQL Server Current Activity folder
>under the Management folder to display locks.
>This was caused by several locks.
>This made it very difficult to resolve the locks without
>the GUI.
>What would cause the SQL Server GUI to be unable to
>display the locks?
>Thank You,
>Mickey Autry
>mautry@.ev1.net
>

error 1203 (SQL Server 6.5)

who knows's the cause of error: 'Caller of lock manager is trying to
unlock an unlocked object' . This error appears 200 time per second.
configuration: SQL 6.5 SP 5 / NT 4 SP6Check the article at
http://support.microsoft.com/default.aspx?scid=kb;en-us;175887, I think it
can help you.
--
Dejan Sarka, SQL Server MVP
FAQ from Neil & others at: http://www.sqlserverfaq.com
Please reply only to the newsgroups.
PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"marijn" <mklijs@.ons.nl> wrote in message
news:d35da914.0307280159.7819b3a7@.posting.google.com...
> who knows's the cause of error: 'Caller of lock manager is trying to
> unlock an unlocked object' . This error appears 200 time per second.
> configuration: SQL 6.5 SP 5 / NT 4 SP6

Wednesday, March 7, 2012

Error ?

Hi,
any ideas on this error '?
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 23-10-2003
Time: 21:45:44
User: N/A
Computer: LX1SQL004
Description:
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 68, ECID 0, UMS Context 0x03843DE8 Data:
0000: db 45 00 00 01 00 00 00 =DBE.....
0008: 0a 00 00 00 4c 00 58 00 ...L.X.
0010: 31 00 53 00 51 00 4c 00 1.S.Q.L.
0018: 30 00 30 00 34 00 00 00 0.0.4...
0020: 00 00 00 00 ...
Thanks in advance
Miguel CorreiaHave a look at this KB article
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B810885
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Miguel" <cmlcorreia@.netcabo.pt> wrote in message
news:084c01c39a1c$c9a680c0$a501280a@.phx.gbl...
Hi,
any ideas on this error '?
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 23-10-2003
Time: 21:45:44
User: N/A
Computer: LX1SQL004
Description:
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 68, ECID 0, UMS
Context 0x03843DE8
Data:
0000: db 45 00 00 01 00 00 00 ÛE.....
0008: 0a 00 00 00 4c 00 58 00 ...L.X.
0010: 31 00 53 00 51 00 4c 00 1.S.Q.L.
0018: 30 00 30 00 34 00 00 00 0.0.4...
0020: 00 00 00 00 ...
Thanks in advance
Miguel Correia|||Thanks a lot :)
>--Original Message--
>Have a look at this KB article
>http://support.microsoft.com/default.aspx?scid=3Dkb%3Ben-us%
3B810885
>-- >
>Allan Mitchell (Microsoft SQL Server MVP)
>MCSE,MCDBA
>www.SQLDTS.com
>I support PASS - the definitive, global community
>for SQL Server professionals - http://www.sqlpass.org
>
>
>"Miguel" <cmlcorreia@.netcabo.pt> wrote in message
>news:084c01c39a1c$c9a680c0$a501280a@.phx.gbl...
>Hi,
>any ideas on this error '?
>Event Type: Information
>Event Source: MSSQLSERVER
>Event Category: (2)
>Event ID: 17052
>Date: 23-10-2003
>Time: 21:45:44
>User: N/A
>Computer: LX1SQL004
>Description:
>Error: 17883, Severity: 1, State: 0
>The Scheduler 0 appears to be hung. SPID 68, ECID 0, UMS
>Context 0x03843DE8
>Data:
>0000: db 45 00 00 01 00 00 00 =DBE.....
>0008: 0a 00 00 00 4c 00 58 00 ...L.X.
>0010: 31 00 53 00 51 00 4c 00 1.S.Q.L.
>0018: 30 00 30 00 34 00 00 00 0.0.4...
>0020: 00 00 00 00 ...
>
>Thanks in advance
>Miguel Correia
>
>.
>

ERROR : Unexpected database error (-2147159548) 0x80040e21

When I tried an run my Example of "Reporting services" application for the
first time.I got an error "The report server cannot decrypt the symmetric
key............" for which I found a page dedicated to this problem and
the URL is
"http://support.microsoft.com/kb/842421" and when I tried the 3rd step of
"RSKeyMgmt -r InstallationID" . I received an error
"Unexpected database error (-2147159548) 0x80040e21" and the
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer>RSKeyMgmt -r f0b56789-7e84-4igh9-ath4-8rhf0c7a1777
Are you sure you want to delete this key (Y/N)? y
"Unexpected database error (-2147159548) 0x80040e21".
Kindly help!!!!!!!!!!Was wondering if you had any luck solving this problem? I've had the same
issue, and have been unable to resolve for the last 2 months.
Thanks
Marvin
"LazyBugger" wrote:
> When I tried an run my Example of "Reporting services" application for the
> first time.I got an error "The report server cannot decrypt the symmetric
> key............" for which I found a page dedicated to this problem and
> the URL is
> "http://support.microsoft.com/kb/842421" and when I tried the 3rd step of
> "RSKeyMgmt -r InstallationID" . I received an error
> "Unexpected database error (-2147159548) 0x80040e21" and the
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer>RSKeyMgmt -r f0b56789-7e84-4igh9-ath4-8rhf0c7a1777
> Are you sure you want to delete this key (Y/N)? y
> "Unexpected database error (-2147159548) 0x80040e21".
> Kindly help!!!!!!!!!!
>
>

Sunday, February 26, 2012

Error : Cannot specify an index or locking hint for a remote data source

We are migrating from sql 7 to sql 2000 and for the time
being leaving the database in sql 7 compatabiliy mode.
Some of the stored procedures reference the tables on a
linked server. The linked server is running sql 2000 and
the database is sql 2000.
When I run the following command
select * from linked_server.database.dbo.tablename (nolock)
I receive the following error
Cannot specify an index or locking hint for a remote data
source.
If I remove the () around nolock the statement runs.
The question(s) I have
1. Did I set something up wrong?
2. Without the () is the nolock still performing the same
function?
3. Assumining I did not error on the configuration, Why do
I receive this error now, and not before?
4. Any ideas to fix the problem without removing the ()?
Thanks in advance for any suggestions/ideas.
John WilliamsWithout the brackets around nolock, the SQL query engine is assigning the
word 'nolock' as an alias to your table in the select statement (i.e.
equivalent to 'as [nolock]').
R
"John Williams" <anonymous@.discussions.microsoft.com> wrote in message
news:27f3501c4636b$941fa990$a301280a@.phx.gbl...
> We are migrating from sql 7 to sql 2000 and for the time
> being leaving the database in sql 7 compatabiliy mode.
> Some of the stored procedures reference the tables on a
> linked server. The linked server is running sql 2000 and
> the database is sql 2000.
> When I run the following command
> select * from linked_server.database.dbo.tablename (nolock)
> I receive the following error
> Cannot specify an index or locking hint for a remote data
> source.
> If I remove the () around nolock the statement runs.
> The question(s) I have
> 1. Did I set something up wrong?
> 2. Without the () is the nolock still performing the same
> function?
> 3. Assumining I did not error on the configuration, Why do
> I receive this error now, and not before?
> 4. Any ideas to fix the problem without removing the ()?
> Thanks in advance for any suggestions/ideas.
> John Williams|||Can you not create a stored procedure on the remote data source that
specifies the hint?
--
http://www.aspfaq.com/
(Reverse address to reply.)
"John Williams" <anonymous@.discussions.microsoft.com> wrote in message
news:27f3501c4636b$941fa990$a301280a@.phx.gbl...
> We are migrating from sql 7 to sql 2000 and for the time
> being leaving the database in sql 7 compatabiliy mode.
> Some of the stored procedures reference the tables on a
> linked server. The linked server is running sql 2000 and
> the database is sql 2000.
> When I run the following command
> select * from linked_server.database.dbo.tablename (nolock)
> I receive the following error
> Cannot specify an index or locking hint for a remote data
> source.
> If I remove the () around nolock the statement runs.
> The question(s) I have
> 1. Did I set something up wrong?
> 2. Without the () is the nolock still performing the same
> function?
> 3. Assumining I did not error on the configuration, Why do
> I receive this error now, and not before?
> 4. Any ideas to fix the problem without removing the ()?
> Thanks in advance for any suggestions/ideas.
> John Williams|||I am not sure if I understand what you are asking? Are you
suggesting that the stored procedure we run on the server
that has the syntax.
Select & from linkerserver.database.dbo.table1 and instead
run a stored procedure on the linked server that
accomplishes the same thing? I can look into this as an
option.
Thanks...
>--Original Message--
>Can you not create a stored procedure on the remote data
source that
>specifies the hint?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>
>"John Williams" <anonymous@.discussions.microsoft.com>
wrote in message
>news:27f3501c4636b$941fa990$a301280a@.phx.gbl...
>> We are migrating from sql 7 to sql 2000 and for the time
>> being leaving the database in sql 7 compatabiliy mode.
>> Some of the stored procedures reference the tables on a
>> linked server. The linked server is running sql 2000 and
>> the database is sql 2000.
>> When I run the following command
>> select * from linked_server.database.dbo.tablename
(nolock)
>> I receive the following error
>> Cannot specify an index or locking hint for a remote
data
>> source.
>> If I remove the () around nolock the statement runs.
>> The question(s) I have
>> 1. Did I set something up wrong?
>> 2. Without the () is the nolock still performing the
same
>> function?
>> 3. Assumining I did not error on the configuration, Why
do
>> I receive this error now, and not before?
>> 4. Any ideas to fix the problem without removing the ()?
>> Thanks in advance for any suggestions/ideas.
>> John Williams
>
>.
>|||Thanks,
That an excellent point, so I am going to get unwanted
results by removing the (), I am concerned about locking
though, do you know since I cannot specify the nolock
hint, am I getting the benefit of (nolock) somehow?
>--Original Message--
>Without the brackets around nolock, the SQL query engine
is assigning the
>word 'nolock' as an alias to your table in the select
statement (i.e.
>equivalent to 'as [nolock]').
>R
>"John Williams" <anonymous@.discussions.microsoft.com>
wrote in message
>news:27f3501c4636b$941fa990$a301280a@.phx.gbl...
>> We are migrating from sql 7 to sql 2000 and for the time
>> being leaving the database in sql 7 compatabiliy mode.
>> Some of the stored procedures reference the tables on a
>> linked server. The linked server is running sql 2000 and
>> the database is sql 2000.
>> When I run the following command
>> select * from linked_server.database.dbo.tablename
(nolock)
>> I receive the following error
>> Cannot specify an index or locking hint for a remote
data
>> source.
>> If I remove the () around nolock the statement runs.
>> The question(s) I have
>> 1. Did I set something up wrong?
>> 2. Without the () is the nolock still performing the
same
>> function?
>> 3. Assumining I did not error on the configuration, Why
do
>> I receive this error now, and not before?
>> 4. Any ideas to fix the problem without removing the ()?
>> Thanks in advance for any suggestions/ideas.
>> John Williams
>
>.
>|||Yes, I think you will find that if you create a stored procedure on the
remote server, instead of running an ad hoc query locally, you will have
more freedom over transactions within the proc, locking hints, etc. You
should always be using stored procs as opposed to ad hoc statements
anyway...
--
http://www.aspfaq.com/
(Reverse address to reply.)
<anonymous@.discussions.microsoft.com> wrote in message
news:274bb01c46371$b02b52a0$a501280a@.phx.gbl...
> I am not sure if I understand what you are asking? Are you
> suggesting that the stored procedure we run on the server
> that has the syntax.
> Select & from linkerserver.database.dbo.table1 and instead
> run a stored procedure on the linked server that
> accomplishes the same thing? I can look into this as an
> option.
> Thanks...
>
> >--Original Message--
> >Can you not create a stored procedure on the remote data
> source that
> >specifies the hint?
> >
> >--
> >http://www.aspfaq.com/
> >(Reverse address to reply.)
> >
> >
> >
> >
> >"John Williams" <anonymous@.discussions.microsoft.com>
> wrote in message
> >news:27f3501c4636b$941fa990$a301280a@.phx.gbl...
> >> We are migrating from sql 7 to sql 2000 and for the time
> >> being leaving the database in sql 7 compatabiliy mode.
> >> Some of the stored procedures reference the tables on a
> >> linked server. The linked server is running sql 2000 and
> >> the database is sql 2000.
> >>
> >> When I run the following command
> >> select * from linked_server.database.dbo.tablename
> (nolock)
> >>
> >> I receive the following error
> >> Cannot specify an index or locking hint for a remote
> data
> >> source.
> >>
> >> If I remove the () around nolock the statement runs.
> >>
> >> The question(s) I have
> >>
> >> 1. Did I set something up wrong?
> >> 2. Without the () is the nolock still performing the
> same
> >> function?
> >> 3. Assumining I did not error on the configuration, Why
> do
> >> I receive this error now, and not before?
> >> 4. Any ideas to fix the problem without removing the ()?
> >>
> >> Thanks in advance for any suggestions/ideas.
> >>
> >> John Williams
> >
> >
> >.
> >

Friday, February 24, 2012

Error "Lock Request Time Out" when deleting a record

Hi all,
I'm trying to delete one record from application but I get an Error :
"Lock request time out periode exceeded (37000) was experienced when
deleting a record from dbo.fe9srjh".
I'm using SQL Server 2000 SP3. What should I do ? Thank's a lot ..
rgds,
yuliusSomeone has a conflicting lock which cases your LOCK_TIMEOUT setting (set by
the programmer of your
client application) to time out. Use sp_who, sp_who2, sp_lock, Current Activ
ity in EM to find out
who is locking the resource. When you find that person, talk to the vendor o
f the application that
the person is using and have them figure out why the long lived lock.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Yulius Sutanto" <ysutanto@.atlas-sp.com> wrote in message
news:1130208619.276385.284300@.f14g2000cwb.googlegroups.com...
> Hi all,
> I'm trying to delete one record from application but I get an Error :
> "Lock request time out periode exceeded (37000) was experienced when
> deleting a record from dbo.fe9srjh".
> I'm using SQL Server 2000 SP3. What should I do ? Thank's a lot ..
> rgds,
> yulius
>

Error - The report server cannot decrypt the symmetric key?

SSRS had been working fine on my comp till the time i insatlled VS 2005. I have started getting following error since VS2005 install

The report server cannot decrypt the symmetric key used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content and then restart the service. Check the documentation for more information. (rsReportServerDisabled) Get Online Help
Bad Data.

Why does this error cropped and how can i fix it? I am using SQL Server 2000.

Thanks

It cropped because VS.NET 2005 did aspnet_regiis.exe. Assuming that you have backed up your encryption key (you did right?), you can use the Reporting Services Configuration utility to restore it. If no backup, do:

"C:\Program Files\Microsoft SQL Server\90\Tools\Binn\RsKeyMgmt.exe" -d

Then, go to the Report Manager and reset the connection string in all data sources.

|||if the above command is executed, it seems like it will delete all the reporting data also.
is that correct?|||Incorrect. Only the ecrypted information will be nuked, i.e. connection credentials, connection strings, and any secure information stored in subscriptions – by default this is only username & password in File Share delivery extension.|||So the actual data is never encrypted in the Reporting Services db? Then in case I never made a backup of the encryption keys, and I have to delete it now, I wouldn't be losing any data; just
connection strings etc. Where do I go about changing these connection strings? Again a newbie question for you, what is the File Share delivery extension?

Thanks|||Excluding snapshots, the actual data is not stored in the report catalog. Yes, you will loose only the data source credentials. You can go to the Report Manager to change them. FSE is about delivering subsribed reports (users can subscribe to reports believe it or not) to a network file share.

Sunday, February 19, 2012

Error - The report server cannot decrypt the symmetric key?

SSRS had been working fine on my comp till the time i insatlled VS 2005. I have started getting following error since VS2005 install

The report server cannot decrypt the symmetric key used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content and then restart the service. Check the documentation for more information. (rsReportServerDisabled) Get Online Help
Bad Data.

Why does this error cropped and how can i fix it? I am using SQL Server 2000.

Thanks

It cropped because VS.NET 2005 did aspnet_regiis.exe. Assuming that you have backed up your encryption key (you did right?), you can use the Reporting Services Configuration utility to restore it. If no backup, do:

"C:\Program Files\Microsoft SQL Server\90\Tools\Binn\RsKeyMgmt.exe" -d

Then, go to the Report Manager and reset the connection string in all data sources.

|||if the above command is executed, it seems like it will delete all the reporting data also.
is that correct?

|||Incorrect. Only the ecrypted information will be nuked, i.e. connection credentials, connection strings, and any secure information stored in subscriptions – by default this is only username & password in File Share delivery extension.|||So the actual data is never encrypted in the Reporting Services db? Then in case I never made a backup of the encryption keys, and I have to delete it now, I wouldn't be losing any data; just
connection strings etc. Where do I go about changing these connection strings? Again a newbie question for you, what is the File Share delivery extension?

Thanks
|||Excluding snapshots, the actual data is not stored in the report catalog. Yes, you will loose only the data source credentials. You can go to the Report Manager to change them. FSE is about delivering subsribed reports (users can subscribe to reports believe it or not) to a network file share.

Friday, February 17, 2012

Error

I tryed to execute the maintenace plan, but it failed... the second time I
tryed to execute it it gave me this error message:
Execute Maintenance Plan
An exception occured while executing a Transact-SQL statement or batch
(Microsoft.SqlServer.ConnectInfo)
SqlServerAgent Error: Request to run job backup_db (from <domain>\Jeff)
refused because the job is already running from a request by User
<domain>\Jeff (Microsft Sql Server, Error 22022)
I'm not sure how the first error message was (I tryed to execute the
maintenance plan twice)...
strange if I should get an error that the job is already running...
well, maybe it was caused by my user account, which not a member of the
local administrator on that server, but I'm a member of the administrators
in the domain
any suggestions?Hi
Did you try to execute the job or the maintenance plan? If you look at the
view history of the plan it may have something in for the last run, if it is
still running then it would be incomplete information.
John
"Jeff" wrote:

> I tryed to execute the maintenace plan, but it failed... the second time I
> tryed to execute it it gave me this error message:
> Execute Maintenance Plan
> An exception occured while executing a Transact-SQL statement or batch
> (Microsoft.SqlServer.ConnectInfo)
> SqlServerAgent Error: Request to run job backup_db (from <domain>\Jeff)
> refused because the job is already running from a request by User
> <domain>\Jeff (Microsft Sql Server, Error 22022)
> I'm not sure how the first error message was (I tryed to execute the
> maintenance plan twice)...
> strange if I should get an error that the job is already running...
> well, maybe it was caused by my user account, which not a member of the
> local administrator on that server, but I'm a member of the administrators
> in the domain
> any suggestions?
>
>|||It fails because as the error message refers it's already running. You
should check the history for any detailed error messages about the running
job if there is any.
Ekrem nsoy
"Jeff" <donot@.spam.me> wrote in message
news:enncutLQIHA.5184@.TK2MSFTNGP05.phx.gbl...
>I tryed to execute the maintenace plan, but it failed... the second time I
>tryed to execute it it gave me this error message:
> Execute Maintenance Plan
> An exception occured while executing a Transact-SQL statement or batch
> (Microsoft.SqlServer.ConnectInfo)
> SqlServerAgent Error: Request to run job backup_db (from <domain>\Jeff)
> refused because the job is already running from a request by User
> <domain>\Jeff (Microsft Sql Server, Error 22022)
> I'm not sure how the first error message was (I tryed to execute the
> maintenance plan twice)...
> strange if I should get an error that the job is already running...
> well, maybe it was caused by my user account, which not a member of the
> local administrator on that server, but I'm a member of the administrators
> in the domain
> any suggestions?
>