Cannot edit SQL Job in Management Studio.

Hello,

In SQL Management Studio, I cannot edit a SQL Job. When I double-click on a sql job or select properties on the context menu, I get a "New Job" window. This was working fine a few days back. Any help will be appreciated.

Thanks,

Ashish.

What happens when you right click and select properties on the job?|||Try installing SQL Server 2005 SP2 on the client. This should solve your problem.|||

I installed SP2 on the client. It didn't help. Thanks for replying back to my post.

Also, we have 3 other developers in the team who are having the same problem.

|||

Thanks for your reply. When I right-click and select properties, I still get the "New Job" window.

|||It could be an issues with SQL tools, have you tried accessing the same job from another client's machine.|||

Hi Satya,

Thanks for your reply. I tried editing the sql job from another computer. I was able to edit it. I know it's issue with the client tools, but cannot figure out to resolve the problem. I installed SP2 on the client side. That also didn't help.

|||You may need to uninstall the client tools, and reinstall them, and also add SP2 again.

Cannot detach the database for previous publications

I had replication job in one database. Since I need to detach the database
and move it somewhere else, I deleted all publications. However when I tried
to detach the db, the error message says that the database cannot be detached
because it is replicated. I updated the statistics of both that database and
distribution database. However the error remains. Please advice.
Thanks,
Charts
Try using sp_dboption to set 'published' and 'merge publish' to false.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Great ! It works. Thanks so much.
"Paul Ibison" wrote:

> Try using sp_dboption to set 'published' and 'merge publish' to false.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>

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 Maintenance Plan job

Hi
I had a Maintenance Plan with a scheduled job setup in SQL 2005. I have
deleted the Plan without deleting the scheduled job. Now I cannot delete the
job without the Plan. Any help will be great appreciated.
I have deleted the job by setting up another maintenance plan. After the new
maintenance plan ran, the orphaned job was deleted. Sorry, I think I should
have posted this on another newsgroup. Thanks!
"Yuhong" wrote:

> Hi
> I had a Maintenance Plan with a scheduled job setup in SQL 2005. I have
> deleted the Plan without deleting the scheduled job. Now I cannot delete the
> job without the Plan. Any help will be great appreciated.

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 Recurring backup

I am not able to create a recurring backup job on sql2005. There is no
schedule option when you right click on database then tasks-->backup, also
when I try to do it thru maintenance plan I am not able to see my databases.
Can someone tell me how to resolve this problem?
Thanks in advance for any help-RobRob wrote:
> I am not able to create a recurring backup job on sql2005. There is no
> schedule option when you right click on database then tasks-->backup, al
so
> when I try to do it thru maintenance plan I am not able to see my database
s.
> Can someone tell me how to resolve this problem?
> Thanks in advance for any help-Rob
Don't use the pointy-clicky interface, instead script your backups.
Create a SQL Agent job that uses the BACKUP DATABASE/BACKUP LOG commands.
http://realsqlguy.com/twiki/bin/vie...realsqlguy.com|||Rob wrote on Wed, 12 Jul 2006 13:39:02 -0700:

> I am not able to create a recurring backup job on sql2005. There is no
> schedule option when you right click on database then tasks-->backup,
> also when I try to do it thru maintenance plan I am not able to see my
> databases. Can someone tell me how to resolve this problem?
> Thanks in advance for any help-Rob
Did you restore these databases from a SQL2000 or older server? If so, they
have compatibility set to 80 or lower, and the Maintenance Plan will ignore
them. Change each database to compatibility 90 and they'll then be
selectable in the GUI maintenance plan.
Dan

Cannot create Recurring backup

I am not able to create a recurring backup job on sql2005. There is no
schedule option when you right click on database then tasks-->backup, also
when I try to do it thru maintenance plan I am not able to see my databases.
Can someone tell me how to resolve this problem?
Thanks in advance for any help-RobRob wrote:
> I am not able to create a recurring backup job on sql2005. There is no
> schedule option when you right click on database then tasks-->backup, also
> when I try to do it thru maintenance plan I am not able to see my databases.
> Can someone tell me how to resolve this problem?
> Thanks in advance for any help-Rob
Don't use the pointy-clicky interface, instead script your backups.
Create a SQL Agent job that uses the BACKUP DATABASE/BACKUP LOG commands.
http://realsqlguy.com/twiki/bin/view/RealSQLGuy/AutomaticBackupOfAllDatabases
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Rob wrote on Wed, 12 Jul 2006 13:39:02 -0700:
> I am not able to create a recurring backup job on sql2005. There is no
> schedule option when you right click on database then tasks-->backup,
> also when I try to do it thru maintenance plan I am not able to see my
> databases. Can someone tell me how to resolve this problem?
> Thanks in advance for any help-Rob
Did you restore these databases from a SQL2000 or older server? If so, they
have compatibility set to 80 or lower, and the Maintenance Plan will ignore
them. Change each database to compatibility 90 and they'll then be
selectable in the GUI maintenance plan.
Dan

