can't deploy, SSRS 2K5

Hi kids:
I'm sure this is an easy one, sorry for posting a knob question...
Whenever I attempt to deploy a report, I get prompted for a login. I
don't remember setting SSRS to run as anyting except Local System, and
the configuration tool bears that out. When I click "deploy" on my
(very simple) report, it prompts me for a username & password. If I
click cancel, it declares the deployment a failure and stops. I have
tried entering my domain\user & password, user & password, sa &
password, but all fail.
Suggestions?
Thanks;
DuncanIs RS on your machine or a different one? It doesn't matter what RS uses to
run, it implements security and you have to have the correct rights to
deploy.
First, even without a report deployed you need to be able to see Report
Manager (the portal that ships with RS). Does that work for you?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Duncan A. McRae" <google.com@.mcrae.ca> wrote in message
news:1187288669.801335.68890@.q3g2000prf.googlegroups.com...
> Hi kids:
> I'm sure this is an easy one, sorry for posting a knob question...
> Whenever I attempt to deploy a report, I get prompted for a login. I
> don't remember setting SSRS to run as anyting except Local System, and
> the configuration tool bears that out. When I click "deploy" on my
> (very simple) report, it prompts me for a username & password. If I
> click cancel, it declares the deployment a failure and stops. I have
> tried entering my domain\user & password, user & password, sa &
> password, but all fail.
> Suggestions?
> Thanks;
> Duncan
>

Can't delete job

When attempt to delete a job, the following error is
encountered:
Cannot add, update, or delete a job (or its steps or
schedules) that originated from an MSX server.
How would you reslove this?
Thanks,
BenDo you have master-target server configuration setup? If not, did you
recently rename your SQL Server?
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Ben" <bluebells88@.yahoo.com> wrote in message
news:379601c3fdd4$05d89540$a001280a@.phx.gbl...
When attempt to delete a job, the following error is
encountered:
Cannot add, update, or delete a job (or its steps or
schedules) that originated from an MSX server.
How would you reslove this?
Thanks,
Ben|||Sorry, what is 'master-target server configuration
setup'?
The machine joined a domain group after the job is
created.
Thanks,
Ben
>--Original Message--
>Do you have master-target server configuration setup? If
not, did you
>recently rename your SQL Server?
>--
>HTH,
>Vyas, MVP (SQL Server)
>http://vyaskn.tripod.com/
>Is .NET important for a database professional?
>http://vyaskn.tripod.com/poll.htm
>
>"Ben" <bluebells88@.yahoo.com> wrote in message
>news:379601c3fdd4$05d89540$a001280a@.phx.gbl...
>When attempt to delete a job, the following error is
>encountered:
>Cannot add, update, or delete a job (or its steps or
>schedules) that originated from an MSX server.
>How would you reslove this?
>Thanks,
>Ben
>
>.
>|||You probably have incorrect machine name in msdb..sysjobs. The old machine
name is still in msdb..sysjobs. Since you changed the machine name, SQLAgent
now thinks that this job is owned by a master server. You can change
the machine names for all jobs with below SQL Statement. Warning: Hacking
system tables is not supported and should be done with care (below should be
rather safe, though).
DECLARE @.srv sysname
SET @.srv = CAST(SERVERPROPERTY('ServerName') AS sysname)
UPDATE sysjobs SET originating_server = @.srv
NOTE:
If this is a target server (you have jobs sent from a master server), you
have to exclude them, so you don't transfer those jobs into local jobs:
WHERE originating_server = 'oldservname'
If you want to do this the supported way, see below KB article
http://support.microsoft.com/default.aspx?scid=kb;en-us;281642
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Ben" <bluebells88@.yahoo.com> wrote in message
news:44ba01c3fe7b$b69c3970$a101280a@.phx.gbl...
> Sorry, what is 'master-target server configuration
> setup'?
> The machine joined a domain group after the job is
> created.
> Thanks,
> Ben
> >--Original Message--
> >Do you have master-target server configuration setup? If
> not, did you
> >recently rename your SQL Server?
> >--
> >HTH,
> >Vyas, MVP (SQL Server)
> >http://vyaskn.tripod.com/
> >Is .NET important for a database professional?
> >http://vyaskn.tripod.com/poll.htm
> >
> >
> >"Ben" <bluebells88@.yahoo.com> wrote in message
> >news:379601c3fdd4$05d89540$a001280a@.phx.gbl...
> >When attempt to delete a job, the following error is
> >encountered:
> >
> >Cannot add, update, or delete a job (or its steps or
> >schedules) that originated from an MSX server.
> >
> >How would you reslove this?
> >
> >Thanks,
> >Ben
> >
> >
> >.
> >|||Thanks all for the helps.
Ben
>--Original Message--
>You probably have incorrect machine name in
msdb..sysjobs. The old machine
>name is still in msdb..sysjobs. Since you changed the
machine name, SQLAgent
>now thinks that this job is owned by a master server.
You can change
>the machine names for all jobs with below SQL Statement.
Warning: Hacking
>system tables is not supported and should be done with
care (below should be
>rather safe, though).
>DECLARE @.srv sysname
>SET @.srv = CAST(SERVERPROPERTY('ServerName') AS sysname)
>UPDATE sysjobs SET originating_server = @.srv
>
>NOTE:
>If this is a target server (you have jobs sent from a
master server), you
>have to exclude them, so you don't transfer those jobs
into local jobs:
>WHERE originating_server = 'oldservname'
>
>If you want to do this the supported way, see below KB
article
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;281642
>
>--
>Tibor Karaszi, SQL Server MVP
>Archive at:
>http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Ben" <bluebells88@.yahoo.com> wrote in message
>news:44ba01c3fe7b$b69c3970$a101280a@.phx.gbl...
>> Sorry, what is 'master-target server configuration
>> setup'?
>> The machine joined a domain group after the job is
>> created.
>> Thanks,
>> Ben
>> >--Original Message--
>> >Do you have master-target server configuration setup?
If
>> not, did you
>> >recently rename your SQL Server?
>> >--
>> >HTH,
>> >Vyas, MVP (SQL Server)
>> >http://vyaskn.tripod.com/
>> >Is .NET important for a database professional?
>> >http://vyaskn.tripod.com/poll.htm
>> >
>> >
>> >"Ben" <bluebells88@.yahoo.com> wrote in message
>> >news:379601c3fdd4$05d89540$a001280a@.phx.gbl...
>> >When attempt to delete a job, the following error is
>> >encountered:
>> >
>> >Cannot add, update, or delete a job (or its steps or
>> >schedules) that originated from an MSX server.
>> >
>> >How would you reslove this?
>> >
>> >Thanks,
>> >Ben
>> >
>> >
>> >.
>> >
>
>.
>

