Showing posts with label copied. Show all posts
Showing posts with label copied. Show all posts

Thursday, March 22, 2012

Deployment problem

Hi. I created an app on my laptop and wish to deploy it to a server. I followed the steps to release the project and I copied the files over to the server. I'm getting an access denied or server does not exist error message. I went into the code behind pages to change the connection string but it still doesn't work. I think it has something to do with the SQL Server name. It's just local. The person that installed it did not change the name. In enterprise manager, it looks like this. (local) (Windows NT) Should the connection string be SERVER/(local) ? Is there a default name I'm not aware of? Any help would be greatly appreciated. Thanks!

Here is the error message:


Server Error in '/' Application.
------------------------

SQL Server does not exist or access denied.
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: SQL Server does not exist or access denied.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[SqlException: SQL Server does not exist or access denied.]
System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction) +474
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction) +372
System.Data.SqlClient.SqlConnection.Open() +384
System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState) +44
System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +304
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +77
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) +36
ICCSalesTracker.WebForm1.GetRGU() +433
ICCSalesTracker.WebForm1.Page_Load(Object sender, EventArgs e) +7
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +750

Another question, would local host work for server id?

Also, I took a look at PDB file and it still has my other file paths. Does that matter? Should they be changed?

And lastly, The web server admin does not want to use the inetpub folder so he created a different folder that houses all of the files. What will that effect? What do I have to change?

Please let me know. Thanks!!!!|||Hi,
It sounds like the app worked well on your laptop, but wont work when moved to a server. You need to understand the authentication and authorization scheme the app will use to access the DB. That situation may be different from the one you had on your laptop. You can use Windows Integrated security, if IIS and the SQL Server are on the same computer and the user is in the same domain. For an internet app, the client may not have credentials to pass, or passing them posses a risk, so ASP.NET uses a default user for it's worker process called ASPNET (it's called NETWORK SERVICE by Windows 2003 Server). SQL Server sees this default user and checks to see if it has permission to use that DB. In order to gain access to the DB, the ASPNET (or NETWORK SERVICE), user needs to be registered on the SQL Server and given the appropriate (just enough), permissions to use that DB. There are other factors and schemes, but you might just look to see that the SQL Server DB has the right user set up correctly.
Good luck.|||I added ASPNET & NT AUTHORITY and even my domain user is set to owner. It still will not pull it up.|||Hi,
Was the user in the form "NT_AUTHORITY\NETWORK SERVICE"? I know that worked for me one time on a local setup that didn't accept "thecomputername\NETWORK SERVICE". Also, are you sure that these default users have the correct read/write permissions set?

Some more that know more than I do will probably get you the right answer. If I had to figure it out myself, I might try using a different type of Authentication (Forms), just to see if I could get it working - then figure out how to get the authentication scheme I want working too. You might try writting a very simple data access app (using the Data Web Form wizard), just to test the connection. That way you don't have to messup your project.

Good luck.|||Thank you for your help Brian!

Well I figured out the server name. Apparently, if the server say local when you look at it in Enterprise Manager, you leave the sql servername blank in the connection string. "SERVER/"

Now I"m getting a login failed for user 'NT AUTHORITY\NETWORK SERVICE error even though IIS is set to windows integrated authentication. Is there another place I have to change a setting to ensure it only uses windows authentication?|||Hi,
Glad to hear that you are making some progress - even if my info wasn't much help.

Is the login error message from SQL Server?

In your message it says ...for user 'NT AUTHORITY\NETW...', but I think it should have an underscore between NT and AUTHORITY -- 'NT_AUTHORITY\NETWORK SERVICE'

It seemed odd to me that they connect the first two part name, and leave a blank in the second, but that's the way I saw it on my system. Double check.

Good luck.|||You are correct. I typed it in wrong. I had to add that user to the SQL users directory and now it loads. But now I have yet another problem. The initial page loads. It has an onload function that calls a stored procedure to return the number of units sold for the day. That works just fine. The second part of the page is the order entry function that passes parameters to an insert procedure. When I click on submit, I get an access denied or server not found error. It's wierd because it's using the same connection string as the on load procedure. Do you have any idea what that might be? Thanks for the help!|||Hi,
Looks like you are making progress.

I'm not sure about why the second part of the page wont function. My first guess is that the first part is only reading data, and it sounds like the second part is reading and writing. Are you sure that the user permissions include insert and update allowed?

You need to be very careful with any database access granted to internet users. That's even more the case when you grant write or execute permissions. Keep in mind that it's one thing to get it working, but you'll want to make sure you have the security issues understood and accounted for before you deploy the application. I'm still working my way through this myself. Using stored procedures for the functions that your users will perform is generally a good idea, but they're not a security panacea. You'll have to do some research to find the best safegaurds. I know that MSDN has some series on security best practices, webcasts, etc...