cannot create job steps in 2005

I have a feeling this might be a security problem so I posting the question
in the security group as well. Sorry for the double post, I'll paste any
answers over there as well.
Here's the problem;
I'm trying to do some prototyping with SQL 2005 Standard - Full Text Search
in preparation for moving away from SQL 2000. I setup a FTS index and tried
to create a job to rebuild the index nightly. This job build feature is
built right into the
FTS wizard. The job is created but it fails to create the steps and just
says "Failed to connect to server...blah blah blah....Naped Pipes Provider,
Error 40, Could not open connection"
At first I thought it was something with FTS not configured right but then I
just tried to create simple maintenance plan job and the same thing
happened. It
couldn't create the job step. The message from that was even more helpful.
It said "Job failed" I'm doing all this from SSMS logged in with SA.
Anyone have any idea why I can't create job steps on a newly installed SQL
2005 using SA?
Thanks in advance
--
MazSome of the things to check for:
- Make sure that the 'shared memory' prtocol is enabled on the server and
has order=1
- Make sure that sql server is configured to listen on the shared memory net
lib
You can check the settings using the SQL Server Configuration Manager.
hth
--
Vikram Vamshi
Database Engineer
Eclipsys Corporation
"Spicy Mikey" <Maz@.newsgroups.nospam> wrote in message
news:A993F690-0AC3-4FA6-9760-85C2F24523C8@.microsoft.com...
>I have a feeling this might be a security problem so I posting the question
> in the security group as well. Sorry for the double post, I'll paste any
> answers over there as well.
> Here's the problem;
> I'm trying to do some prototyping with SQL 2005 Standard - Full Text
> Search
> in preparation for moving away from SQL 2000. I setup a FTS index and
> tried
> to create a job to rebuild the index nightly. This job build feature is
> built right into the
> FTS wizard. The job is created but it fails to create the steps and just
> says "Failed to connect to server...blah blah blah....Naped Pipes
> Provider,
> Error 40, Could not open connection"
> At first I thought it was something with FTS not configured right but then
> I
> just tried to create simple maintenance plan job and the same thing
> happened. It
> couldn't create the job step. The message from that was even more
> helpful.
> It said "Job failed" I'm doing all this from SSMS logged in with SA.
> Anyone have any idea why I can't create job steps on a newly installed SQL
> 2005 using SA?
> Thanks in advance
> --
> Maz
>|||Thanks Vikran
I have everything enabled except VIA. Don't know what that is so I left it
alone.
I think there's something wrong with this FTS product in SQL Server. I'm
logged into SQL as the system adminstrator (sa). I'm also logged onto
windows as a domain admin. It can't be security. it doesn't seem to be a
config problem. I'm stumped
--
Maz
"Vikram Vamshi" wrote:

> Some of the things to check for:
> - Make sure that the 'shared memory' prtocol is enabled on the server and
> has order=1
> - Make sure that sql server is configured to listen on the shared memory n
et
> lib
> You can check the settings using the SQL Server Configuration Manager.
> hth
> --
> Vikram Vamshi
> Database Engineer
> Eclipsys Corporation
> "Spicy Mikey" <Maz@.newsgroups.nospam> wrote in message
> news:A993F690-0AC3-4FA6-9760-85C2F24523C8@.microsoft.com...
>
>|||Did you ever get this resolved? I'm having the same problem. I'm using
the sa account and logged in as domain admin and yet I cannot create a
job step for any maintenance plan. We're running SQL 2005 Standard
with noe fancy bells or whistles. Even the "Wizard" craps out every
time. Can anyone offer any advice?
E
On Feb 5, 8:34 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
> Thanks Vikran
> I have everything enabled except VIA. Don't know what that is so I left i
t
> alone.
> I think there's something wrong with this FTS product inSQLServer. I'm
> logged intoSQLas the system adminstrator (sa). I'm also logged onto
> windows as a domain admin. It can't be security. it doesn't seem to be a
> config problem. I'm stumped
> --
> Maz
>
> "Vikram Vamshi" wrote:
>
>
>
>
>
>
> - Show quoted text -|||No, I never got it resolved. For the time being I've tabled the issue and
moved on to the rest of the project development. However, I will need an
answer in a few weeks.
Doesn anyone understand what has changed with permissions in SQL 2005 OR is
this a hard bug and no one (except a few of us) seem to care
Thanks anyone
--
Maz
"Elroyskimms" wrote:

