Saturday, February 25, 2012

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 -> Surface Area configuration for services and connections ->; Datsbase engine -> 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.

No comments:

Post a Comment