One other thing occurs to me, if you don't have a compelling reason to have both the functions you mentioned on the same aspx page, consider moving the second to another page, with a link from the first. My thought is that it compartmentalizes the functions, and it could make it easier to track down problems, and keep the first function available, even if the other is broken. You'll know if it makes sense to do this in your project.

Let me know how it goes for you.|||All of the required users have permissions to all of the objects in the database. This is an intranet and the security is set to windows integrated. The reason the page has both the on load and on submit function is to track entered units in real time. As they enter in sales, the datagrid tied to the getunit stored procedure runs every time the page loads. So when the sales agent enters in 2 revenue units, datagrid reflects those units when the page reloads. That portion works just fine. However when I click submit, I get the following error


Server Error in '/' Application.
------------------------

SQL Server does not exist or access denied.
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: SQL Server does not exist or access denied.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[SqlException: SQL Server does not exist or access denied.]
System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction) +474
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction) +372
System.Data.SqlClient.SqlConnection.Open() +384
ICCSalesTracker.WebForm1.btnSubmit_Click(Object sender, EventArgs e) +7239
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +57
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +18
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33
System.Web.UI.Page.ProcessRequestMain() +1292

I'm pretty sure it's not the connection string as that is specified in the web.config file. I'm thinking it has something to do with IIS or something. Thanks for the help! I'll let you know if I figure it out...

Sunday, March 11, 2012

Deploying Reports to a New Server

I developed some reports on one system that I would like to move to another
system. I copied the rdl file to the new system and uploaded it via Report
Manager.
The data source the report uses is based upon SQL views which I created on
the new server.
I'm having a problem with the data source. I've tried creating a new custom
data source by going to the properties of the report and clicking on Data
Sources. I've also tried creating a new data source by clicking New Data
Source from the home page of the Reports.
I've received login errors using the sa account and I've seen that, despite
picking a new data source, it still seems to use the old data source.
What do I need to do to point the report to a the current server's data?
--
Charles Allen, MVPIf both the servers are accessible on your network, just go to report project
properties and change the server to your new server and deploy it, instead of
you doing it does the job perfectly, including datasource..
Amarnath
"Charles Allen" wrote:
> I developed some reports on one system that I would like to move to another
> system. I copied the rdl file to the new system and uploaded it via Report
> Manager.
> The data source the report uses is based upon SQL views which I created on
> the new server.
> I'm having a problem with the data source. I've tried creating a new custom
> data source by going to the properties of the report and clicking on Data
> Sources. I've also tried creating a new data source by clicking New Data
> Source from the home page of the Reports.
> I've received login errors using the sa account and I've seen that, despite
> picking a new data source, it still seems to use the old data source.
> What do I need to do to point the report to a the current server's data?
> --
> Charles Allen, MVP
>|||Thank you for replying quickly.
In this case, the machines are not on the same network. One is a test
environment I use and the other is a client's production system.
--
Charles Allen, MVP
"Amarnath" wrote:
> If both the servers are accessible on your network, just go to report project
> properties and change the server to your new server and deploy it, instead of
> you doing it does the job perfectly, including datasource..
> Amarnath
> "Charles Allen" wrote:
> > I developed some reports on one system that I would like to move to another
> > system. I copied the rdl file to the new system and uploaded it via Report
> > Manager.
> >
> > The data source the report uses is based upon SQL views which I created on
> > the new server.
> >
> > I'm having a problem with the data source. I've tried creating a new custom
> > data source by going to the properties of the report and clicking on Data
> > Sources. I've also tried creating a new data source by clicking New Data
> > Source from the home page of the Reports.
> >
> > I've received login errors using the sa account and I've seen that, despite
> > picking a new data source, it still seems to use the old data source.
> >
> > What do I need to do to point the report to a the current server's data?
> > --
> > Charles Allen, MVP
> >|||ok, MS has provided a sample script on "how to deploy the reports using
command prompt", you can have a look at that sample for your solution.
Amarnath
"Charles Allen" wrote:
> Thank you for replying quickly.
> In this case, the machines are not on the same network. One is a test
> environment I use and the other is a client's production system.
> --
> Charles Allen, MVP
>
> "Amarnath" wrote:
> > If both the servers are accessible on your network, just go to report project
> > properties and change the server to your new server and deploy it, instead of
> > you doing it does the job perfectly, including datasource..
> >
> > Amarnath
> >
> > "Charles Allen" wrote:
> >
> > > I developed some reports on one system that I would like to move to another
> > > system. I copied the rdl file to the new system and uploaded it via Report
> > > Manager.
> > >
> > > The data source the report uses is based upon SQL views which I created on
> > > the new server.
> > >
> > > I'm having a problem with the data source. I've tried creating a new custom
> > > data source by going to the properties of the report and clicking on Data
> > > Sources. I've also tried creating a new data source by clicking New Data
> > > Source from the home page of the Reports.
> > >
> > > I've received login errors using the sa account and I've seen that, despite
> > > picking a new data source, it still seems to use the old data source.
> > >
> > > What do I need to do to point the report to a the current server's data?
> > > --
> > > Charles Allen, MVP
> > >

