Cannot Edit Jobs

Two days back we have installed SP2 on SQLServer2005 Active/Active Cluster which result in failure.

Only Database Services and Analysis Services where not updated and rest of the services got updated.

After a restart , the behaviour of SQLServer is helarious.

We got into lot of problem so we opened support from Microsoft.

One of the problem i forgot to mentioed to Microsoft was on editing the Job i cannot see anything inside,all the entries where empty closing the job window and opening it again i got all my entries back but on editing i got the below mentioned Error.

Error:

Creating an instance of the COM component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from the IClassFactory failed due to the following error:c001f011(Microsoft.SqlServer.ManagedDTS)

If anyone faced the same problem and got any resolution please let me know.

Anyhelp will be appriciated.

Solved the Error.

In one of the artical i read tht after installation of SP2 few of the DLL left unregistered.

Registered the DTS.DLL and it work like charm.

"C:\Program Files\Microsoft SQL Server\90\DTS\Binn>regsvr32 dts.dll"

Hope this help to others.

sql

Cannot edit jobs

i am get this error message every time I try to remove some old jobs that
were created on a different server:
error 14274: cannot add, update,or delete a job (or its step or
schedules) that originated from an msx server
What do I need to do to remove these jobs?
Either remove them from the master server. Or hack msdb..sysjobs (originating_server column to the
name for your server). Some info found here (adapt to your needs):
http://www.karaszi.com/SQLServer/inf...erver_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Takia" <Takia@.discussions.microsoft.com> wrote in message
news:527F2E42-BDF8-4968-B717-4BDA27347FDB@.microsoft.com...
>i am get this error message every time I try to remove some old jobs that
> were created on a different server:
> error 14274: cannot add, update,or delete a job (or its step or
> schedules) that originated from an msx server
> What do I need to do to remove these jobs?
>

Cannot edit jobs

i am get this error message every time I try to remove some old jobs that
were created on a different server:
error 14274: cannot add, update,or delete a job (or its step or
schedules) that originated from an msx server
What do I need to do to remove these jobs?Either remove them from the master server. Or hack msdb..sysjobs (originatin
g_server column to the
name for your server). Some info found here (adapt to your needs):
http://www.karaszi.com/SQLServer/in...server_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Takia" <Takia@.discussions.microsoft.com> wrote in message
news:527F2E42-BDF8-4968-B717-4BDA27347FDB@.microsoft.com...
>i am get this error message every time I try to remove some old jobs that
> were created on a different server:
> error 14274: cannot add, update,or delete a job (or its step or
> schedules) that originated from an msx server
> What do I need to do to remove these jobs?
>

Cannot edit jobs

i am get this error message every time I try to remove some old jobs that
were created on a different server:
error 14274: cannot add, update,or delete a job (or its step or
schedules) that originated from an msx server
What do I need to do to remove these jobs?Either remove them from the master server. Or hack msdb..sysjobs (originating_server column to the
name for your server). Some info found here (adapt to your needs):
http://www.karaszi.com/SQLServer/info_change_server_name.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Takia" <Takia@.discussions.microsoft.com> wrote in message
news:527F2E42-BDF8-4968-B717-4BDA27347FDB@.microsoft.com...
>i am get this error message every time I try to remove some old jobs that
> were created on a different server:
> error 14274: cannot add, update,or delete a job (or its step or
> schedules) that originated from an msx server
> What do I need to do to remove these jobs?
>

Cannot delete SQL Job

I have several jobs in SQL 2005 that I cannot delete. I get "The DELETE statement conflicted with the REFERENCE constraint "FK_subplan_job_id" the conflict occured in database "msdb", table "dbo.sysmaintplan_subplans" columd 'job_id'.

How can I fix this?

TIA <JP>

Hello my friend,

It looks like the job you are trying to delete is used in another job. Delete this other job and then it should let you delete it.

Kind regards

Scotty

|||

Scotty,

How do I identify other dependencies? I see nothing obvious poking me in the eye. I have several of these and can't figure it out. Could it be because I'm running in a cluster?

Cannot delete or edit transfered SQL Server Jobs

Hello,

I have a problem with EM and the msdb. I get an error message 14274
when I try to edit or delete a job. The data in the msdb for the jobs
was generated by a restored backup that came from another machine, and
a different instance of SQL Server. The old default server instance
was called 'SQL_Server' and the new default instance is called
'SDO-SQL'.
The error message states:

