Hi, I'm new to Reporting Services. However, I am sa on the reporting
services database server and also admin rights on the server. I deployed my
report to the reporting services server without errors, however someone else
(not sa equivalent on the database, and not admin equivalent) cannot deploy
because they get permission errors.
Any ideas? Thanks in advance.Read up on roles. Security works in RS via assigning user or groups to
roles. By default the administrators group of the server is in a role which
is why everything works for you. What I do is create local groups and to
that group I add domain users/groups. Then I assign that local group to a
role (this is done in Report Manager).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"RichieRich" <RichieRich@.discussions.microsoft.com> wrote in message
news:221820BB-1DF3-4C08-8E73-2F0B6F4DC2A2@.microsoft.com...
> Hi, I'm new to Reporting Services. However, I am sa on the reporting
> services database server and also admin rights on the server. I deployed
> my
> report to the reporting services server without errors, however someone
> else
> (not sa equivalent on the database, and not admin equivalent) cannot
> deploy
> because they get permission errors.
> Any ideas? Thanks in advance.|||Thanks. I'll try it. I completed the MS Course 2030A Creating Reporting
Solutions, but can you recommend any other courses?
Thanks.
"Bruce L-C [MVP]" wrote:
> Read up on roles. Security works in RS via assigning user or groups to
> roles. By default the administrators group of the server is in a role which
> is why everything works for you. What I do is create local groups and to
> that group I add domain users/groups. Then I assign that local group to a
> role (this is done in Report Manager).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "RichieRich" <RichieRich@.discussions.microsoft.com> wrote in message
> news:221820BB-1DF3-4C08-8E73-2F0B6F4DC2A2@.microsoft.com...
> > Hi, I'm new to Reporting Services. However, I am sa on the reporting
> > services database server and also admin rights on the server. I deployed
> > my
> > report to the reporting services server without errors, however someone
> > else
> > (not sa equivalent on the database, and not admin equivalent) cannot
> > deploy
> > because they get permission errors.
> >
> > Any ideas? Thanks in advance.
>
>|||Sorry. Not familiar with the course. I would recommend buying some books.
There are several good ones. Two I have are Hitchhiker's Guide to SQL Server
2000 Reporting Services and Microsoft Reporting Services In Action.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"RichieRich" <RichieRich@.discussions.microsoft.com> wrote in message
news:058E276C-0DE6-4667-8D98-8B1226CA224D@.microsoft.com...
> Thanks. I'll try it. I completed the MS Course 2030A Creating Reporting
> Solutions, but can you recommend any other courses?
> Thanks.
> "Bruce L-C [MVP]" wrote:
>> Read up on roles. Security works in RS via assigning user or groups to
>> roles. By default the administrators group of the server is in a role
>> which
>> is why everything works for you. What I do is create local groups and to
>> that group I add domain users/groups. Then I assign that local group to a
>> role (this is done in Report Manager).
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "RichieRich" <RichieRich@.discussions.microsoft.com> wrote in message
>> news:221820BB-1DF3-4C08-8E73-2F0B6F4DC2A2@.microsoft.com...
>> > Hi, I'm new to Reporting Services. However, I am sa on the reporting
>> > services database server and also admin rights on the server. I
>> > deployed
>> > my
>> > report to the reporting services server without errors, however someone
>> > else
>> > (not sa equivalent on the database, and not admin equivalent) cannot
>> > deploy
>> > because they get permission errors.
>> >
>> > Any ideas? Thanks in advance.
>>
Showing posts with label errors. Show all posts
Showing posts with label errors. Show all posts
Wednesday, March 21, 2012
Friday, March 9, 2012
Deploying MSSQL 2005 Express DB to MSSQL 2005 WKGP Errors
DB is developed on local computer with MSSQL 2005 Express. My host is on MSSQL 2005 workgroup. Are they compatible, because I am getting errors? Is my approach wrong?
I have tried several approaches.
A) I created a backup of database on my local, then placed a copy on the server. Then I tried to restore through Server Management Studio. I get this error.
TITLE: Microsoft SQL Server Management Studio
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
ADDITIONAL INFORMATION:
The backed-up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database.
RESTORE FILELIST is terminating abnormally. (Microsoft SQL Server, Error: 3169)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=3169&LinkId=20476
BUTTONS:
OK
B: I also have tried copying the database. I put it in the same path as the other databases that can be read with server management studio on the server. Then, tried to get to it through server managements studio and it did not appear. So I tried to attach it. Then I received this error:
TITLE: Microsoft SQL Server Management Studio
Attach database failed for Server 'MROACH1'. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Could not find row in sysindexes for database ID 10, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.
Could not open new database 'LodgingDB'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 602)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=602&LinkId=20476
BUTTONS:
OK
C: I have also tried opening the Database, and back up file through Server Management Studio. without success.
D: I also tried Windows and Software update at microsoft update, but no updates were recommended for Version on Server.
I'm surprised this is so hard. My original data base was created in same family of software. 2005 MS SQL Express. I could use some direct help from someone experienced with this. Am I doing it wrong or are the DB versions incompatible.
Mark Roach
Hi Mark,
The first error you mention would indicate that your hosting company is using SQL 2000 not SQL 2005. Database files are not backward compatible. You should verify with your host what version of SQL Server they have, or if they have both 2000 and 2005, that they are pointing you to a 2005 server.
Mike
|||Thanks Mike,
The host machine is on MSSQL 2005 WorkGroup.
|||Actually, you may be incorrect about what is running on the hosting system.
The error message from the restore:
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=3169&LinkId=20476
indicates (ProdVer=08.00.2039) that it is running SQL 2000, not SQL 2005. Also, the error message talking about versions of databases indicates the same.
All SKUs/editions of SQL databases of the same version are compatible. There are no diffences in database format between Express and Workgroup as long as both are the same version.
|||Hi there,
I got the same error when I tried to restore the SQL 2005 DB to SQL 2005 DB.
Were you able to figure this one out? If so, could you please let me know?
Thanks in advance,
SG.
Deploying MSSQL 2005 Express DB to MSSQL 2005 WKGP Errors
DB is developed on local computer with MSSQL 2005 Express. My host is on MSSQL 2005 workgroup. Are they compatible, because I am getting errors? Is my approach wrong?
I have tried several approaches.
A) I created a backup of database on my local, then placed a copy on the server. Then I tried to restore through Server Management Studio. I get this error.
TITLE: Microsoft SQL Server Management Studio
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
ADDITIONAL INFORMATION:
The backed-up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database.
RESTORE FILELIST is terminating abnormally. (Microsoft SQL Server, Error: 3169)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=3169&LinkId=20476
BUTTONS:
OK
B: I also have tried copying the database. I put it in the same path as the other databases that can be read with server management studio on the server. Then, tried to get to it through server managements studio and it did not appear. So I tried to attach it. Then I received this error:
TITLE: Microsoft SQL Server Management Studio
Attach database failed for Server 'MROACH1'. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Could not find row in sysindexes for database ID 10, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.
Could not open new database 'LodgingDB'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 602)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=602&LinkId=20476
BUTTONS:
OK
C: I have also tried opening the Database, and back up file through Server Management Studio. without success.
D: I also tried Windows and Software update at microsoft update, but no updates were recommended for Version on Server.
I'm surprised this is so hard. My original data base was created in same family of software. 2005 MS SQL Express. I could use some direct help from someone experienced with this. Am I doing it wrong or are the DB versions incompatible.
Mark Roach
Hi Mark,
The first error you mention would indicate that your hosting company is using SQL 2000 not SQL 2005. Database files are not backward compatible. You should verify with your host what version of SQL Server they have, or if they have both 2000 and 2005, that they are pointing you to a 2005 server.
Mike
|||Thanks Mike,
The host machine is on MSSQL 2005 WorkGroup.
|||Actually, you may be incorrect about what is running on the hosting system.
The error message from the restore:
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=3169&LinkId=20476
indicates (ProdVer=08.00.2039) that it is running SQL 2000, not SQL 2005. Also, the error message talking about versions of databases indicates the same.
All SKUs/editions of SQL databases of the same version are compatible. There are no diffences in database format between Express and Workgroup as long as both are the same version.
|||Hi there,
I got the same error when I tried to restore the SQL 2005 DB to SQL 2005 DB.
Were you able to figure this one out? If so, could you please let me know?
Thanks in advance,
SG.
Wednesday, March 7, 2012
Deploying a website with user authentication - getting errors
I have built a site that uses form-based authentication. Am I correct in assuming that the users and passwords will be stored in the SQLServer database in the aspnetdb.mdf file? The website works great and the authentication works how I want it to. However, I've tried to copy over the file onto a remote machine. The first page is a login screen and this is displayed without any problems but as soon as I attempt to log in I get an error message of:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
I'm wondering if this is something to do with the fact I installed SQLServer Express edition on the remote machine. The website works no problem on the local machine in debug mode of Visual Studio 2005 (Professional Edition). I followed instructions to enable remote connections on SQLServer Express from a Microsoft support doc. If anybody can point me in the right direction I'll be very grateful as I've hit a wall here.
Did you check the connection string in web.config if it is pointing to the right server. Also, if you are using aspnetdb.mdf, you should have at least SQL Server Express edition installed on the machine hosting the website.
|||
Hi. Thanks for replying. The only connection string I have in my webconfig file is for an Oracle database that I access elsewhere in the website. Since the original website works in the debug mode of Vis Studio 2005 without any other connection string then I just copied the webconfig file over to the remote server as it was. Does that mean I have to add a connection string to the aspnetdb.mdf file? (The server has SQLServer Express installed on it.)
Have a look at this and try adding a connectionstring to the server.
https://help.maximumasp.com/SmarterTicket/Customer/KBArticle.aspx?articleid=878
You might have to attach the local mdf file using this in the connection string.
AttachDBFilename=|DataDirectory|aspnet.mdfconnectionStrings> <remove name="LocalSqlServer" /> <add name="LocalSqlServer" connectionString="data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true" providerName="System.Data.SqlClient"/></connectionStrings>
Saturday, February 25, 2012
Deployed reports have javascript errors?
Hello-
I have developed a number of reports on Win XP with VS2005. They run on our development server, which is running Windows Server 2003 32-bit. I then deploy these reports on our production server, which is running Windows Server 2003 64-bit edition.
Accessing any of the reports from Report Manager results in javascript errors, such as 'Line 41 Error: 'RSClientController' is undefined'
I get these errors also when invoking these reports through a form post.
It appears that some javascript code generated by the report server is missing. Could this be a 32-bit vs 64-bit issue? Report Manager seems to work fine; it is only when I run a report that I have this problem. This is the first time I've tried to deploy reports to this server.
Thanks.Solution!
The problem is the .axd file extention which is generated by the sql server on the fly when one tries to run a report.
There is an IIS setting that needs to be changed. Open IIS and go to the properties of the Reports website. Under the directory tab, click on the Configuration button. Find the .axd extension in the Mappings tab and double-click to get to its properties. Uncheck the 'Check that file exists' option, save, and that is it.
This is a known issue and MS hasn't yet written a KB article for it.|||Excellent analysis. This solved my problem with reports and the WebResource.axd file.|||
What if I'm having the same "'RSClientController' is undefined" issue, but when I go to the .axd extension properties, "verify that file exists" is already unchecked?
This is on a clean install of SQL 2k5 on Server 2k3 SP1.
Thanks.
|||On IIS v 6.0, on the Virtual Directory tab of the ReportServer, I chose configuration, then on the mappings tab I needed to edit the Wildcard application to uncheck the box to "verify file exists"
Thanks again;)
|||Anyone found a solution for this ?|||If you website is using forms authentication, you have to grant access to authenticated users to Reserved.ReportViewerWebControl.axd.
After I added the following location entry in my web.config file I no longer received "RSClient Controller is not defined messages".
<location path="Reserved.ReportViewerWebControl.axd">
<system.web>
<authorization>
<allow roles="RoleA, RoleB">
</allow>
</authorization>
</system.web>
</location>
Deployed reports have javascript errors?
Hello-
I have developed a number of reports on Win XP with VS2005. They run on our development server, which is running Windows Server 2003 32-bit. I then deploy these reports on our production server, which is running Windows Server 2003 64-bit edition.
Accessing any of the reports from Report Manager results in javascript errors, such as 'Line 41 Error: 'RSClientController' is undefined'
I get these errors also when invoking these reports through a form post.
It appears that some javascript code generated by the report server is missing. Could this be a 32-bit vs 64-bit issue? Report Manager seems to work fine; it is only when I run a report that I have this problem. This is the first time I've tried to deploy reports to this server.
Thanks.
Solution!
The problem is the .axd file extention which is generated by the sql server on the fly when one tries to run a report.
There is an IIS setting that needs to be changed. Open IIS and go to the properties of the Reports website. Under the directory tab, click on the Configuration button. Find the .axd extension in the Mappings tab and double-click to get to its properties. Uncheck the 'Check that file exists' option, save, and that is it.
This is a known issue and MS hasn't yet written a KB article for it.
|||Excellent analysis. This solved my problem with reports and the WebResource.axd file.|||
What if I'm having the same "'RSClientController' is undefined" issue, but when I go to the .axd extension properties, "verify that file exists" is already unchecked?
This is on a clean install of SQL 2k5 on Server 2k3 SP1.
Thanks.
|||On IIS v 6.0, on the Virtual Directory tab of the ReportServer, I chose configuration, then on the mappings tab I needed to edit the Wildcard application to uncheck the box to "verify file exists"
Thanks again;)
|||Anyone found a solution for this ?|||If you website is using forms authentication, you have to grant access to authenticated users to Reserved.ReportViewerWebControl.axd.
After I added the following location entry in my web.config file I no longer received "RSClient Controller is not defined messages".
<location path="Reserved.ReportViewerWebControl.axd">
<system.web>
<authorization>
<allow roles="RoleA, RoleB">
</allow>
</authorization>
</system.web>
</location>
Deployed reports have javascript errors?
Hello-
I have developed a number of reports on Win XP with VS2005. They run on our development server, which is running Windows Server 2003 32-bit. I then deploy these reports on our production server, which is running Windows Server 2003 64-bit edition.
Accessing any of the reports from Report Manager results in javascript errors, such as 'Line 41 Error: 'RSClientController' is undefined'
I get these errors also when invoking these reports through a form post.
It appears that some javascript code generated by the report server is missing. Could this be a 32-bit vs 64-bit issue? Report Manager seems to work fine; it is only when I run a report that I have this problem. This is the first time I've tried to deploy reports to this server.
Thanks.
Solution!
The problem is the .axd file extention which is generated by the sql server on the fly when one tries to run a report.
There is an IIS setting that needs to be changed. Open IIS and go to the properties of the Reports website. Under the directory tab, click on the Configuration button. Find the .axd extension in the Mappings tab and double-click to get to its properties. Uncheck the 'Check that file exists' option, save, and that is it.
This is a known issue and MS hasn't yet written a KB article for it.
|||Excellent analysis. This solved my problem with reports and the WebResource.axd file.|||
What if I'm having the same "'RSClientController' is undefined" issue, but when I go to the .axd extension properties, "verify that file exists" is already unchecked?
This is on a clean install of SQL 2k5 on Server 2k3 SP1.
Thanks.
|||On IIS v 6.0, on the Virtual Directory tab of the ReportServer, I chose configuration, then on the mappings tab I needed to edit the Wildcard application to uncheck the box to "verify file exists"
Thanks again;)
|||Anyone found a solution for this ?|||If you website is using forms authentication, you have to grant access to authenticated users to Reserved.ReportViewerWebControl.axd.
After I added the following location entry in my web.config file I no longer received "RSClient Controller is not defined messages".
<location path="Reserved.ReportViewerWebControl.axd">
<system.web>
<authorization>
<allow roles="RoleA, RoleB">
</allow>
</authorization>
</system.web>
</location>
Deployed reports have javascript errors?
Hello-
I have developed a number of reports on Win XP with VS2005. They run on our development server, which is running Windows Server 2003 32-bit. I then deploy these reports on our production server, which is running Windows Server 2003 64-bit edition.
Accessing any of the reports from Report Manager results in javascript errors, such as 'Line 41 Error: 'RSClientController' is undefined'
I get these errors also when invoking these reports through a form post.
It appears that some javascript code generated by the report server is missing. Could this be a 32-bit vs 64-bit issue? Report Manager seems to work fine; it is only when I run a report that I have this problem. This is the first time I've tried to deploy reports to this server.
Thanks.Solution!
The problem is the .axd file extention which is generated by the sql server on the fly when one tries to run a report.
There is an IIS setting that needs to be changed. Open IIS and go to the properties of the Reports website. Under the directory tab, click on the Configuration button. Find the .axd extension in the Mappings tab and double-click to get to its properties. Uncheck the 'Check that file exists' option, save, and that is it.
This is a known issue and MS hasn't yet written a KB article for it.|||Excellent analysis. This solved my problem with reports and the WebResource.axd file.|||
What if I'm having the same "'RSClientController' is undefined" issue, but when I go to the .axd extension properties, "verify that file exists" is already unchecked?
This is on a clean install of SQL 2k5 on Server 2k3 SP1.
Thanks.
|||On IIS v 6.0, on the Virtual Directory tab of the ReportServer, I chose configuration, then on the mappings tab I needed to edit the Wildcard application to uncheck the box to "verify file exists"
Thanks again;)
|||Anyone found a solution for this ?|||If you website is using forms authentication, you have to grant access to authenticated users to Reserved.ReportViewerWebControl.axd.
After I added the following location entry in my web.config file I no longer received "RSClient Controller is not defined messages".
<location path="Reserved.ReportViewerWebControl.axd">
<system.web>
<authorization>
<allow roles="RoleA, RoleB">
</allow>
</authorization>
</system.web>
</location>
Subscribe to:
Posts (Atom)