Wednesday, March 7, 2012

Deploying AS to Production

Hi,

Is this the right deployment procedure: I copied the whole project to production server and re-processes the cube. Does the OLAP database resides in \bin or is it the one in C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data? What's the extension name?

Thanks alot!

cherriesh

Copy the whole project is not really required. The database in the \bin folder is the one that was last built from the BI Development Studio (BIDS), but you do not deploy this file by copying it. In your program files folder where you have installed BIDS you should have an Analysis Services folder with an Analysis Services deployment wizard. This wizard allows you to do a number of things that are useful when deploying to production such as changing or retaining data source connection strings and retaining roles and partitions which may be different between dev and prod.

Also from BIDS, you can setup different profiles and change the target server for the deploy operation from BIDS, but if you needed to change data source connections you would need to remember to do that yourself.

|||

Hi,

After deployment, does the AS database reside in the drive where Analysis Services resides? I'm afraid in the server it is installed in C:\ with only 10GB instead of in the D:\ which has much greater space capacity..

cherriesh

|||

Hi,

If you open up the management studio and right click on the server instance and look at the properties. The Property DataDir will tell you where it's storing the databases. You can change it if it is wrong from C: to D: and you might want to change the backup and log directories property too (BackupDir, LogDir).

Hope that helps

Matt

|||

Hi,

Done with LogDir, BackUpDir and DataDir. I also saw the AllowedBrowsingFolder that is set to :

C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Log|C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Backup

Do I have to change this also?

I've done the Deployment wizard and I have generated the .xmla script. How to proceed from there?

cherriesh

|||

Hi,

Probably worth doing the AllowedBrowsingFolder to, it populates the drop down when you are backup and restore, various things like that.

On the assumption your script looks something like:

<Alter AllowCreate="true" ObjectExpansion="ObjectProperties" xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">

<Object />

<ObjectDefinition>

<Server xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlnsBig Smiledl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlnsBig Smiledl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2">

<ID>SERVER</ID>

<Name>SERVER</Name>

<ServerProperties>

<ServerProperty>

<Name>BackupDir</Name>

<Value>D:\Microsoft SQL Server\MSSQL.4\OLAP\Backup</Value>

</ServerProperty>

</ServerProperties>

</Server>

</ObjectDefinition>

</Alter>

Just open an xmla query, run it on the server and restart the service. It should in theory create the directories, pretty sure it did when i have done this before. If there is anything already on the AS Server, best to back that up first then restore it in the new location.

Any problems, just post again.

Matt

|||

hi,

sorry im really new to this. how do i run this .xmla in the server? what command?

thanks a lot!

cherriesh

|||

Hi,

Not to worry. If you open up management studio, click on File, then New, Analysis Services XMLA Query. Type in the server you are changing into "Server Name"

Or there is an icon on the query tool bar, has XMLA in green on it, if you hover over it it will say "Analysis Services XMLA Query".

An Alternative to not running XMLA:

If you are in management studio, connect to the server and right click the server in the object explorer. You can manually change the settings in the properties there.

If I didn't make any sense:

http://www.microsoft.com/technet/prodtechnol/sql/2005/ssasproperties.mspx

(Figures 1 and 2 are the wrong way around though)

remember to restart it the service

Hope that helps

Matt

|||

Thanks a lot! this really helps. is it the AS service that i need to restart? because, when i ran the .xmla, i could already see the AS database in the Management Studio. Does it really important to restart?

thanks!

cherriesh

|||

The changes you make won't actually take effect until you do, just the AS service.

No problem

Matt

Deploying AS to Production

Hi,

Is this the right deployment procedure: I copied the whole project to production server and re-processes the cube. Does the OLAP database resides in \bin or is it the one in C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data? What's the extension name?

Thanks alot!

cherriesh

Copy the whole project is not really required. The database in the \bin folder is the one that was last built from the BI Development Studio (BIDS), but you do not deploy this file by copying it. In your program files folder where you have installed BIDS you should have an Analysis Services folder with an Analysis Services deployment wizard. This wizard allows you to do a number of things that are useful when deploying to production such as changing or retaining data source connection strings and retaining roles and partitions which may be different between dev and prod.

Also from BIDS, you can setup different profiles and change the target server for the deploy operation from BIDS, but if you needed to change data source connections you would need to remember to do that yourself.