Cannot add, update, or delete a job (or its steps or schedules) that
originated from an MSX server.

I don't have a master scheduling server. I get the error
message when attempting to change a job. eg. enable/disable a job,
change the time, delete a job, add a job.

Server is running w2k Server SP4

I tired the following:

USE MSDB

UPDATE sysjobs

SET originating_server = 'SD0-SQL'

From the properties of any job, I can see that the 'Source' is now
correctly identified as 'SDO-SQL', but the problem still remains.

What can I do with these jobs so that I can edit and delete them on
the new server?

Thank you for your help!

CSDunnHi

It looks like you may have already seen

http://support.microsoft.com/defaul...kb;en-us;281642

It suggests that you rename the server back to the old server name rather
than mess with the tables, but if you are trying to update sysjob I would
expect originating_server to be in the form 'server\instance'.

John

"CSDunn" <cdunn@.valverde.edu> wrote in message
news:807dbff7.0405151632.2f68ffe8@.posting.google.c om...
> Hello,
> I have a problem with EM and the msdb. I get an error message 14274
> when I try to edit or delete a job. The data in the msdb for the jobs
> was generated by a restored backup that came from another machine, and
> a different instance of SQL Server. The old default server instance
> was called 'SQL_Server' and the new default instance is called
> 'SDO-SQL'.
> The error message states:
> Cannot add, update, or delete a job (or its steps or schedules) that
> originated from an MSX server.
> I don't have a master scheduling server. I get the error
> message when attempting to change a job. eg. enable/disable a job,
> change the time, delete a job, add a job.
> Server is running w2k Server SP4
> I tired the following:
> USE MSDB
> UPDATE sysjobs
> SET originating_server = 'SD0-SQL'
> From the properties of any job, I can see that the 'Source' is now
> correctly identified as 'SDO-SQL', but the problem still remains.
> What can I do with these jobs so that I can edit and delete them on
> the new server?
> Thank you for your help!
> CSDunn|||John,
Thank you for your help!

CSDunn

"John Bell" <jbellnewsposts@.hotmail.com> wrote in message news:<0lEpc.948$XY4.12507228@.news-text.cableinet.net>...
> Hi
> It looks like you may have already seen
> http://support.microsoft.com/defaul...kb;en-us;281642
> It suggests that you rename the server back to the old server name rather
> than mess with the tables, but if you are trying to update sysjob I would
> expect originating_server to be in the form 'server\instance'.
> John
> "CSDunn" <cdunn@.valverde.edu> wrote in message
> news:807dbff7.0405151632.2f68ffe8@.posting.google.c om...
> > Hello,
> > I have a problem with EM and the msdb. I get an error message 14274
> > when I try to edit or delete a job. The data in the msdb for the jobs
> > was generated by a restored backup that came from another machine, and
> > a different instance of SQL Server. The old default server instance
> > was called 'SQL_Server' and the new default instance is called
> > 'SDO-SQL'.
> > The error message states:
> > Cannot add, update, or delete a job (or its steps or schedules) that
> > originated from an MSX server.
> > I don't have a master scheduling server. I get the error
> > message when attempting to change a job. eg. enable/disable a job,
> > change the time, delete a job, add a job.
> > Server is running w2k Server SP4
> > I tired the following:
> > USE MSDB
> > UPDATE sysjobs
> > SET originating_server = 'SD0-SQL'
> > From the properties of any job, I can see that the 'Source' is now
> > correctly identified as 'SDO-SQL', but the problem still remains.
> > What can I do with these jobs so that I can edit and delete them on
> > the new server?
> > Thank you for your help!
> > CSDunn|||I found another workaround (OS W2K3 Server, SQL Server 2K with SP4):

1. Script out all of the jobs.
2. Update the job source by:
USE MSDB
UPDATE sysjobs
SET originating_server = 'New_Server_Name'
3. Rename the jobs to be deleted.
4. Delete the jobs.
5. Add back the jobs by running the script generated from step 1.

Hope this will work better!

Ray

Cannot Delete Job