> Did you ever get this resolved? I'm having the same problem. I'm using
> the sa account and logged in as domain admin and yet I cannot create a
> job step for any maintenance plan. We're running SQL 2005 Standard
> with noe fancy bells or whistles. Even the "Wizard" craps out every
> time. Can anyone offer any advice?
> E
>
> On Feb 5, 8:34 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
>
>|||SP2 was released a couple of weeks ago. I read a bug report where
someone mentioned an issue similar to this and the MS tech linked to
the SP2 download site. Of course, it is always MS's policy to say
"install the service pack" as a standard answer to all of your
questions (about as useful as using 42 as the answer). I will try and
run the install of SP2 over the weekend and see if that resolves the
issue. I'll report back here with the results.
-E
On Mar 5, 6:16 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
> No, I never got it resolved. For the time being I've tabled the issue and
> moved on to the rest of the project development. However, I will need an
> answer in a few weeks.
> Doesn anyone understand what has changed with permissions in SQL 2005 OR i
s
> this a hard bug and no one (except a few of us) seem to care
> Thanks anyone
> --
> Maz
>
> "Elroyskimms" wrote:
>
>
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -|||Theh machine I'm running this on is Windows 2003 Server. It has all the
latest security updates, sp's, etc. It's totally clean
Give it a shot but don't hold your breath until it works.
MICROSOFT TECHS MONITORING THIS BOARD: Any suggestions?
Maz
"Elroyskimms" wrote:

> SP2 was released a couple of weeks ago. I read a bug report where
> someone mentioned an issue similar to this and the MS tech linked to
> the SP2 download site. Of course, it is always MS's policy to say
> "install the service pack" as a standard answer to all of your
> questions (about as useful as using 42 as the answer). I will try and
> run the install of SP2 over the weekend and see if that resolves the
> issue. I'll report back here with the results.
> -E
> On Mar 5, 6:16 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
>
>

cannot create job steps in 2005

I have a feeling this might be a security problem so I posting the question
in the security group as well. Sorry for the double post, I'll paste any
answers over there as well.
Here's the problem;
I'm trying to do some prototyping with SQL 2005 Standard - Full Text Search
in preparation for moving away from SQL 2000. I setup a FTS index and tried
to create a job to rebuild the index nightly. This job build feature is
built right into the
FTS wizard. The job is created but it fails to create the steps and just
says "Failed to connect to server...blah blah blah....Naped Pipes Provider,
Error 40, Could not open connection"
At first I thought it was something with FTS not configured right but then I
just tried to create simple maintenance plan job and the same thing
happened. It
couldn't create the job step. The message from that was even more helpful.
It said "Job failed" I'm doing all this from SSMS logged in with SA.
Anyone have any idea why I can't create job steps on a newly installed SQL
2005 using SA?
Thanks in advance
Maz
Some of the things to check for:
- Make sure that the 'shared memory' prtocol is enabled on the server and
has order=1
- Make sure that sql server is configured to listen on the shared memory net
lib
You can check the settings using the SQL Server Configuration Manager.
hth
Vikram Vamshi
Database Engineer
Eclipsys Corporation
"Spicy Mikey" <Maz@.newsgroups.nospam> wrote in message
news:A993F690-0AC3-4FA6-9760-85C2F24523C8@.microsoft.com...
>I have a feeling this might be a security problem so I posting the question
> in the security group as well. Sorry for the double post, I'll paste any
> answers over there as well.
> Here's the problem;
> I'm trying to do some prototyping with SQL 2005 Standard - Full Text
> Search
> in preparation for moving away from SQL 2000. I setup a FTS index and
> tried
> to create a job to rebuild the index nightly. This job build feature is
> built right into the
> FTS wizard. The job is created but it fails to create the steps and just
> says "Failed to connect to server...blah blah blah....Naped Pipes
> Provider,
> Error 40, Could not open connection"
> At first I thought it was something with FTS not configured right but then
> I
> just tried to create simple maintenance plan job and the same thing
> happened. It
> couldn't create the job step. The message from that was even more
> helpful.
> It said "Job failed" I'm doing all this from SSMS logged in with SA.
> Anyone have any idea why I can't create job steps on a newly installed SQL
> 2005 using SA?
> Thanks in advance
> --
> Maz
>
|||Thanks Vikran
I have everything enabled except VIA. Don't know what that is so I left it
alone.
I think there's something wrong with this FTS product in SQL Server. I'm
logged into SQL as the system adminstrator (sa). I'm also logged onto
windows as a domain admin. It can't be security. it doesn't seem to be a
config problem. I'm stumped
Maz
"Vikram Vamshi" wrote:

> Some of the things to check for:
> - Make sure that the 'shared memory' prtocol is enabled on the server and
> has order=1
> - Make sure that sql server is configured to listen on the shared memory net
> lib
> You can check the settings using the SQL Server Configuration Manager.
> hth
> --
> Vikram Vamshi
> Database Engineer
> Eclipsys Corporation
> "Spicy Mikey" <Maz@.newsgroups.nospam> wrote in message
> news:A993F690-0AC3-4FA6-9760-85C2F24523C8@.microsoft.com...
>
>
|||Did you ever get this resolved? I'm having the same problem. I'm using
the sa account and logged in as domain admin and yet I cannot create a
job step for any maintenance plan. We're running SQL 2005 Standard
with noe fancy bells or whistles. Even the "Wizard" craps out every
time. Can anyone offer any advice?
E
On Feb 5, 8:34 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
> Thanks Vikran
> I have everything enabled except VIA. Don't know what that is so I left it
> alone.
> I think there's something wrong with this FTS product inSQLServer. I'm
> logged intoSQLas the system adminstrator (sa). I'm also logged onto
> windows as a domain admin. It can't be security. it doesn't seem to be a
> config problem. I'm stumped
> --
> Maz
>
> "Vikram Vamshi" wrote:
>
>
>
> - Show quoted text -
|||No, I never got it resolved. For the time being I've tabled the issue and
moved on to the rest of the project development. However, I will need an
answer in a few weeks.
Doesn anyone understand what has changed with permissions in SQL 2005 OR is
this a hard bug and no one (except a few of us) seem to care
Thanks anyone
Maz
"Elroyskimms" wrote:

> Did you ever get this resolved? I'm having the same problem. I'm using
> the sa account and logged in as domain admin and yet I cannot create a
> job step for any maintenance plan. We're running SQL 2005 Standard
> with noe fancy bells or whistles. Even the "Wizard" craps out every
> time. Can anyone offer any advice?
> E
>
> On Feb 5, 8:34 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
>
>
|||SP2 was released a couple of weeks ago. I read a bug report where
someone mentioned an issue similar to this and the MS tech linked to
the SP2 download site. Of course, it is always MS's policy to say
"install the service pack" as a standard answer to all of your
questions (about as useful as using 42 as the answer). I will try and
run the install of SP2 over the weekend and see if that resolves the
issue. I'll report back here with the results.
-E
On Mar 5, 6:16 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
> No, I never got it resolved. For the time being I've tabled the issue and
> moved on to the rest of the project development. However, I will need an
> answer in a few weeks.
> Doesn anyone understand what has changed with permissions in SQL 2005 OR is
> this a hard bug and no one (except a few of us) seem to care
> Thanks anyone
> --
> Maz
>
> "Elroyskimms" wrote:
>
>
>
>
>
>
> - Show quoted text -
|||Theh machine I'm running this on is Windows 2003 Server. It has all the
latest security updates, sp's, etc. It's totally clean
Give it a shot but don't hold your breath until it works.
MICROSOFT TECHS MONITORING THIS BOARD: Any suggestions?
Maz
"Elroyskimms" wrote:

> SP2 was released a couple of weeks ago. I read a bug report where
> someone mentioned an issue similar to this and the MS tech linked to
> the SP2 download site. Of course, it is always MS's policy to say
> "install the service pack" as a standard answer to all of your
> questions (about as useful as using 42 as the answer). I will try and
> run the install of SP2 over the weekend and see if that resolves the
> issue. I'll report back here with the results.
> -E
> On Mar 5, 6:16 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
>
>