|||

Hi,

After deployment, does the AS database reside in the drive where Analysis Services resides? I'm afraid in the server it is installed in C:\ with only 10GB instead of in the D:\ which has much greater space capacity..

cherriesh

|||

Hi,

If you open up the management studio and right click on the server instance and look at the properties. The Property DataDir will tell you where it's storing the databases. You can change it if it is wrong from C: to D: and you might want to change the backup and log directories property too (BackupDir, LogDir).

Hope that helps

Matt

|||

Hi,

Done with LogDir, BackUpDir and DataDir. I also saw the AllowedBrowsingFolder that is set to :

C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Log|C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Backup

Do I have to change this also?

I've done the Deployment wizard and I have generated the .xmla script. How to proceed from there?

cherriesh

|||

Hi,

Probably worth doing the AllowedBrowsingFolder to, it populates the drop down when you are backup and restore, various things like that.

On the assumption your script looks something like:

<Alter AllowCreate="true" ObjectExpansion="ObjectProperties" xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">

<Object />

<ObjectDefinition>

<Server xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlnsBig Smiledl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlnsBig Smiledl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2">

<ID>SERVER</ID>

<Name>SERVER</Name>

<ServerProperties>

<ServerProperty>

<Name>BackupDir</Name>

<Value>D:\Microsoft SQL Server\MSSQL.4\OLAP\Backup</Value>

</ServerProperty>

</ServerProperties>

</Server>

</ObjectDefinition>

</Alter>

Just open an xmla query, run it on the server and restart the service. It should in theory create the directories, pretty sure it did when i have done this before. If there is anything already on the AS Server, best to back that up first then restore it in the new location.

Any problems, just post again.

Matt

|||

hi,

sorry im really new to this. how do i run this .xmla in the server? what command?

thanks a lot!

cherriesh

|||

Hi,

Not to worry. If you open up management studio, click on File, then New, Analysis Services XMLA Query. Type in the server you are changing into "Server Name"

Or there is an icon on the query tool bar, has XMLA in green on it, if you hover over it it will say "Analysis Services XMLA Query".

An Alternative to not running XMLA:

If you are in management studio, connect to the server and right click the server in the object explorer. You can manually change the settings in the properties there.

If I didn't make any sense:

http://www.microsoft.com/technet/prodtechnol/sql/2005/ssasproperties.mspx

(Figures 1 and 2 are the wrong way around though)

remember to restart it the service

Hope that helps

Matt

|||

Thanks a lot! this really helps. is it the AS service that i need to restart? because, when i ran the .xmla, i could already see the AS database in the Management Studio. Does it really important to restart?

thanks!

cherriesh

|||

The changes you make won't actually take effect until you do, just the AS service.

No problem

Matt

deploying a report to a site hosted by 3rd party

I have been trying to deploy a web app that uses sql reports. I have copied the 3 dlls that are talked about.

Microsoft.ReportViewer.Common.dll
Microsoft.ReportViewer.WebForms.dll
Microsoft.ReportViewer.ProcessingObjectModel.dll

When I do this I get the following error:

Server Error in '/' Application.

Required permissions cannot be acquired.

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.Security.Policy.PolicyException: Required permissions cannot be acquired.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.


Stack Trace:

[PolicyException: Required permissions cannot be acquired.] System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Boolean checkExecutionPermission) +2737813 System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Int32& securitySpecialFlags, Boolean checkExecutionPermission) +57[FileLoadException: Could not load file or assembly 'Microsoft.ReportViewer.Common, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)] System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +0 System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +211 System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +141 System.Reflection.Assembly.Load(String assemblyString) +25 System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +32[ConfigurationErrorsException: Could not load file or assembly 'Microsoft.ReportViewer.Common, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)] System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +596 System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() +3479097 System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai) +46 System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig) +177 System.Web.Compilation.WebDirectoryBatchCompiler..ctor(VirtualDirectory vdir) +267 System.Web.Compilation.BuildManager.BatchCompileWebDirectoryInternal(VirtualDirectory vdir, Boolean ignoreErrors) +36 System.Web.Compilation.BuildManager.BatchCompileWebDirectory(VirtualDirectory vdir, VirtualPath virtualDir, Boolean ignoreErrors) +429 System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) +73 System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) +580 System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) +93 System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert) +111 System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert) +54 System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) +31 System.Web.UI.PageHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) +40 System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig) +139 System.Web.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +120 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155



Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

why does this not work?

Thanks,

enak

I would venture that you need to register the dll's in the gac. I'm rolling out an app to a custom webserver and had similiar problems. I need an ide on the machine so I install visual web developer and the reporting services add in and took care of my problem. The install would have taken care of the proper registering.