I used the DTS transfer Jobs to copy a couple of jobs from one server to
another, I now aant to delete those jobs on the target server but I get an
error saying
"Error14274" Cannot add, update, or delete a job (or its steps or
schedule) that originated from an MSX server"
How can I delete these jobs I urgently need to get rid of these....
Thanks for your help,
BrianYou are using an MSX and TSX server, which means that the job you have on
your server was targetted from a master server.
The targetted client can not delete the job, it needs to be done on the
master server.
Check books online on master server jobs
To defect a target server from a master server
1.. Expand a server group, and then expand a server configured as a target
server.
2.. Expand Management.
3.. Right-click SQL Server Agent, point to Multi Server Administration,
and then click Defect from MSX.
4.. Click Yes to confirm that you want to defect this target server from a
master server.
Regards,
Dandy Weyn
MCSE, MCSA, MCDBA, MCT
www.dandyman.net
"Brian" <bfordSPAMOFF@.markem.com> wrote in message
news:%23Gw%23YoR3DHA.3936@.TK2MSFTNGP11.phx.gbl...

quote:

---

> I used the DTS transfer Jobs to copy a couple of jobs from one server to
> another, I now aant to delete those jobs on the target server but I get

---

an

quote:

---

> error saying
> "Error14274" Cannot add, update, or delete a job (or its steps or
> schedule) that originated from an MSX server"
> How can I delete these jobs I urgently need to get rid of these....
> Thanks for your help,
> Brian
>

---

|||Dandy,
Thank you very much for your response, however, I am not using an MSX and
TXS server, at least not knowingly. When I right click Server Agent, I only
get the options to make the server a Master or a Target, is there anyway
that I can edit a system table to remove these?
The original server that the jobs came from will be going away today......
Thanks again,
Brian
"Dandy Weyn" <mct@.dandyman_nospam.net> wrote in message
news:40096d0e$0$773$ba620e4c@.news.skynet.be...

quote:

---

> You are using an MSX and TSX server, which means that the job you have on
> your server was targetted from a master server.
> The targetted client can not delete the job, it needs to be done on the
> master server.
> Check books online on master server jobs
> To defect a target server from a master server
> 1.. Expand a server group, and then expand a server configured as a

---

target

quote:

---

> server.
>
> 2.. Expand Management.
>
> 3.. Right-click SQL Server Agent, point to Multi Server Administration,
> and then click Defect from MSX.
>
> 4.. Click Yes to confirm that you want to defect this target server from

---

a

quote:

---

> master server.
> --
> Regards,
> Dandy Weyn
> MCSE, MCSA, MCDBA, MCT
> www.dandyman.net
> "Brian" <bfordSPAMOFF@.markem.com> wrote in message
> news:%23Gw%23YoR3DHA.3936@.TK2MSFTNGP11.phx.gbl...
> an
>

---

|||Brian,
I am interested in the answer to this one too. My situation occurred becaus
e we renamed the server and sql name when jobs were still there. now the or
iginal server doesnt exist but the jobs do. I've tried removejobbyid method.
The next thing I was look
at is how to defect a master server. these servers are not really multi-hom
ed, they just think they are because the owner of the job is not part of the
new sql server. sp_help_job will tell you who owns it
Mitch|||Brian
check out Can't delete job.
Tibor put a script in there that fixed it for me
mitchsql

Cannot Delete Job

