Seems that someone deleted the maintenace jobs and now I can not delete any
of the jobs associated with them. I get error:
TITLE: Microsoft SQL Server Management Studio
--
Attempt to retrieve data for object failed for Server 'IMPULSE-BPB'.
(Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attempt+to+retrieve+data+for+object+Server&LinkId=20476
--
ADDITIONAL INFORMATION:
The Job 'BP WSS Database Job.DB Backup Job for DB Maintenance Plan 'BP WSS
Database Job'' does not exist on the server. (Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.ObjectDoesNotExist&LinkId=20476
--
BUTTONS:
OK
--
Any Idea's?
ThanksClick on the Jobs node in SSMS and click Refresh.
You know, sometimes items are not refreshed automatically in SSMS (and EM of
course) and you see that Maintenance tasks are deleted but jobs are still
there but they are not actually. So you are trying to delete the deleted
stuff. I've seen this situation lots of times and I thought this could be
your situation.
--
Ekrem Ã?nsoy
"RickSpicknall" <RickSpicknall@.discussions.microsoft.com> wrote in message
news:8A0F2AF9-A5EC-4052-A162-99C94ABD5C96@.microsoft.com...
> Seems that someone deleted the maintenace jobs and now I can not delete
> any
> of the jobs associated with them. I get error:
> TITLE: Microsoft SQL Server Management Studio
> --
> Attempt to retrieve data for object failed for Server 'IMPULSE-BPB'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attempt+to+retrieve+data+for+object+Server&LinkId=20476
> --
> ADDITIONAL INFORMATION:
> The Job 'BP WSS Database Job.DB Backup Job for DB Maintenance Plan 'BP WSS
> Database Job'' does not exist on the server. (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.ObjectDoesNotExist&LinkId=20476
> --
> BUTTONS:
> OK
> --
> Any Idea's?
> Thanks|||Geez whiz, Now I feel dumb. Thanks However I still have one out there I
can not get rid of. I get error:
The DELETE statement conflicted with the REFERENCE constraint
"FK_subplan_job_id". The conflict occurred in database "msdb", table
"dbo.sysmaintplan_subplans", column 'job_id'.
The statement has been terminated. (.Net SqlClient Data Provider)
"Ekrem Ã?nsoy" wrote:
> Click on the Jobs node in SSMS and click Refresh.
> You know, sometimes items are not refreshed automatically in SSMS (and EM of
> course) and you see that Maintenance tasks are deleted but jobs are still
> there but they are not actually. So you are trying to delete the deleted
> stuff. I've seen this situation lots of times and I thought this could be
> your situation.
> --
> Ekrem Ã?nsoy
>
> "RickSpicknall" <RickSpicknall@.discussions.microsoft.com> wrote in message
> news:8A0F2AF9-A5EC-4052-A162-99C94ABD5C96@.microsoft.com...
> > Seems that someone deleted the maintenace jobs and now I can not delete
> > any
> > of the jobs associated with them. I get error:
> >
> > TITLE: Microsoft SQL Server Management Studio
> > --
> >
> > Attempt to retrieve data for object failed for Server 'IMPULSE-BPB'.
> > (Microsoft.SqlServer.Smo)
> >
> > For help, click:
> > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attempt+to+retrieve+data+for+object+Server&LinkId=20476
> >
> > --
> > ADDITIONAL INFORMATION:
> >
> > The Job 'BP WSS Database Job.DB Backup Job for DB Maintenance Plan 'BP WSS
> > Database Job'' does not exist on the server. (Microsoft.SqlServer.Smo)
> >
> > For help, click:
> > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.ObjectDoesNotExist&LinkId=20476
> >
> > --
> > BUTTONS:
> >
> > OK
> > --
> >
> > Any Idea's?
> > Thanks
>|||Hi Rick!
There is a Foreign Key constraint there.
Try this:
USE MSDB
SELECT * FROM dbo.sysmaintplan_subplans
Find your plan_id and then
DELETE FROM dbo.sysmaintplan_log WHERE plan_id = 'plan_id '
EXECUTE sp_delete_maintenance_plan 'plan_id '
Ekrem Ã?nsoy
"RickSpicknall" <RickSpicknall@.discussions.microsoft.com> wrote in message
news:F7029524-ACA4-4F62-85F7-18D5EB924F46@.microsoft.com...
> Geez whiz, Now I feel dumb. Thanks However I still have one out there I
> can not get rid of. I get error:
> The DELETE statement conflicted with the REFERENCE constraint
> "FK_subplan_job_id". The conflict occurred in database "msdb", table
> "dbo.sysmaintplan_subplans", column 'job_id'.
> The statement has been terminated. (.Net SqlClient Data Provider)
> "Ekrem Ã?nsoy" wrote:
>> Click on the Jobs node in SSMS and click Refresh.
>> You know, sometimes items are not refreshed automatically in SSMS (and EM
>> of
>> course) and you see that Maintenance tasks are deleted but jobs are still
>> there but they are not actually. So you are trying to delete the deleted
>> stuff. I've seen this situation lots of times and I thought this could be
>> your situation.
>> --
>> Ekrem Ã?nsoy
>>
>> "RickSpicknall" <RickSpicknall@.discussions.microsoft.com> wrote in
>> message
>> news:8A0F2AF9-A5EC-4052-A162-99C94ABD5C96@.microsoft.com...
>> > Seems that someone deleted the maintenace jobs and now I can not delete
>> > any
>> > of the jobs associated with them. I get error:
>> >
>> > TITLE: Microsoft SQL Server Management Studio
>> > --
>> >
>> > Attempt to retrieve data for object failed for Server 'IMPULSE-BPB'.
>> > (Microsoft.SqlServer.Smo)
>> >
>> > For help, click:
>> > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attempt+to+retrieve+data+for+object+Server&LinkId=20476
>> >
>> > --
>> > ADDITIONAL INFORMATION:
>> >
>> > The Job 'BP WSS Database Job.DB Backup Job for DB Maintenance Plan 'BP
>> > WSS
>> > Database Job'' does not exist on the server. (Microsoft.SqlServer.Smo)
>> >
>> > For help, click:
>> > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.ObjectDoesNotExist&LinkId=20476
>> >
>> > --
>> > BUTTONS:
>> >
>> > OK
>> > --
>> >
>> > Any Idea's?
>> > Thanks
Showing posts with label jobs. Show all posts
Showing posts with label jobs. Show all posts
Sunday, March 25, 2012
Can not create Job on SQL2005
Could not create SQL jobs. Getting Error:
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type
'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)
- Tried several different job types, always same result.
- Installing SP1 or SP2 does not help.
- Installing with or without Integration Service does not help.
Any help is highly appreciated
Thanks.
Try this:
Dim strDBName As String
Dim strJobID As Guid
Dim jobDumpJob As Job
Dim jbsDumpJobStep As JobStep
Dim intStepID As Integer
' Connect to the server
Dim srvMgmtServer As Server
srvMgmtServer = New Server("MyServer")
Dim srvConn As ServerConnection
srvConn = srvMgmtServer.ConnectionContext
srvConn.LoginSecure = True
strDBName = dbDatabase.Name
jobDumpJob = New Job(srvMgmtServer.JobServer, "YourJobName")
jobDumpJob.Description = "Job Description"
jobDumpJob.Category = "[Uncategorized (Local)]"
jobDumpJob.OwnerLoginName = "sa"
jobDumpJob.Create()
strJobID = jobDumpJob.JobID
jbsDumpJobStep = New JobStep(jobDumpJob, "Step 1")
jbsDumpJobStep.DatabaseName = "UserDB"
jbsDumpJobStep.Command = "TSQL command"
jbsDumpJobStep.OnSuccessAction = StepCompletionAction.QuitWithSuccess
jbsDumpJobStep.OnFailAction = StepCompletionAction.QuitWithFailure
jbsDumpJobStep.Create()
intStepID = jbsDumpJobStep.ID
jobDumpJob.ApplyToTargetServer(srvMgmtServer.Name)
jobDumpJob.StartStepID = intStepID
jobDumpJob.Alter()
|||
Hi
I am also having this problem.
Im trying to create a job to run SQL Server Integration Package.
The Code that you have given above. What is that for?
Thanks
|||This code uses SMO in VB.Net to create a job to execute a TSQL command. Browse around in ObjectBrowser and you should find the properties necessary to execute a SSIS package.|||I can execute the SISS Package.
But i want to execute it within a job.
Is there any tutorials for creating jobs that i could look at?
|||for some reason it works on an another machine. I dont no why.|||I figured it out. Despite you could install Management Tool on any computer it will work only on machine that have SQL Server 2005 SP2 installed.
|||Try installing SP2 for the client components on all computers taht run management studio, reboot, then try again from management studio client.|||Identical problems here--also tried the new hotfix as well.
We've held off rolling out SP2 due to these and other errors. Until someone deals with these problems I suppose my company is stuck.
|||Check whether Distributed Transaction Coordinator service is started. If not, start it and try again.|||We have a sql2005 installation that I've created jobs on routinely for months and then today we hit this message. I'm not going to install SP2 just yet since some users report that it doesn't help.
The details from the error message are as follows. Any help would be much appreciated. I deleted all SSIS packages and Jobs with no luck. We've rebooted and cycled services per suggestions from users.
The original error message:
TITLE: Microsoft SQL Server Management Studio
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)
BUTTONS:
OK
Technical details
===================================
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)
Program Location:
at Microsoft.SqlServer.Management.Smo.Agent.JobCollection.GetObjectByKey(ObjectKeyBase key)
at Microsoft.SqlServer.Management.Smo.SimpleObjectCollectionBase.Contains(String name)
at Microsoft.SqlServer.Management.SqlManagerUI.JobData.JobExists(String jobName)
at Microsoft.SqlServer.Management.SqlManagerUI.JobData.ApplyChanges()
at Microsoft.SqlServer.Management.SqlManagerUI.JobPropertySheet.DoPreProcessExecution(RunType runType, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.DoPreProcessExecutionAndRunViews(RunType runType)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.ExecuteForSql(PreProcessExecutionInfo executionInfo, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.Microsoft.SqlServer.Management.SqlMgmt.IExecutionAwareSqlControlCollection.PreProcessExecution(PreProcessExecutionInfo executionInfo, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.RunNow(RunType runType, Object sender)
|||
Hi folks,
I too had the same exact error when trying to schedule a package. After reading numerous posts and forums, some people have said
SP2 solved their problems and some said it didn't.
Here's what I did to get it to work.
On our SQL Server 2005 development machine, we did install SP2
however, that doesn't solve the problem because the problem lies in scheduling your job using Management Studio through your local machine. If you logged onto your SQL 2005 server that has SP2, you should be able to schedule from there. But it's through Management Studio, which I'm guessing most of you are trying to create a job schedule for your packages. Usually, people don't think of upgrading their client tools as well.
I verified this by upgrading my local machine to SP2 for the client tools and was able to successfully schedule. You might also need to upgrade your server machine to SP2 to work as well.
I hope this helps.
-SX
|||I finally uninstalled all SQL related products and services, reinstalled everything, added hot fixes and finally we have two of the three servers working--mostly. There are still occaisional errors, but most seem limited to SSMS' and its UI
I haven't rolled SP2 to production yet and won't be adding any new SQL servers to our mix until this mess settles. I thought we'd be going to some of the better features (like Mirroring) later this year but now it'll be Q1'08 at the earliest.
Haven't had this much fun since SQL2KSP4! Keep smiling....
|||Hello Visgor Allen and others!
Thank you for reporting this problem, and sorry for the problems that you are experiencing.
I'd like to understand this issue better so we can provide guidance to other customers. Can somebody on this thread please provide more details on how to repro this problem:
1) What is the initial configuration on both server and client machines (if different)? Is it SQL Server 2005 RTM or SP1?
2) Does the problem reproduce after upgrading client/server/both machines to SP2?
3) From what machine (client/server) are you trying to create a new job?
Thanks in advance!
|||
Unable to create new jobs in sql 2005, SSIS service is running. Finally i was surfing net for solution and understood need to install SP2 in my machine. But if i need to create new jobs in remote system what should i do.
Please suggest me a solution.
Can not create Job on SQL2005
Could not create SQL jobs. Getting Error:
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type
'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)
- Tried several different job types, always same result.
- Installing SP1 or SP2 does not help.
- Installing with or without Integration Service does not help.
Any help is highly appreciated
Thanks.
Try this:
Dim strDBName As String
Dim strJobID As Guid
Dim jobDumpJob As Job
Dim jbsDumpJobStep As JobStep
Dim intStepID As Integer
' Connect to the server
Dim srvMgmtServer As Server
srvMgmtServer = New Server("MyServer")
Dim srvConn As ServerConnection
srvConn = srvMgmtServer.ConnectionContext
srvConn.LoginSecure = True
strDBName = dbDatabase.Name
jobDumpJob = New Job(srvMgmtServer.JobServer, "YourJobName")
jobDumpJob.Description = "Job Description"
jobDumpJob.Category = "[Uncategorized (Local)]"
jobDumpJob.OwnerLoginName = "sa"
jobDumpJob.Create()
strJobID = jobDumpJob.JobID
jbsDumpJobStep = New JobStep(jobDumpJob, "Step 1")
jbsDumpJobStep.DatabaseName = "UserDB"
jbsDumpJobStep.Command = "TSQL command"
jbsDumpJobStep.OnSuccessAction = StepCompletionAction.QuitWithSuccess
jbsDumpJobStep.OnFailAction = StepCompletionAction.QuitWithFailure
jbsDumpJobStep.Create()
intStepID = jbsDumpJobStep.ID
jobDumpJob.ApplyToTargetServer(srvMgmtServer.Name)
jobDumpJob.StartStepID = intStepID
jobDumpJob.Alter()
Hi
I am also having this problem.
Im trying to create a job to run SQL Server Integration Package.
The Code that you have given above. What is that for?
Thanks
|||This code uses SMO in VB.Net to create a job to execute a TSQL command. Browse around in ObjectBrowser and you should find the properties necessary to execute a SSIS package.|||I can execute the SISS Package.
But i want to execute it within a job.
Is there any tutorials for creating jobs that i could look at?
|||for some reason it works on an another machine. I dont no why.|||I figured it out. Despite you could install Management Tool on any computer it will work only on machine that have SQL Server 2005 SP2 installed.
|||Try installing SP2 for the client components on all computers taht run management studio, reboot, then try again from management studio client.|||Identical problems here--also tried the new hotfix as well.
We've held off rolling out SP2 due to these and other errors. Until someone deals with these problems I suppose my company is stuck.
|||Check whether Distributed Transaction Coordinator service is started. If not, start it and try again.|||We have a sql2005 installation that I've created jobs on routinely for months and then today we hit this message. I'm not going to install SP2 just yet since some users report that it doesn't help.
The details from the error message are as follows. Any help would be much appreciated. I deleted all SSIS packages and Jobs with no luck. We've rebooted and cycled services per suggestions from users.
The original error message:
TITLE: Microsoft SQL Server Management Studio
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)
BUTTONS:
OK
Technical details
===================================
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)
Program Location:
at Microsoft.SqlServer.Management.Smo.Agent.JobCollection.GetObjectByKey(ObjectKeyBase key)
at Microsoft.SqlServer.Management.Smo.SimpleObjectCollectionBase.Contains(String name)
at Microsoft.SqlServer.Management.SqlManagerUI.JobData.JobExists(String jobName)
at Microsoft.SqlServer.Management.SqlManagerUI.JobData.ApplyChanges()
at Microsoft.SqlServer.Management.SqlManagerUI.JobPropertySheet.DoPreProcessExecution(RunType runType, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.DoPreProcessExecutionAndRunViews(RunType runType)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.ExecuteForSql(PreProcessExecutionInfo executionInfo, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.Microsoft.SqlServer.Management.SqlMgmt.IExecutionAwareSqlControlCollection.PreProcessExecution(PreProcessExecutionInfo executionInfo, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.RunNow(RunType runType, Object sender)
Hi folks,
I too had the same exact error when trying to schedule a package. After reading numerous posts and forums, some people have said
SP2 solved their problems and some said it didn't.
Here's what I did to get it to work.
On our SQL Server 2005 development machine, we did install SP2
however, that doesn't solve the problem because the problem lies in scheduling your job using Management Studio through your local machine. If you logged onto your SQL 2005 server that has SP2, you should be able to schedule from there. But it's through Management Studio, which I'm guessing most of you are trying to create a job schedule for your packages. Usually, people don't think of upgrading their client tools as well.
I verified this by upgrading my local machine to SP2 for the client tools and was able to successfully schedule. You might also need to upgrade your server machine to SP2 to work as well.
I hope this helps.
-SX
|||I finally uninstalled all SQL related products and services, reinstalled everything, added hot fixes and finally we have two of the three servers working--mostly. There are still occaisional errors, but most seem limited to SSMS' and its UI
I haven't rolled SP2 to production yet and won't be adding any new SQL servers to our mix until this mess settles. I thought we'd be going to some of the better features (like Mirroring) later this year but now it'll be Q1'08 at the earliest.
Haven't had this much fun since SQL2KSP4! Keep smiling....
|||Hello Visgor Allen and others!
Thank you for reporting this problem, and sorry for the problems that you are experiencing.
I'd like to understand this issue better so we can provide guidance to other customers. Can somebody on this thread please provide more details on how to repro this problem:
1) What is the initial configuration on both server and client machines (if different)? Is it SQL Server 2005 RTM or SP1?
2) Does the problem reproduce after upgrading client/server/both machines to SP2?
3) From what machine (client/server) are you trying to create a new job?
Thanks in advance!
|||Unable to create new jobs in sql 2005, SSIS service is running. Finally i was surfing net for solution and understood need to install SP2 in my machine. But if i need to create new jobs in remote system what should i do.
Please suggest me a solution.
Can not create Job on SQL2005
Could not create SQL jobs. Getting Error:
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type
'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)
- Tried several different job types, always same result.
- Installing SP1 or SP2 does not help.
- Installing with or without Integration Service does not help.
Any help is highly appreciated
Thanks.
Try this:
Dim strDBName As String
Dim strJobID As Guid
Dim jobDumpJob As Job
Dim jbsDumpJobStep As JobStep
Dim intStepID As Integer
' Connect to the server
Dim srvMgmtServer As Server
srvMgmtServer = New Server("MyServer")
Dim srvConn As ServerConnection
srvConn = srvMgmtServer.ConnectionContext
srvConn.LoginSecure = True
strDBName = dbDatabase.Name
jobDumpJob = New Job(srvMgmtServer.JobServer, "YourJobName")
jobDumpJob.Description = "Job Description"
jobDumpJob.Category = "[Uncategorized (Local)]"
jobDumpJob.OwnerLoginName = "sa"
jobDumpJob.Create()
strJobID = jobDumpJob.JobID
jbsDumpJobStep = New JobStep(jobDumpJob, "Step 1")
jbsDumpJobStep.DatabaseName = "UserDB"
jbsDumpJobStep.Command = "TSQL command"
jbsDumpJobStep.OnSuccessAction = StepCompletionAction.QuitWithSuccess
jbsDumpJobStep.OnFailAction = StepCompletionAction.QuitWithFailure
jbsDumpJobStep.Create()
intStepID = jbsDumpJobStep.ID
jobDumpJob.ApplyToTargetServer(srvMgmtServer.Name)
jobDumpJob.StartStepID = intStepID
jobDumpJob.Alter()
Hi
I am also having this problem.
Im trying to create a job to run SQL Server Integration Package.
The Code that you have given above. What is that for?
Thanks
|||This code uses SMO in VB.Net to create a job to execute a TSQL command. Browse around in ObjectBrowser and you should find the properties necessary to execute a SSIS package.|||I can execute the SISS Package.
But i want to execute it within a job.
Is there any tutorials for creating jobs that i could look at?
|||for some reason it works on an another machine. I dont no why.|||I figured it out. Despite you could install Management Tool on any computer it will work only on machine that have SQL Server 2005 SP2 installed.
|||Try installing SP2 for the client components on all computers taht run management studio, reboot, then try again from management studio client.|||Identical problems here--also tried the new hotfix as well.
We've held off rolling out SP2 due to these and other errors. Until someone deals with these problems I suppose my company is stuck.
|||Check whether Distributed Transaction Coordinator service is started. If not, start it and try again.|||We have a sql2005 installation that I've created jobs on routinely for months and then today we hit this message. I'm not going to install SP2 just yet since some users report that it doesn't help.
The details from the error message are as follows. Any help would be much appreciated. I deleted all SSIS packages and Jobs with no luck. We've rebooted and cycled services per suggestions from users.
The original error message:
TITLE: Microsoft SQL Server Management Studio
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)
BUTTONS:
OK
Technical details
===================================
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)
Program Location:
at Microsoft.SqlServer.Management.Smo.Agent.JobCollection.GetObjectByKey(ObjectKeyBase key)
at Microsoft.SqlServer.Management.Smo.SimpleObjectCollectionBase.Contains(String name)
at Microsoft.SqlServer.Management.SqlManagerUI.JobData.JobExists(String jobName)
at Microsoft.SqlServer.Management.SqlManagerUI.JobData.ApplyChanges()
at Microsoft.SqlServer.Management.SqlManagerUI.JobPropertySheet.DoPreProcessExecution(RunType runType, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.DoPreProcessExecutionAndRunViews(RunType runType)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.ExecuteForSql(PreProcessExecutionInfo executionInfo, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.Microsoft.SqlServer.Management.SqlMgmt.IExecutionAwareSqlControlCollection.PreProcessExecution(PreProcessExecutionInfo executionInfo, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.RunNow(RunType runType, Object sender)
Hi folks,
I too had the same exact error when trying to schedule a package. After reading numerous posts and forums, some people have said
SP2 solved their problems and some said it didn't.
Here's what I did to get it to work.
On our SQL Server 2005 development machine, we did install SP2
however, that doesn't solve the problem because the problem lies in scheduling your job using Management Studio through your local machine. If you logged onto your SQL 2005 server that has SP2, you should be able to schedule from there. But it's through Management Studio, which I'm guessing most of you are trying to create a job schedule for your packages. Usually, people don't think of upgrading their client tools as well.
I verified this by upgrading my local machine to SP2 for the client tools and was able to successfully schedule. You might also need to upgrade your server machine to SP2 to work as well.
I hope this helps.
-SX
|||I finally uninstalled all SQL related products and services, reinstalled everything, added hot fixes and finally we have two of the three servers working--mostly. There are still occaisional errors, but most seem limited to SSMS' and its UI
I haven't rolled SP2 to production yet and won't be adding any new SQL servers to our mix until this mess settles. I thought we'd be going to some of the better features (like Mirroring) later this year but now it'll be Q1'08 at the earliest.
Haven't had this much fun since SQL2KSP4! Keep smiling....
|||Hello Visgor Allen and others!
Thank you for reporting this problem, and sorry for the problems that you are experiencing.
I'd like to understand this issue better so we can provide guidance to other customers. Can somebody on this thread please provide more details on how to repro this problem:
1) What is the initial configuration on both server and client machines (if different)? Is it SQL Server 2005 RTM or SP1?
2) Does the problem reproduce after upgrading client/server/both machines to SP2?
3) From what machine (client/server) are you trying to create a new job?
Thanks in advance!
|||Unable to create new jobs in sql 2005, SSIS service is running. Finally i was surfing net for solution and understood need to install SP2 in my machine. But if i need to create new jobs in remote system what should i do.
Please suggest me a solution.
Can not create Job on SQL2005
Could not create SQL jobs. Getting Error:
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type
'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)
- Tried several different job types, always same result.
- Installing SP1 or SP2 does not help.
- Installing with or without Integration Service does not help.
Any help is highly appreciated
Thanks.
Try this:
Dim strDBName As String
Dim strJobID As Guid
Dim jobDumpJob As Job
Dim jbsDumpJobStep As JobStep
Dim intStepID As Integer
' Connect to the server
Dim srvMgmtServer As Server
srvMgmtServer = New Server("MyServer")
Dim srvConn As ServerConnection
srvConn = srvMgmtServer.ConnectionContext
srvConn.LoginSecure = True
strDBName = dbDatabase.Name
jobDumpJob = New Job(srvMgmtServer.JobServer, "YourJobName")
jobDumpJob.Description = "Job Description"
jobDumpJob.Category = "[Uncategorized (Local)]"
jobDumpJob.OwnerLoginName = "sa"
jobDumpJob.Create()
strJobID = jobDumpJob.JobID
jbsDumpJobStep = New JobStep(jobDumpJob, "Step 1")
jbsDumpJobStep.DatabaseName = "UserDB"
jbsDumpJobStep.Command = "TSQL command"
jbsDumpJobStep.OnSuccessAction = StepCompletionAction.QuitWithSuccess
jbsDumpJobStep.OnFailAction = StepCompletionAction.QuitWithFailure
jbsDumpJobStep.Create()
intStepID = jbsDumpJobStep.ID
jobDumpJob.ApplyToTargetServer(srvMgmtServer.Name)
jobDumpJob.StartStepID = intStepID
jobDumpJob.Alter()
Hi
I am also having this problem.
Im trying to create a job to run SQL Server Integration Package.
The Code that you have given above. What is that for?
Thanks
|||This code uses SMO in VB.Net to create a job to execute a TSQL command. Browse around in ObjectBrowser and you should find the properties necessary to execute a SSIS package.|||I can execute the SISS Package.
But i want to execute it within a job.
Is there any tutorials for creating jobs that i could look at?
|||for some reason it works on an another machine. I dont no why.|||I figured it out. Despite you could install Management Tool on any computer it will work only on machine that have SQL Server 2005 SP2 installed.
|||Try installing SP2 for the client components on all computers taht run management studio, reboot, then try again from management studio client.|||Identical problems here--also tried the new hotfix as well.
We've held off rolling out SP2 due to these and other errors. Until someone deals with these problems I suppose my company is stuck.
|||Check whether Distributed Transaction Coordinator service is started. If not, start it and try again.|||We have a sql2005 installation that I've created jobs on routinely for months and then today we hit this message. I'm not going to install SP2 just yet since some users report that it doesn't help.
The details from the error message are as follows. Any help would be much appreciated. I deleted all SSIS packages and Jobs with no luck. We've rebooted and cycled services per suggestions from users.
The original error message:
TITLE: Microsoft SQL Server Management Studio
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)
BUTTONS:
OK
Technical details
===================================
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)
Program Location:
at Microsoft.SqlServer.Management.Smo.Agent.JobCollection.GetObjectByKey(ObjectKeyBase key)
at Microsoft.SqlServer.Management.Smo.SimpleObjectCollectionBase.Contains(String name)
at Microsoft.SqlServer.Management.SqlManagerUI.JobData.JobExists(String jobName)
at Microsoft.SqlServer.Management.SqlManagerUI.JobData.ApplyChanges()
at Microsoft.SqlServer.Management.SqlManagerUI.JobPropertySheet.DoPreProcessExecution(RunType runType, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.DoPreProcessExecutionAndRunViews(RunType runType)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.ExecuteForSql(PreProcessExecutionInfo executionInfo, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.Microsoft.SqlServer.Management.SqlMgmt.IExecutionAwareSqlControlCollection.PreProcessExecution(PreProcessExecutionInfo executionInfo, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.RunNow(RunType runType, Object sender)
Hi folks,
I too had the same exact error when trying to schedule a package. After reading numerous posts and forums, some people have said
SP2 solved their problems and some said it didn't.
Here's what I did to get it to work.
On our SQL Server 2005 development machine, we did install SP2
however, that doesn't solve the problem because the problem lies in scheduling your job using Management Studio through your local machine. If you logged onto your SQL 2005 server that has SP2, you should be able to schedule from there. But it's through Management Studio, which I'm guessing most of you are trying to create a job schedule for your packages. Usually, people don't think of upgrading their client tools as well.
I verified this by upgrading my local machine to SP2 for the client tools and was able to successfully schedule. You might also need to upgrade your server machine to SP2 to work as well.
I hope this helps.
-SX
|||I finally uninstalled all SQL related products and services, reinstalled everything, added hot fixes and finally we have two of the three servers working--mostly. There are still occaisional errors, but most seem limited to SSMS' and its UI
I haven't rolled SP2 to production yet and won't be adding any new SQL servers to our mix until this mess settles. I thought we'd be going to some of the better features (like Mirroring) later this year but now it'll be Q1'08 at the earliest.
Haven't had this much fun since SQL2KSP4! Keep smiling....
|||Hello Visgor Allen and others!
Thank you for reporting this problem, and sorry for the problems that you are experiencing.
I'd like to understand this issue better so we can provide guidance to other customers. Can somebody on this thread please provide more details on how to repro this problem:
1) What is the initial configuration on both server and client machines (if different)? Is it SQL Server 2005 RTM or SP1?
2) Does the problem reproduce after upgrading client/server/both machines to SP2?
3) From what machine (client/server) are you trying to create a new job?
Thanks in advance!
|||Unable to create new jobs in sql 2005, SSIS service is running. Finally i was surfing net for solution and understood need to install SP2 in my machine. But if i need to create new jobs in remote system what should i do.
Please suggest me a solution.
sqlCan not create Job on SQL2005
Could not create SQL jobs. Getting Error:
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type
'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)
- Tried several different job types, always same result.
- Installing SP1 or SP2 does not help.
- Installing with or without Integration Service does not help.
Any help is highly appreciated
Thanks.
Try this:
Dim strDBName As String
Dim strJobID As Guid
Dim jobDumpJob As Job
Dim jbsDumpJobStep As JobStep
Dim intStepID As Integer
' Connect to the server
Dim srvMgmtServer As Server
srvMgmtServer = New Server("MyServer")
Dim srvConn As ServerConnection
srvConn = srvMgmtServer.ConnectionContext
srvConn.LoginSecure = True
strDBName = dbDatabase.Name
jobDumpJob = New Job(srvMgmtServer.JobServer, "YourJobName")
jobDumpJob.Description = "Job Description"
jobDumpJob.Category = "[Uncategorized (Local)]"
jobDumpJob.OwnerLoginName = "sa"
jobDumpJob.Create()
strJobID = jobDumpJob.JobID
jbsDumpJobStep = New JobStep(jobDumpJob, "Step 1")
jbsDumpJobStep.DatabaseName = "UserDB"
jbsDumpJobStep.Command = "TSQL command"
jbsDumpJobStep.OnSuccessAction = StepCompletionAction.QuitWithSuccess
jbsDumpJobStep.OnFailAction = StepCompletionAction.QuitWithFailure
jbsDumpJobStep.Create()
intStepID = jbsDumpJobStep.ID
jobDumpJob.ApplyToTargetServer(srvMgmtServer.Name)
jobDumpJob.StartStepID = intStepID
jobDumpJob.Alter()
Hi
I am also having this problem.
Im trying to create a job to run SQL Server Integration Package.
The Code that you have given above. What is that for?
Thanks
|||This code uses SMO in VB.Net to create a job to execute a TSQL command. Browse around in ObjectBrowser and you should find the properties necessary to execute a SSIS package.|||I can execute the SISS Package.
But i want to execute it within a job.
Is there any tutorials for creating jobs that i could look at?
|||for some reason it works on an another machine. I dont no why.|||I figured it out. Despite you could install Management Tool on any computer it will work only on machine that have SQL Server 2005 SP2 installed.
|||Try installing SP2 for the client components on all computers taht run management studio, reboot, then try again from management studio client.|||Identical problems here--also tried the new hotfix as well.
We've held off rolling out SP2 due to these and other errors. Until someone deals with these problems I suppose my company is stuck.
|||Check whether Distributed Transaction Coordinator service is started. If not, start it and try again.|||We have a sql2005 installation that I've created jobs on routinely for months and then today we hit this message. I'm not going to install SP2 just yet since some users report that it doesn't help.
The details from the error message are as follows. Any help would be much appreciated. I deleted all SSIS packages and Jobs with no luck. We've rebooted and cycled services per suggestions from users.
The original error message:
TITLE: Microsoft SQL Server Management Studio
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)
BUTTONS:
OK
Technical details
===================================
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)
Program Location:
at Microsoft.SqlServer.Management.Smo.Agent.JobCollection.GetObjectByKey(ObjectKeyBase key)
at Microsoft.SqlServer.Management.Smo.SimpleObjectCollectionBase.Contains(String name)
at Microsoft.SqlServer.Management.SqlManagerUI.JobData.JobExists(String jobName)
at Microsoft.SqlServer.Management.SqlManagerUI.JobData.ApplyChanges()
at Microsoft.SqlServer.Management.SqlManagerUI.JobPropertySheet.DoPreProcessExecution(RunType runType, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.DoPreProcessExecutionAndRunViews(RunType runType)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.ExecuteForSql(PreProcessExecutionInfo executionInfo, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.Microsoft.SqlServer.Management.SqlMgmt.IExecutionAwareSqlControlCollection.PreProcessExecution(PreProcessExecutionInfo executionInfo, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.RunNow(RunType runType, Object sender)
Hi folks,
I too had the same exact error when trying to schedule a package. After reading numerous posts and forums, some people have said
SP2 solved their problems and some said it didn't.
Here's what I did to get it to work.
On our SQL Server 2005 development machine, we did install SP2
however, that doesn't solve the problem because the problem lies in scheduling your job using Management Studio through your local machine. If you logged onto your SQL 2005 server that has SP2, you should be able to schedule from there. But it's through Management Studio, which I'm guessing most of you are trying to create a job schedule for your packages. Usually, people don't think of upgrading their client tools as well.
I verified this by upgrading my local machine to SP2 for the client tools and was able to successfully schedule. You might also need to upgrade your server machine to SP2 to work as well.
I hope this helps.
-SX
|||I finally uninstalled all SQL related products and services, reinstalled everything, added hot fixes and finally we have two of the three servers working--mostly. There are still occaisional errors, but most seem limited to SSMS' and its UI
I haven't rolled SP2 to production yet and won't be adding any new SQL servers to our mix until this mess settles. I thought we'd be going to some of the better features (like Mirroring) later this year but now it'll be Q1'08 at the earliest.
Haven't had this much fun since SQL2KSP4! Keep smiling....
|||Hello Visgor Allen and others!
Thank you for reporting this problem, and sorry for the problems that you are experiencing.
I'd like to understand this issue better so we can provide guidance to other customers. Can somebody on this thread please provide more details on how to repro this problem:
1) What is the initial configuration on both server and client machines (if different)? Is it SQL Server 2005 RTM or SP1?
2) Does the problem reproduce after upgrading client/server/both machines to SP2?
3) From what machine (client/server) are you trying to create a new job?
Thanks in advance!
|||Unable to create new jobs in sql 2005, SSIS service is running. Finally i was surfing net for solution and understood need to install SP2 in my machine. But if i need to create new jobs in remote system what should i do.
Please suggest me a solution.
Can not create Job on SQL2005
Could not create SQL jobs. Getting Error:
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type
'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)
- Tried several different job types, always same result.
- Installing SP1 or SP2 does not help.
- Installing with or without Integration Service does not help.
Any help is highly appreciated
Thanks.
Try this:
Dim strDBName As String
Dim strJobID As Guid
Dim jobDumpJob As Job
Dim jbsDumpJobStep As JobStep
Dim intStepID As Integer
' Connect to the server
Dim srvMgmtServer As Server
srvMgmtServer = New Server("MyServer")
Dim srvConn As ServerConnection
srvConn = srvMgmtServer.ConnectionContext
srvConn.LoginSecure = True
strDBName = dbDatabase.Name
jobDumpJob = New Job(srvMgmtServer.JobServer, "YourJobName")
jobDumpJob.Description = "Job Description"
jobDumpJob.Category = "[Uncategorized (Local)]"
jobDumpJob.OwnerLoginName = "sa"
jobDumpJob.Create()
strJobID = jobDumpJob.JobID
jbsDumpJobStep = New JobStep(jobDumpJob, "Step 1")
jbsDumpJobStep.DatabaseName = "UserDB"
jbsDumpJobStep.Command = "TSQL command"
jbsDumpJobStep.OnSuccessAction = StepCompletionAction.QuitWithSuccess
jbsDumpJobStep.OnFailAction = StepCompletionAction.QuitWithFailure
jbsDumpJobStep.Create()
intStepID = jbsDumpJobStep.ID
jobDumpJob.ApplyToTargetServer(srvMgmtServer.Name)
jobDumpJob.StartStepID = intStepID
jobDumpJob.Alter()
Hi
I am also having this problem.
Im trying to create a job to run SQL Server Integration Package.
The Code that you have given above. What is that for?
Thanks
|||This code uses SMO in VB.Net to create a job to execute a TSQL command. Browse around in ObjectBrowser and you should find the properties necessary to execute a SSIS package.|||I can execute the SISS Package.
But i want to execute it within a job.
Is there any tutorials for creating jobs that i could look at?
|||for some reason it works on an another machine. I dont no why.|||I figured it out. Despite you could install Management Tool on any computer it will work only on machine that have SQL Server 2005 SP2 installed.
|||Try installing SP2 for the client components on all computers taht run management studio, reboot, then try again from management studio client.|||Identical problems here--also tried the new hotfix as well.
We've held off rolling out SP2 due to these and other errors. Until someone deals with these problems I suppose my company is stuck.
|||Check whether Distributed Transaction Coordinator service is started. If not, start it and try again.|||We have a sql2005 installation that I've created jobs on routinely for months and then today we hit this message. I'm not going to install SP2 just yet since some users report that it doesn't help.
The details from the error message are as follows. Any help would be much appreciated. I deleted all SSIS packages and Jobs with no luck. We've rebooted and cycled services per suggestions from users.
The original error message:
TITLE: Microsoft SQL Server Management Studio
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)
BUTTONS:
OK
Technical details
===================================
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)
Program Location:
at Microsoft.SqlServer.Management.Smo.Agent.JobCollection.GetObjectByKey(ObjectKeyBase key)
at Microsoft.SqlServer.Management.Smo.SimpleObjectCollectionBase.Contains(String name)
at Microsoft.SqlServer.Management.SqlManagerUI.JobData.JobExists(String jobName)
at Microsoft.SqlServer.Management.SqlManagerUI.JobData.ApplyChanges()
at Microsoft.SqlServer.Management.SqlManagerUI.JobPropertySheet.DoPreProcessExecution(RunType runType, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.DoPreProcessExecutionAndRunViews(RunType runType)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.ExecuteForSql(PreProcessExecutionInfo executionInfo, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.Microsoft.SqlServer.Management.SqlMgmt.IExecutionAwareSqlControlCollection.PreProcessExecution(PreProcessExecutionInfo executionInfo, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.RunNow(RunType runType, Object sender)
Hi folks,
I too had the same exact error when trying to schedule a package. After reading numerous posts and forums, some people have said
SP2 solved their problems and some said it didn't.
Here's what I did to get it to work.
On our SQL Server 2005 development machine, we did install SP2
however, that doesn't solve the problem because the problem lies in scheduling your job using Management Studio through your local machine. If you logged onto your SQL 2005 server that has SP2, you should be able to schedule from there. But it's through Management Studio, which I'm guessing most of you are trying to create a job schedule for your packages. Usually, people don't think of upgrading their client tools as well.
I verified this by upgrading my local machine to SP2 for the client tools and was able to successfully schedule. You might also need to upgrade your server machine to SP2 to work as well.
I hope this helps.
-SX
|||I finally uninstalled all SQL related products and services, reinstalled everything, added hot fixes and finally we have two of the three servers working--mostly. There are still occaisional errors, but most seem limited to SSMS' and its UI
I haven't rolled SP2 to production yet and won't be adding any new SQL servers to our mix until this mess settles. I thought we'd be going to some of the better features (like Mirroring) later this year but now it'll be Q1'08 at the earliest.
Haven't had this much fun since SQL2KSP4! Keep smiling....
|||Hello Visgor Allen and others!
Thank you for reporting this problem, and sorry for the problems that you are experiencing.
I'd like to understand this issue better so we can provide guidance to other customers. Can somebody on this thread please provide more details on how to repro this problem:
1) What is the initial configuration on both server and client machines (if different)? Is it SQL Server 2005 RTM or SP1?
2) Does the problem reproduce after upgrading client/server/both machines to SP2?
3) From what machine (client/server) are you trying to create a new job?
Thanks in advance!
|||Unable to create new jobs in sql 2005, SSIS service is running. Finally i was surfing net for solution and understood need to install SP2 in my machine. But if i need to create new jobs in remote system what should i do.
Please suggest me a solution.
Tuesday, February 14, 2012
Can I remove the ability of sa to create users?
HI, I know what I should do is jus change the password, but there are over
100 jobs and DTS package connections that run with sa auth, and that will
take a long time, unless someone knows how that can be automated to change
all sa users to something else, sorry that's another question. The issue I
have is that I came into a Job where security setting were left wide open,
and as I try to provide security, and tighten things down, I have users who
know the sa PW and can go in create a new local ID and set themselves as SA,
System Administrator. Although they should be delt with by admin, that's
another story... SO question is how can I disallow sa from creating
logins, AND how can I change all job, and DTS connections (anything that
uses sa creds) to something else? PLEASE... Thanks you.You basically can't deny anything to SA. Giving out the SA password is a
VERY bad thing to do. Your choices are to change it or fire everyone who
knows it.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"WANNABE" <breichenbach AT istate DOT com> wrote in message
news:ueC1Pm5xGHA.2168@.TK2MSFTNGP06.phx.gbl...
> HI, I know what I should do is jus change the password, but there are
> over 100 jobs and DTS package connections that run with sa auth, and that
> will take a long time, unless someone knows how that can be automated to
> change all sa users to something else, sorry that's another question. The
> issue I have is that I came into a Job where security setting were left
> wide open, and as I try to provide security, and tighten things down, I
> have users who know the sa PW and can go in create a new local ID and set
> themselves as SA, System Administrator. Although they should be delt with
> by admin, that's another story... SO question is how can I disallow sa
> from creating logins, AND how can I change all job, and DTS connections
> (anything that uses sa creds) to something else? PLEASE... Thanks you.
>|||Thanks Roger, That is what I thought.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:uCJGrG8xGHA.4960@.TK2MSFTNGP05.phx.gbl...
> You basically can't deny anything to SA. Giving out the SA password is a
> VERY bad thing to do. Your choices are to change it or fire everyone who
> knows it.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "WANNABE" <breichenbach AT istate DOT com> wrote in message
> news:ueC1Pm5xGHA.2168@.TK2MSFTNGP06.phx.gbl...
>> HI, I know what I should do is jus change the password, but there are
>> over 100 jobs and DTS package connections that run with sa auth, and that
>> will take a long time, unless someone knows how that can be automated to
>> change all sa users to something else, sorry that's another question.
>> The issue I have is that I came into a Job where security setting were
>> left wide open, and as I try to provide security, and tighten things
>> down, I have users who know the sa PW and can go in create a new local ID
>> and set themselves as SA, System Administrator. Although they should be
>> delt with by admin, that's another story... SO question is how can I
>> disallow sa from creating logins, AND how can I change all job, and DTS
>> connections (anything that uses sa creds) to something else? PLEASE...
>> Thanks you.
>
100 jobs and DTS package connections that run with sa auth, and that will
take a long time, unless someone knows how that can be automated to change
all sa users to something else, sorry that's another question. The issue I
have is that I came into a Job where security setting were left wide open,
and as I try to provide security, and tighten things down, I have users who
know the sa PW and can go in create a new local ID and set themselves as SA,
System Administrator. Although they should be delt with by admin, that's
another story... SO question is how can I disallow sa from creating
logins, AND how can I change all job, and DTS connections (anything that
uses sa creds) to something else? PLEASE... Thanks you.You basically can't deny anything to SA. Giving out the SA password is a
VERY bad thing to do. Your choices are to change it or fire everyone who
knows it.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"WANNABE" <breichenbach AT istate DOT com> wrote in message
news:ueC1Pm5xGHA.2168@.TK2MSFTNGP06.phx.gbl...
> HI, I know what I should do is jus change the password, but there are
> over 100 jobs and DTS package connections that run with sa auth, and that
> will take a long time, unless someone knows how that can be automated to
> change all sa users to something else, sorry that's another question. The
> issue I have is that I came into a Job where security setting were left
> wide open, and as I try to provide security, and tighten things down, I
> have users who know the sa PW and can go in create a new local ID and set
> themselves as SA, System Administrator. Although they should be delt with
> by admin, that's another story... SO question is how can I disallow sa
> from creating logins, AND how can I change all job, and DTS connections
> (anything that uses sa creds) to something else? PLEASE... Thanks you.
>|||Thanks Roger, That is what I thought.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:uCJGrG8xGHA.4960@.TK2MSFTNGP05.phx.gbl...
> You basically can't deny anything to SA. Giving out the SA password is a
> VERY bad thing to do. Your choices are to change it or fire everyone who
> knows it.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "WANNABE" <breichenbach AT istate DOT com> wrote in message
> news:ueC1Pm5xGHA.2168@.TK2MSFTNGP06.phx.gbl...
>> HI, I know what I should do is jus change the password, but there are
>> over 100 jobs and DTS package connections that run with sa auth, and that
>> will take a long time, unless someone knows how that can be automated to
>> change all sa users to something else, sorry that's another question.
>> The issue I have is that I came into a Job where security setting were
>> left wide open, and as I try to provide security, and tighten things
>> down, I have users who know the sa PW and can go in create a new local ID
>> and set themselves as SA, System Administrator. Although they should be
>> delt with by admin, that's another story... SO question is how can I
>> disallow sa from creating logins, AND how can I change all job, and DTS
>> connections (anything that uses sa creds) to something else? PLEASE...
>> Thanks you.
>
Can I remove the ability of sa to create users?
HI, I know what I should do is jus change the password, but there are over
100 jobs and DTS package connections that run with sa auth, and that will
take a long time, unless someone knows how that can be automated to change
all sa users to something else, sorry that's another question. The issue I
have is that I came into a Job where security setting were left wide open,
and as I try to provide security, and tighten things down, I have users who
know the sa PW and can go in create a new local ID and set themselves as SA,
System Administrator. Although they should be delt with by admin, that's
another story... SO question is how can I disallow sa from creating
logins, AND how can I change all job, and DTS connections (anything that
uses sa creds) to something else? PLEASE... Thanks you.You basically can't deny anything to SA. Giving out the SA password is a
VERY bad thing to do. Your choices are to change it or fire everyone who
knows it.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"WANNABE" <breichenbach AT istate DOT com> wrote in message
news:ueC1Pm5xGHA.2168@.TK2MSFTNGP06.phx.gbl...
> HI, I know what I should do is jus change the password, but there are
> over 100 jobs and DTS package connections that run with sa auth, and that
> will take a long time, unless someone knows how that can be automated to
> change all sa users to something else, sorry that's another question. The
> issue I have is that I came into a Job where security setting were left
> wide open, and as I try to provide security, and tighten things down, I
> have users who know the sa PW and can go in create a new local ID and set
> themselves as SA, System Administrator. Although they should be delt with
> by admin, that's another story... SO question is how can I disallow sa
> from creating logins, AND how can I change all job, and DTS connections
> (anything that uses sa creds) to something else? PLEASE... Thanks you.
>|||Thanks Roger, That is what I thought.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:uCJGrG8xGHA.4960@.TK2MSFTNGP05.phx.gbl...
> You basically can't deny anything to SA. Giving out the SA password is a
> VERY bad thing to do. Your choices are to change it or fire everyone who
> knows it.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "WANNABE" <breichenbach AT istate DOT com> wrote in message
> news:ueC1Pm5xGHA.2168@.TK2MSFTNGP06.phx.gbl...
>
100 jobs and DTS package connections that run with sa auth, and that will
take a long time, unless someone knows how that can be automated to change
all sa users to something else, sorry that's another question. The issue I
have is that I came into a Job where security setting were left wide open,
and as I try to provide security, and tighten things down, I have users who
know the sa PW and can go in create a new local ID and set themselves as SA,
System Administrator. Although they should be delt with by admin, that's
another story... SO question is how can I disallow sa from creating
logins, AND how can I change all job, and DTS connections (anything that
uses sa creds) to something else? PLEASE... Thanks you.You basically can't deny anything to SA. Giving out the SA password is a
VERY bad thing to do. Your choices are to change it or fire everyone who
knows it.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"WANNABE" <breichenbach AT istate DOT com> wrote in message
news:ueC1Pm5xGHA.2168@.TK2MSFTNGP06.phx.gbl...
> HI, I know what I should do is jus change the password, but there are
> over 100 jobs and DTS package connections that run with sa auth, and that
> will take a long time, unless someone knows how that can be automated to
> change all sa users to something else, sorry that's another question. The
> issue I have is that I came into a Job where security setting were left
> wide open, and as I try to provide security, and tighten things down, I
> have users who know the sa PW and can go in create a new local ID and set
> themselves as SA, System Administrator. Although they should be delt with
> by admin, that's another story... SO question is how can I disallow sa
> from creating logins, AND how can I change all job, and DTS connections
> (anything that uses sa creds) to something else? PLEASE... Thanks you.
>|||Thanks Roger, That is what I thought.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:uCJGrG8xGHA.4960@.TK2MSFTNGP05.phx.gbl...
> You basically can't deny anything to SA. Giving out the SA password is a
> VERY bad thing to do. Your choices are to change it or fire everyone who
> knows it.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "WANNABE" <breichenbach AT istate DOT com> wrote in message
> news:ueC1Pm5xGHA.2168@.TK2MSFTNGP06.phx.gbl...
>
Subscribe to:
Posts (Atom)