Can't delete job

When attempt to delete a job, the following error is
encountered:
Cannot add, update, or delete a job (or its steps or
schedules) that originated from an MSX server.
How would you reslove this?
Thanks,
BenDo you have master-target server configuration setup? If not, did you
recently rename your SQL Server?
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Ben" <bluebells88@.yahoo.com> wrote in message
news:379601c3fdd4$05d89540$a001280a@.phx.gbl...
When attempt to delete a job, the following error is
encountered:
Cannot add, update, or delete a job (or its steps or
schedules) that originated from an MSX server.
How would you reslove this?
Thanks,
Ben|||Sorry, what is 'master-target server configuration
setup'?
The machine joined a domain group after the job is
created.
Thanks,
Ben

>--Original Message--
>Do you have master-target server configuration setup? If
not, did you
>recently rename your SQL Server?
>--
>HTH,
>Vyas, MVP (SQL Server)
>http://vyaskn.tripod.com/
>Is .NET important for a database professional?
>http://vyaskn.tripod.com/poll.htm
>
>"Ben" <bluebells88@.yahoo.com> wrote in message
>news:379601c3fdd4$05d89540$a001280a@.phx.gbl...
>When attempt to delete a job, the following error is
>encountered:
>Cannot add, update, or delete a job (or its steps or
>schedules) that originated from an MSX server.
>How would you reslove this?
>Thanks,
>Ben
>
>.
>|||You probably have incorrect machine name in msdb..sysjobs. The old machine
name is still in msdb..sysjobs. Since you changed the machine name, SQLAgent
now thinks that this job is owned by a master server. You can change
the machine names for all jobs with below SQL Statement. Warning: Hacking
system tables is not supported and should be done with care (below should be
rather safe, though).
DECLARE @.srv sysname
SET @.srv = CAST(SERVERPROPERTY('ServerName') AS sysname)
UPDATE sysjobs SET originating_server = @.srv
NOTE:
If this is a target server (you have jobs sent from a master server), you
have to exclude them, so you don't transfer those jobs into local jobs:
WHERE originating_server = 'oldservname'
If you want to do this the supported way, see below KB article
http://support.microsoft.com/defaul...kb;en-us;281642
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Ben" <bluebells88@.yahoo.com> wrote in message
news:44ba01c3fe7b$b69c3970$a101280a@.phx.gbl...
> Sorry, what is 'master-target server configuration
> setup'?
> The machine joined a domain group after the job is
> created.
> Thanks,
> Ben
>
> not, did you|||tibor,
I am trying your tip and obviously doing something wrong.
original server name was foxapp
new server name is foxsql
this is what I type but get originating_server not a valid column name?
DECLARE @.srv sysname
SET @.srv = CAST(SERVERPROPERTY('foxsql') AS sysname)
UPDATE sysjobs SET originating_server = @.srv
WHERE orginating_server = 'foxapp'
could you pls tell me what I did wrong thanks
mitch|||You shouldn't replace 'ServerName' inside the function call.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"mitch" <anonymous@.discussions.microsoft.com> wrote in message
news:DE663F9F-66CD-407B-97D9-0B51860DDB1E@.microsoft.com...
> tibor,
> I am trying your tip and obviously doing something wrong.
> original server name was foxapp
> new server name is foxsql
> this is what I type but get originating_server not a valid column name?
> DECLARE @.srv sysname
> SET @.srv = CAST(SERVERPROPERTY('foxsql') AS sysname)
> UPDATE sysjobs SET originating_server = @.srv
> WHERE orginating_server = 'foxapp'
> could you pls tell me what I did wrong thanks
> mitch|||Tibor,
thank you very much!
excellent fix!
mitch