Cannot edit RS reports...!

You need the Manage reports task. You can get this on a default report server installation by having the Content Manager role.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
--Original Message--
From: Kerc
Posted At: Wednesday, October 05, 2005 10:32 AM
Posted To: microsoft.public.sqlserver.reportingsvcs
Conversation: Cannot edit RS reports...!!!
Subject: Cannot edit RS reports...!!!
I'm new at using RS, so please bear with me...
I need to make small changes to existing reports. I'm able to execute
the reports and view the report list through the Report Manager, but I
don't ge the "Edit" options for the reports.
What security options must I have to be able to edit the reports?
Also, are the RDLs stored in the Catalog table? I ask because I can't
find an RDL on the report server to save my life...
Thanks!I just verified and I do have the "Content Manager" role. So far my
experience with RS has been pretty frustrating...

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:
>
>

Cannot create a connection to data source !!!

Hello everyone,

I posted the same issue before, but I couldn't find the solution yet. I am posting this agian cos I tried almost everything and I am not able to solve the issue.

Let me explain what is happening here:

Server A - is my development local machine

Server B - is the remote reporting server, where all reports are deployed

Server C - is where the databases are located

- After successfully deploying the project (the reports and datasources) on the remote server and try to run the report , I am getting the following error message

An error has occurred during report processing. (rsProcessingAborted)

Cannot create a connection to data source 'dsCallB'. (rsErrorOpeningConnection)

For more information about this error navigate to the report server on the local server machine, or enable remote errors

- I tried to deploy and run the same report on my local machine report server(Server A), which is still accessing the same database from Server C. This works fine.

So from this we can understand that A ==> B ==> C is not working, however A ==>C works fine(using Server A as a report server).

I almost tried all the possible solutions that are posted on the forum, such as storing the credential information on the report server (server B), created a data source, which is not a shared data source, on the report server level e.t.c. and I ended up with nuthin.

The weired thing is that there are existing reports that are already created and deployed(by somebody else) in the report server (server B) , which access the database on Server C. These existing reports run with no problem, even I can create a report which uses the existing data source and runs perfectly. However, when I create a new report which uses a different data source (from Server C), and deploy it to Server B and tried to run it, the above error message comes.

Please let me know if you have any idea.

Thx.

What type of data source is it, and how are you connecting? OLEDB, ODBC? Are you using Windows Authentication for the data source?|||If you are using windows integrated security this could be the "double hop issue". Try to connect to Server B via remote desktop and start the report. If it works you have to mark the server b as "trusted for delegation" in your active directory. I am actually not sure if this is enough, but you can also google this problem. there are also some KB entries (at least for ASP .NET) concerning this problem.|||

Actually, the data source is Microsoft SQL Server type. And for the authentication I stored the login and password securely on the report server.

|||Are you using SQL Server or Windows authentication?|||

I have the same problem, when trying to change the datasource on reports deployed from Visual Studio. It seems that if you change the data source before deploying, then that is okay and the connection works. Changing the data source within Reporting Services is where I get the trouble.

I develop the reports on a development server against a test database on the same server. Then I change the datasource in visual studio to a staging data source, and deploy the reports. I go to the reporting services server and run the reports, and they are fine. At this point the reports have my blessing to become the "live" reports, so all I need to do is change the data source on them to the live production database server. But doing that only makes the reports fail. If I go back to the development server and change the data source there and redeploy, the reports work.

This is only a problem for me when I am trying to change to a firewall protected data source which is not accessable from the development machine. I'm really interested if anyone has a solution for this, as its not correct for me to go and change the firewall settings simply to get reporting services to operate the way I know it is meant to work. It almost feels as if somehow the reports KNOW that they were deployed with a different data source, and are balking at letting me change that. Why? <frust>

|||

Duh, in my post above I couldnt see why changing the data source on the report after deployment didnt work... not too surprising as the mapping between the server name and the IP address (the hosts file) was not set up on the reporting services server the same way it was set up on the server from which I was doing the deployment. Need I say it... duh

Never mind!

Pjos