I used the DTS transfer Jobs to copy a couple of jobs from one server to
another, I now aant to delete those jobs on the target server but I get an
error saying
"Error14274" Cannot add, update, or delete a job (or its steps or
schedule) that originated from an MSX server"
How can I delete these jobs I urgently need to get rid of these....
Thanks for your help,
BrianYou are using an MSX and TSX server, which means that the job you have on
your server was targetted from a master server.
The targetted client can not delete the job, it needs to be done on the
master server.
Check books online on master server jobs
To defect a target server from a master server
1.. Expand a server group, and then expand a server configured as a target
server.
2.. Expand Management.
3.. Right-click SQL Server Agent, point to Multi Server Administration,
and then click Defect from MSX.
4.. Click Yes to confirm that you want to defect this target server from a
master server.
--
Regards,
Dandy Weyn
MCSE, MCSA, MCDBA, MCT
www.dandyman.net
"Brian" <bfordSPAMOFF@.markem.com> wrote in message
news:%23Gw%23YoR3DHA.3936@.TK2MSFTNGP11.phx.gbl...
> I used the DTS transfer Jobs to copy a couple of jobs from one server to
> another, I now aant to delete those jobs on the target server but I get
an
> error saying
> "Error14274" Cannot add, update, or delete a job (or its steps or
> schedule) that originated from an MSX server"
> How can I delete these jobs I urgently need to get rid of these....
> Thanks for your help,
> Brian
>|||Dandy,
Thank you very much for your response, however, I am not using an MSX and
TXS server, at least not knowingly. When I right click Server Agent, I only
get the options to make the server a Master or a Target, is there anyway
that I can edit a system table to remove these?
The original server that the jobs came from will be going away today......
Thanks again,
Brian
"Dandy Weyn" <mct@.dandyman_nospam.net> wrote in message
news:40096d0e$0$773$ba620e4c@.news.skynet.be...
> You are using an MSX and TSX server, which means that the job you have on
> your server was targetted from a master server.
> The targetted client can not delete the job, it needs to be done on the
> master server.
> Check books online on master server jobs
> To defect a target server from a master server
> 1.. Expand a server group, and then expand a server configured as a
target
> server.
>
> 2.. Expand Management.
>
> 3.. Right-click SQL Server Agent, point to Multi Server Administration,
> and then click Defect from MSX.
>
> 4.. Click Yes to confirm that you want to defect this target server from
a
> master server.
> --
> Regards,
> Dandy Weyn
> MCSE, MCSA, MCDBA, MCT
> www.dandyman.net
> "Brian" <bfordSPAMOFF@.markem.com> wrote in message
> news:%23Gw%23YoR3DHA.3936@.TK2MSFTNGP11.phx.gbl...
> > I used the DTS transfer Jobs to copy a couple of jobs from one server to
> > another, I now aant to delete those jobs on the target server but I get
> an
> > error saying
> >
> > "Error14274" Cannot add, update, or delete a job (or its steps or
> > schedule) that originated from an MSX server"
> >
> > How can I delete these jobs I urgently need to get rid of these....
> >
> > Thanks for your help,
> >
> > Brian
> >
> >
>

cannot create jobs on x64

Hi all,
Just installed sql 2005 x64 (DB Server + Client Tools incl. management tools) on a win2003 x64 server and encountered the following problems:

1) Could not create 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 does not help.
- Installing with or without Integration Service does not help.

Any help is highly appreciated

TIA
Dan

Just as a checkup, have you installed SQLExpress before on thsi machine?

refer to KBA http://support.microsoft.com/kb/922214 for more information.

|||

No express installation before.

TIA
acki

|||

Just as a little add on.

I cannot create the jobs in management console.
If I create a job by script, job shows up under SQL Server Agent / Jobs but detail view of job contains no data (no jobsteps, no schedule, no name)

If I check jobdeails in detailed Activity Monitor view all looks fine ?

Please advice

acki

|||Check here http://connect.microsoft.com/ whether this has been reported, if not I suggest to report for a fix.|||Anyone learn anything on this? I have the same problems after installing the SQL Server 2005 Service Pack 2 for XP (SQLServer2005SP2-KB921896-x86-ENU.exe)?|||

gfay

I just got this realy helpful comment on a feedback I supplied to Microsoft:

"Thanks for letting us know about the problems you faced making agent jobs.

Because the problems are in the original setup, there is no way for us to address them in a service pack. I have, however, added this issue to the work items for our next major release. "

|||

Hi Guys

We succeded create job remotly (from another computer 32 bit SQL (x86))

but when you open it from x64 edition you cannot see the steps

|||Thanks (acki4711) for the info!
|||had same problem on x86 version. Reapplying SP2 to client tools on the server was the solution for me.|||

Make sure the client and server are up to date with all patches (especially if you're on SP2) and are at the same version level.

cannot create jobs on x64

Hi all,
Just installed sql 2005 x64 (DB Server + Client Tools incl. management tools) and encountered the following problems:

1) Could not create 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 does not help?

Any help is highly appreciated

TIA
Dan

I get the same error when I try to remotly run commands. It seems to be a problem with remote connections. In my situation the server is on another domain and that may be the problem.|||

Please post this to the "SQL Server Tools General" forum.

Thanks,

Peter Saddow

|||Check whether your MS Distributed Transaction Coordinator service is running or not. If not start the service.

cannot create jobs on x64

Hi all,
Just installed sql 2005 x64 (DB Server + Client Tools incl. management tools) and encountered the following problems:

1) Could not create 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 does not help?

Any help is highly appreciated

TIA
Dan

I get the same error when I try to remotly run commands. It seems to be a problem with remote connections. In my situation the server is on another domain and that may be the problem.|||

