on 09-11-2013 8:59 AM
Hi All,
I have created a universe with OLE DB drivers. I could see the LOVs for objects created but when I create a WEBI report based off the same universe, I am getting below error. From Rich Client I am able to create a report however after I publish it with OPEN ON REFRESH it throws the error.
Database error: [Microsoft SQL Server Native Client 10.0] : Named Pipes Provider: Could not open a connection to SQL Server [53]. . (IES 10901) (WIS 10901)
As it is working from client machine but not from BI LaunchPad, I think it is referring to something that resides on client machine and not on server.
Environment:
BI 4.0 SP06
SQL server 2008.
Client tools on same patch level.
Regards,
Tejas
Hi guys,
Thanks for your suggestions.
It was not a DSN issue as I use OLE DB drivers.
I could have it resolved with my ADMIN. The issue was connectivity between my database and BO server.
I was able to ping the database server from my machine but not from BO server.
DNS name for server was not able to resolve. We then made a host entry on server and have it worked
Thanks for all your help.,
Tejas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tejas,
You need to check your system ODBC connection settings. Check the DSN details.
Try to create a new connection again.
If you are able to run this it in client machine than its a connection problem in your machine.
Please check.
- Vignesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
this just means that you did not setup 64bit connection to this data source on your server.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tejas,
Try just to create a new connection then modify the universe connection accordingly and exported it back.
Regards,
Amine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A few things to check:
Is TCP/IP enabled on the server?
Are the correct ports open in the firewall?
Log on remotely to your server and run cliconfg.exe
If named pipes is first, demote it to below TCP/IP
Error 53 is a bad network path so the firewall is the most likely problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.