Deserialization failed: The type initializer for 'Microsoft.ReportDesigner.Drawing.RptStyle

I have VS2003 and VS2005 installed as well as SQL Server 2000 and SQL Server 2005 Tools. I have RS2000 and RS2005 installed. RS2000 works fine in VS2003. When using VS2005 and opening a Microsoft sample project for 2005, I get the error listed in the subject line.

When trying to create a new project and connecting to an Oracle database or a SQL Server 2005 database, I get the following error: "A connection cannot be made to the database. Set and check the connection string." The connection works fine when the test button is clicked, but fails when continuing in the wizard.

Any suggestions. We are trying to migrate from RS2000 to RS2005 and nothing in 2005 works.

We're gettiing the same error on 8 machines at our company. We opened a ticket with MS and they closed it tell us to reinstall XP on the PCs. None have agreed to let us do this without knowing if it will work. If anyone has a clue why this is happening we'd really like to know.|||

Try the cure-all for every software problem. Reformat and reinstall.

|||Try modifying the HKEY_CURRENT_USER\Control Panel\International\sPositiveSign registry key so that its value is nothing. If it appears as though the value is already empty, edit the data string to some arbitrary viewable character, save it, open it up again and remove the value.sql

Deployment problem to production server

I just started using reporting services and have a set of reports done that works on VS2005, however I am struggling with how to deploy this to a production server. The production server does not have a public presnet on the web. If I copy the directory to the production machine it does not work. I realzie that somehow I need to update the report database on the production machine but am lost about how to do that if I cannot connect to the machine from VS2005. I also tried the upload function in report manager.

How do I get my reports onto this box? Surely there is a way to do this without having to have a connection from VS2005. If you do applications that you want to ship to remote users there must be a way to do this.

Thanks

Chuck

In an effort to see how this works I took the reports database from my devleopment machine and installed it onto the server using SQL backup / restore. Does this break the reports database? Do I have to uninstall the reporting services using the SQL install tool or is there a way to recreate the database without doing the SQL uninstall reinstall?

Thanks

Chuck

deploying reports from vs2005 issue

I'm trying to deploy reports to development server that is running
mssql 2000 and a named instance of mssql 2005 but when I deploy I'm
running into authentication issues. From some articles I'm finding
that this can occur when using SSRS in mssql2000. Do I need to modify
the deployment path in visual studio to some how point to the named
mssql 2005 database, if so how? Also where do I find the
configuration in vs2005 to not overwrite the datasources when a report
is deployed?
Thanks,
JeffWhen you setup for deployment you give it the web address. If your report
server is working that is all you should need to do. For instance it would
look like this for TargetServerURL: http://yourserver/ReportServer
Now, to be able to deploy you need to have the rights to do so. This is
Reporting Services rights. It has nothing to do with SQL Server DB rights.
Can you run reports? First make sure of that.
If your domain account is in the local administrators group on the server
then you will automatically have all the rights you need. Again, this is
around your windows account, not your SQL Server access rights.
Also, the default in vs2005 is to NOT overwrite a datasource. Right mouse
click on the project, properties. This is where you set the targetserverurl
and also the overwritedatasources (which you want to be false).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Jeffa" <Jeff.Arlt@.gmail.com> wrote in message
news:1183479523.437839.111440@.j4g2000prf.googlegroups.com...
> I'm trying to deploy reports to development server that is running
> mssql 2000 and a named instance of mssql 2005 but when I deploy I'm
> running into authentication issues. From some articles I'm finding
> that this can occur when using SSRS in mssql2000. Do I need to modify
> the deployment path in visual studio to some how point to the named
> mssql 2005 database, if so how? Also where do I find the
> configuration in vs2005 to not overwrite the datasources when a report
> is deployed?
> Thanks,
> Jeff
>

Deploying database with application

i written an application in vs2005 using vb; it connects to a database on the server.

how do i publish/distribute this application with the database? so that when the client installs the application it will also create the whole database on its machine... or have it create the database on a server asking the client to specify the server path, name... etc