Please post this to the "SQL Server Tools General" forum.

Thanks,

Peter Saddow

|||Check whether your MS Distributed Transaction Coordinator service is running or not. If not start the service.

cannot create jobs on x64

Hi all,
Just installed sql 2005 x64 (DB Server + Client Tools incl. management tools) on a win2003 x64 server and encountered the following problems:

1) Could not create 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 does not help.
- Installing with or without Integration Service does not help.

Any help is highly appreciated

TIA
Dan

Just as a checkup, have you installed SQLExpress before on thsi machine?

refer to KBA http://support.microsoft.com/kb/922214 for more information.

|||

No express installation before.

TIA
acki

|||

Just as a little add on.

I cannot create the jobs in management console.
If I create a job by script, job shows up under SQL Server Agent / Jobs but detail view of job contains no data (no jobsteps, no schedule, no name)

If I check jobdeails in detailed Activity Monitor view all looks fine ?

Please advice

acki

|||Check here http://connect.microsoft.com/ whether this has been reported, if not I suggest to report for a fix.|||Anyone learn anything on this? I have the same problems after installing the SQL Server 2005 Service Pack 2 for XP (SQLServer2005SP2-KB921896-x86-ENU.exe)?|||

gfay

I just got this realy helpful comment on a feedback I supplied to Microsoft:

"Thanks for letting us know about the problems you faced making agent jobs.

Because the problems are in the original setup, there is no way for us to address them in a service pack. I have, however, added this issue to the work items for our next major release. "

|||

Hi Guys

We succeded create job remotly (from another computer 32 bit SQL (x86))

but when you open it from x64 edition you cannot see the steps

|||Thanks (acki4711) for the info!|||had same problem on x86 version. Reapplying SP2 to client tools on the server was the solution for me.|||

Make sure the client and server are up to date with all patches (especially if you're on SP2) and are at the same version level.

cannot create jobs on x64

Hi all,
Just installed sql 2005 x64 (DB Server + Client Tools incl. management tools) on a win2003 x64 server and encountered the following problems:

1) Could not create 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 does not help.
- Installing with or without Integration Service does not help.

Any help is highly appreciated

TIA
Dan

Just as a checkup, have you installed SQLExpress before on thsi machine?

refer to KBA http://support.microsoft.com/kb/922214 for more information.

|||

No express installation before.

TIA
acki

|||

Just as a little add on.

I cannot create the jobs in management console.
If I create a job by script, job shows up under SQL Server Agent / Jobs but detail view of job contains no data (no jobsteps, no schedule, no name)

If I check jobdeails in detailed Activity Monitor view all looks fine ?

Please advice

acki

|||Check here http://connect.microsoft.com/ whether this has been reported, if not I suggest to report for a fix.|||Anyone learn anything on this? I have the same problems after installing the SQL Server 2005 Service Pack 2 for XP (SQLServer2005SP2-KB921896-x86-ENU.exe)?|||

gfay

I just got this realy helpful comment on a feedback I supplied to Microsoft:

"Thanks for letting us know about the problems you faced making agent jobs.

Because the problems are in the original setup, there is no way for us to address them in a service pack. I have, however, added this issue to the work items for our next major release. "

|||

Hi Guys

We succeded create job remotly (from another computer 32 bit SQL (x86))

but when you open it from x64 edition you cannot see the steps

|||Thanks (acki4711) for the info!|||had same problem on x86 version. Reapplying SP2 to client tools on the server was the solution for me.|||

Make sure the client and server are up to date with all patches (especially if you're on SP2) and are at the same version level.

Cannot create diagram and not run jobs with my domain account logi

Hi!
I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in with
my domain account (HIK\Tommy) wich is a member of the Administrators group on
my computer and there is a corresponding Windows login account with sysadmin
permissions in SQL Server.
I can do most things with that account, BUT when I try to create a diagram
to a database. SQL does not like the owner of the database (my domain
account)
This is the error message that show up:
"Database diagram support objects cannot be installed because this database
does not have a valid owner. To continue, first use the Files page of the
Database Properties dialog box or ALTER AUTHORIZATION statement to set the
database owner to a valid login, then add the database diagram support
objects."
Again when I try to run a job that is owned by my domain account (HIK\Tommy)
Following message arise:
"The job failed. Unable to determine if the owner (HIK\Tommy) of job
MaintenancePlan2 has server access (reason: Could not obtain information
about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE 42000]
(Error 15404) The statement has been terminated. [SQLSTATE 01000] (Error
3621))."
I would be very grateful if you could come up with some suggestions.
Regards
TommyThis might be due to a mismatch between the 'dbo' user mapping and the
actual database owner. You can correct this with sp_changedbowner:
USE MyDatabase
EXEC sp_changedbowner 'HIK\Tommy'
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Tommy" <Tommy@.discussions.microsoft.com> wrote in message
news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
> Hi!
> I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in with
> my domain account (HIK\Tommy) wich is a member of the Administrators group
> on
> my computer and there is a corresponding Windows login account with
> sysadmin
> permissions in SQL Server.
> I can do most things with that account, BUT when I try to create a diagram
> to a database. SQL does not like the owner of the database (my domain
> account)
> This is the error message that show up:
> "Database diagram support objects cannot be installed because this
> database
> does not have a valid owner. To continue, first use the Files page of the
> Database Properties dialog box or ALTER AUTHORIZATION statement to set the
> database owner to a valid login, then add the database diagram support
> objects."
> Again when I try to run a job that is owned by my domain account
> (HIK\Tommy)
> Following message arise:
> "The job failed. Unable to determine if the owner (HIK\Tommy) of job
> MaintenancePlan2 has server access (reason: Could not obtain information
> about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE 42000]
> (Error 15404) The statement has been terminated. [SQLSTATE 01000] (Error
> 3621))."
> I would be very grateful if you could come up with some suggestions.
> Regards
> Tommy|||Thanks for your suggestion but it does not work.
USE MyDatabase
EXEC sp_changedbowner 'HIK\Tommy'
doesn't change anything.
On the other hand it 's possible to change user to sa and everything works
OK, so it's my domain name that is the trouble. Have never had this problem i
SQL Server 2K.
/Tommy
"Dan Guzman" wrote:
> This might be due to a mismatch between the 'dbo' user mapping and the
> actual database owner. You can correct this with sp_changedbowner:
> USE MyDatabase
> EXEC sp_changedbowner 'HIK\Tommy'
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
> news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
> > Hi!
> > I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in with
> > my domain account (HIK\Tommy) wich is a member of the Administrators group
> > on
> > my computer and there is a corresponding Windows login account with
> > sysadmin
> > permissions in SQL Server.
> >
> > I can do most things with that account, BUT when I try to create a diagram
> > to a database. SQL does not like the owner of the database (my domain
> > account)
> >
> > This is the error message that show up:
> > "Database diagram support objects cannot be installed because this
> > database
> > does not have a valid owner. To continue, first use the Files page of the
> > Database Properties dialog box or ALTER AUTHORIZATION statement to set the
> > database owner to a valid login, then add the database diagram support
> > objects."
> >
> > Again when I try to run a job that is owned by my domain account
> > (HIK\Tommy)
> >
> > Following message arise:
> >
> > "The job failed. Unable to determine if the owner (HIK\Tommy) of job
> > MaintenancePlan2 has server access (reason: Could not obtain information
> > about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE 42000]
> > (Error 15404) The statement has been terminated. [SQLSTATE 01000] (Error
> > 3621))."
> >
> > I would be very grateful if you could come up with some suggestions.
> >
> > Regards
> > Tommy
>
>|||My apologies but I misread your post. I guess I should a finished my coffee
first :-)
For your first issue, the database needs to be in 90 compatibility mode in
order to create diagrams.
Regarding your second problem, run the SQL Server Configuration utility to
make sure the SQL Agent isn't running under the Network Service account.
Use a domain account.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Tommy" <Tommy@.discussions.microsoft.com> wrote in message
news:753C2D7A-C719-4B67-8CCD-0E3A03A9B8D5@.microsoft.com...
> Thanks for your suggestion but it does not work.
> USE MyDatabase
> EXEC sp_changedbowner 'HIK\Tommy'
> doesn't change anything.
> On the other hand it 's possible to change user to sa and everything works
> OK, so it's my domain name that is the trouble. Have never had this
> problem i
> SQL Server 2K.
> /Tommy
> "Dan Guzman" wrote:
>> This might be due to a mismatch between the 'dbo' user mapping and the
>> actual database owner. You can correct this with sp_changedbowner:
>> USE MyDatabase
>> EXEC sp_changedbowner 'HIK\Tommy'
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
>> news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
>> > Hi!
>> > I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in
>> > with
>> > my domain account (HIK\Tommy) wich is a member of the Administrators
>> > group
>> > on
>> > my computer and there is a corresponding Windows login account with
>> > sysadmin
>> > permissions in SQL Server.
>> >
>> > I can do most things with that account, BUT when I try to create a
>> > diagram
>> > to a database. SQL does not like the owner of the database (my domain
>> > account)
>> >
>> > This is the error message that show up:
>> > "Database diagram support objects cannot be installed because this
>> > database
>> > does not have a valid owner. To continue, first use the Files page of
>> > the
>> > Database Properties dialog box or ALTER AUTHORIZATION statement to set
>> > the
>> > database owner to a valid login, then add the database diagram support
>> > objects."
>> >
>> > Again when I try to run a job that is owned by my domain account
>> > (HIK\Tommy)
>> >
>> > Following message arise:
>> >
>> > "The job failed. Unable to determine if the owner (HIK\Tommy) of job
>> > MaintenancePlan2 has server access (reason: Could not obtain
>> > information
>> > about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE
>> > 42000]
>> > (Error 15404) The statement has been terminated. [SQLSTATE 01000]
>> > (Error
>> > 3621))."
>> >
>> > I would be very grateful if you could come up with some suggestions.
>> >
>> > Regards
>> > Tommy
>>|||Using a domain account for the Agent and SQL Server service solves the
problem with recognizeing job owner as my domain login (HIK\Tommy), but it
still don't like my domain login as database owner when trying to create a
diagram.
My administrator don't want me to use a domain account for services for
security reasons so, I'm going to use a workaround, e.g. use sa as owner
until this bug (?) is fixed.
Thank's anyway
Tommy
"Dan Guzman" wrote:
> My apologies but I misread your post. I guess I should a finished my coffee
> first :-)
> For your first issue, the database needs to be in 90 compatibility mode in
> order to create diagrams.
> Regarding your second problem, run the SQL Server Configuration utility to
> make sure the SQL Agent isn't running under the Network Service account.
> Use a domain account.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
> news:753C2D7A-C719-4B67-8CCD-0E3A03A9B8D5@.microsoft.com...
> > Thanks for your suggestion but it does not work.
> >
> > USE MyDatabase
> > EXEC sp_changedbowner 'HIK\Tommy'
> >
> > doesn't change anything.
> >
> > On the other hand it 's possible to change user to sa and everything works
> > OK, so it's my domain name that is the trouble. Have never had this
> > problem i
> > SQL Server 2K.
> >
> > /Tommy
> >
> > "Dan Guzman" wrote:
> >
> >> This might be due to a mismatch between the 'dbo' user mapping and the
> >> actual database owner. You can correct this with sp_changedbowner:
> >>
> >> USE MyDatabase
> >> EXEC sp_changedbowner 'HIK\Tommy'
> >>
> >> --
> >> Hope this helps.
> >>
> >> Dan Guzman
> >> SQL Server MVP
> >>
> >> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
> >> news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
> >> > Hi!
> >> > I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in
> >> > with
> >> > my domain account (HIK\Tommy) wich is a member of the Administrators
> >> > group
> >> > on
> >> > my computer and there is a corresponding Windows login account with
> >> > sysadmin
> >> > permissions in SQL Server.
> >> >
> >> > I can do most things with that account, BUT when I try to create a
> >> > diagram
> >> > to a database. SQL does not like the owner of the database (my domain
> >> > account)
> >> >
> >> > This is the error message that show up:
> >> > "Database diagram support objects cannot be installed because this
> >> > database
> >> > does not have a valid owner. To continue, first use the Files page of
> >> > the
> >> > Database Properties dialog box or ALTER AUTHORIZATION statement to set
> >> > the
> >> > database owner to a valid login, then add the database diagram support
> >> > objects."
> >> >
> >> > Again when I try to run a job that is owned by my domain account
> >> > (HIK\Tommy)
> >> >
> >> > Following message arise:
> >> >
> >> > "The job failed. Unable to determine if the owner (HIK\Tommy) of job
> >> > MaintenancePlan2 has server access (reason: Could not obtain
> >> > information
> >> > about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE
> >> > 42000]
> >> > (Error 15404) The statement has been terminated. [SQLSTATE 01000]
> >> > (Error
> >> > 3621))."
> >> >
> >> > I would be very grateful if you could come up with some suggestions.
> >> >
> >> > Regards
> >> > Tommy
> >>
> >>
> >>
>
>|||> My administrator don't want me to use a domain account for services for
> security reasons so, I'm going to use a workaround, e.g. use sa as owner
> until this bug (?) is fixed.
The Books Online (Setting up Windows Accounts) states that it is best is to
use minimally privileged accounts for services. If you don't want to use a
low privilege domain user, you can use a (minimally privileged) local
Windows user account. I don't think this a a bug, it's just that SQL 2005
is more secure out-of-the-box so additional configuration work is needed to
loosen up security according to your organization's security policies.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Tommy" <Tommy@.discussions.microsoft.com> wrote in message
news:ED165CD9-5A84-4D4F-AC22-BF57C87A1A16@.microsoft.com...
> Using a domain account for the Agent and SQL Server service solves the
> problem with recognizeing job owner as my domain login (HIK\Tommy), but it
> still don't like my domain login as database owner when trying to create a
> diagram.
> My administrator don't want me to use a domain account for services for
> security reasons so, I'm going to use a workaround, e.g. use sa as owner
> until this bug (?) is fixed.
> Thank's anyway
> Tommy
> "Dan Guzman" wrote:
>> My apologies but I misread your post. I guess I should a finished my
>> coffee
>> first :-)
>> For your first issue, the database needs to be in 90 compatibility mode
>> in
>> order to create diagrams.
>> Regarding your second problem, run the SQL Server Configuration utility
>> to
>> make sure the SQL Agent isn't running under the Network Service account.
>> Use a domain account.
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
>> news:753C2D7A-C719-4B67-8CCD-0E3A03A9B8D5@.microsoft.com...
>> > Thanks for your suggestion but it does not work.
>> >
>> > USE MyDatabase
>> > EXEC sp_changedbowner 'HIK\Tommy'
>> >
>> > doesn't change anything.
>> >
>> > On the other hand it 's possible to change user to sa and everything
>> > works
>> > OK, so it's my domain name that is the trouble. Have never had this
>> > problem i
>> > SQL Server 2K.
>> >
>> > /Tommy
>> >
>> > "Dan Guzman" wrote:
>> >
>> >> This might be due to a mismatch between the 'dbo' user mapping and the
>> >> actual database owner. You can correct this with sp_changedbowner:
>> >>
>> >> USE MyDatabase
>> >> EXEC sp_changedbowner 'HIK\Tommy'
>> >>
>> >> --
>> >> Hope this helps.
>> >>
>> >> Dan Guzman
>> >> SQL Server MVP
>> >>
>> >> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
>> >> news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
>> >> > Hi!
>> >> > I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging
>> >> > in
>> >> > with
>> >> > my domain account (HIK\Tommy) wich is a member of the Administrators
>> >> > group
>> >> > on
>> >> > my computer and there is a corresponding Windows login account with
>> >> > sysadmin
>> >> > permissions in SQL Server.
>> >> >
>> >> > I can do most things with that account, BUT when I try to create a
>> >> > diagram
>> >> > to a database. SQL does not like the owner of the database (my
>> >> > domain
>> >> > account)
>> >> >
>> >> > This is the error message that show up:
>> >> > "Database diagram support objects cannot be installed because this
>> >> > database
>> >> > does not have a valid owner. To continue, first use the Files page
>> >> > of
>> >> > the
>> >> > Database Properties dialog box or ALTER AUTHORIZATION statement to
>> >> > set
>> >> > the
>> >> > database owner to a valid login, then add the database diagram
>> >> > support
>> >> > objects."
>> >> >
>> >> > Again when I try to run a job that is owned by my domain account
>> >> > (HIK\Tommy)
>> >> >
>> >> > Following message arise:
>> >> >
>> >> > "The job failed. Unable to determine if the owner (HIK\Tommy) of
>> >> > job
>> >> > MaintenancePlan2 has server access (reason: Could not obtain
>> >> > information
>> >> > about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE
>> >> > 42000]
>> >> > (Error 15404) The statement has been terminated. [SQLSTATE 01000]
>> >> > (Error
>> >> > 3621))."
>> >> >
>> >> > I would be very grateful if you could come up with some suggestions.
>> >> >
>> >> > Regards
>> >> > Tommy
>> >>
>> >>
>> >>
>>