i am sure there is a simple way ot do this but i am new ot this and have never done this before..

appreciate all the help... thanks

You can take help of unattended installation, refer http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=636755&SiteID=1 too.|||

Here is an excellent resource detailing unattended installations of SQL Server along with applications.

SQL Server 2005 UnAttended Installations
http://www.devx.com/dbzone/Article/31648

deploying App to 2003 server with SQL2005

I devloped this app with vs2005 and SQL 2005 express, everything seems to work fine, when I deploied the app to my web server I got a few different error messages that I worked through but now stuck on this one. i am sure it is something with SQL 2005 server. is there anywhere that has a good check list for doing things right in asp and SQL deployment?

here is the error message i am getting from debugging.

The SELECT permission was denied on the object 'Categories', database 'Blog', schema 'dbo'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: The SELECT permission was denied on the object 'Categories', database 'Blog', schema 'dbo'.

Source Error:

Line 33: SqlConnection connection = CreateConnection();
Line 34: SqlCommand command = CreateCommand(connection, query, parameters);
Line 35: SqlDataReader reader = command.ExecuteReader(CommandBehavior.CloseConnection);
Line 36:
Line 37: Type datatype = factory.GetDataType();

Source File: c:\Inetpub\blogplankroad\App_Code\Utilities\SqlDatabase.cs Line: 35

Hi Planker,

Just as the exception message describes, the user account you're using to connect to the database does not have permission to perform a SELECT on the certain table.

In the SQL Server Management Studio, please open the user property window and grant the proper permission for the user.

HTH. If this does not answer you question, please feel free to mark it as Not Answered and post your reply. Thanks!

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>

Deployed report fails to start

VS2005 project with imbedded SQL Server reports works fine in VS IDE going agianst a network SQL Server 2005 or the local SQL Server 2005. However, when the application is deployed (to another computer). the application starts and connects successfully to the network SQL Server 2005. Everything works until the user tries to produce a report. Then the following error is generated:

Named Pipes Provider, error: 0 - No process is on the other end of the pipe (the verbose part of the error message is left out). SQL Server agent is running both on the file server and the local computer. Also, named pipes and shared memory are enabled in file server and local computer (TCP and VIA protocoles are disabled). Same is done for Client protocoles.

Any suggestions are greatly appreciated.

Go to SQL Surface are configuration -&gt; Surface Area configuration for services and connections -&gt;; Datsbase engine -&gt; remote connections and check if remote connections using TCP/IP and named pipes is enabled.gatharia|||

Have you enabled remote network connections?

http://codebetter.com/blogs/sahil.malik/archive/2005/11/05/134318.aspx

|||

Tks for suggestion. Both on the file server and the local computer I have set the Surface Area ... to TCP/IP and Named Pipes. Please note that the access to and use of the SQL server database engine is not a problem. Everything works. The problem is related to the SSRS. That is the problem occurs when the report program tries to access the database.Maybe in the way the report dataset or datasource is defined. But then why does it work from within IDE?

|||

Yes I have. Connecting to database engine is no problem. Failure occurs when the report function tries to access the database.

|||Are you using integrated security for your datsets? I recommend using sql login.

Deploy successful, but updated report not showing...

Using VS2005 to deploy an updated report on a machine running SQL 2005
Reporting Services.
VS states that the deployment was successful, but the old version of the
report is what's getting run.
Can't reset the Default Website on that machine as it's running the web
services behind our application.
What have I missed?
Kyle JedrusiakOn Dec 4, 11:47 am, "Kyle Jedrusiak"
<kjedrus...@.princetoninformation.com> wrote:
> Using VS2005 to deploy an updated report on a machine running SQL 2005
> Reporting Services.
> VS states that the deployment was successful, but the old version of the
> report is what's getting run.
> Can't reset the Default Website on that machine as it's running the web
> services behind our application.
> What have I missed?
> Kyle Jedrusiak
Try deleting the report and re-deploying it. It worked for me.