Unable to connect BO XI3.1 SP3 on linux to sql server 2008

I am looking for some assistance with trying to connect to sql server 2008 db. We have BO XI 3.1 SP3 installed in linux environment. Was able to set up oracle and db2 variable to connect to oracle and db2 universes, after loading the db2 client and oracle 32b client. trying to connect to sql server 2008, but getting error Unable to Bind Configuration Object -(WIS 10901). Thank You.

Hi Ravi,
Depending on the version you may find useful some KB articles:
[1463263 - Error: Unable to bind to Configuration object (WIS 10901) - SQL driver for UNIX server |https://service.sap.com/sap/support/notes/1463263] (XI3.1)
[1607125 - How to configure SQL Server connectivity for WebIntelligence from a BI4.0 unix environment? |https://service.sap.com/sap/support/notes/1607125] (BI4.0)
[1607125 - How to configure SQL Server connectivity for WebIntelligence from a BI4.0 unix environment? |https://service.sap.com/sap/support/notes/1607125] (BI4.0)
If this doesn't help can you please specify version and patch level, as well as the exact error message you get.
Thanks and regards
Simone

Similar Messages

How to connect captivate file in a database (MS SQL SERVER 2008)

Hi...
How to connect captivate file in a database (MS SQL SERVER 2008) ???
Kindly response please..
thanks!!!

Hi there
See if the link below helps you out.
Click here to view
Cheers... Rick
Helpful and Handy Links
Captivate Wish Form/Bug Reporting Form
Adobe Certified Captivate Training
SorcerStone Blog
Captivate eBooks

Unable to connect Informatica on Sun Solaris to a SQL Server datasource

Background*
We have a fully operational OBIEE with OBIA Apps infrastructure running with Informatica PC8.6 ETL suite. Informatica services are running on a Sun Solaris 64 bit platform.
We currently extract data from two Oracle EBS 11.5.10 sources. Now we are trying to extract data from a new MS SQL Server 2000 source into the OBAW.
Problem*
I'm trying the use the native ODBC 5.2 Data Direct driver to connect the the data source.
I've gone through and completed the 9 steps of the 'Connecting to an ODBC Data Source' chapter in Informatica on our Solaris Unix box.
I've made the following changes to the *.profile*
# ODBC HOME
ODBC_HOME=/oracle/Informatica/PowerCenter8.6.0/ODBC5.2
export ODBC_HOME
ODBC_INI=/oracle/Informatica/PowerCenter8.6.0/ODBC5.2/odbc.ini
export ODBC_INI
PATH=${PATH}:$ODBC_HOME/bin
export PATH
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$ODBCHOME/lib
export LD_LIBRARY_PATH
I've also made changes to the odbc.ini file as suggested:
[MSS_DB]
Driver=/oracle/Informatica/PowerCenter8.6.0/ODBC5.2/lib/DWmsss22.so
Description=DataDirect 5.2 SQL Server Wire Protocol
Address=MssServer.xxx.co.uk,1433
AlternateServers=
AnsiNPW=Yes
ConnectionRetryCount=0
ConnectionRetryDelay=3
Database=MIS_Report_DB
LoadBalancing=0
LogonID=myuser
Password=mypwd
QuotedId=No
ReportCodePageConversionErrors=0
InstallDir=/oracle/Informatica/PowerCenter8.6.0/ODBC5.2
I've created the Connection--> Relational --> ODBC connection on Workflow Manager
I've specified the username/pwd and connect string MssServer.xxx.co.uk@MIS_Report_DB. I've called it exactly the same as MSS_DB specified in the odbc.ini
When I run the workflow. It fails but doesn't throw up any error/error code in the session log. The last 3 lines of the Session Log below and then it just bombs out within 5 secs.
PETL_24006 : Starting data movement.
TM_6660 : Total Buffer Pool size is 4234808 bytes and Block size is 468312 bytes.
DBG_21438 : Reader: Source is [MssServer.xxx.co.uk], user [myuser]
If you ping from the Unix server it says 'MssServer.xxx.co.uk is alive'
Can anyone suggest what we need to do different or spot something obvious?
Edited by: bebedi123 on 13-Apr-2010 09:43

user00726 wrote:
i am able to create files in /tmp
$ pwd
/tmp
$ touch test
$ ls -l
total 64
drwxr-xr-x   2 root     other        194 May 27 14:20 OraInstall2009-05-27_02-20
-02PM
drwxr-xr-x   2 root     other        194 May 27 14:35 OraInstall2009-05-27_02-35
-06PM
drwxr-xr-x   6 root     other        445 May 27 14:38 OraInstall2009-05-27_02-38
-48PM
-rw-rw-r--   1 root     sys         6644 May 27 14:00 ps_data
-rw-r--r--   1 oracle   dba            0 May 27 16:04 test
$and i have also removed /tmp_dir_n8ai9b files
but still there is a problemYou have root as owner of subdirectories (e.g. OraInstall2009-05-27_02-38-48PM) and not oracle:
- do you install as root now?
- or make the directories writable for oracle, too.The write flag is missing (something like chmod -R a+w OraInstall2009-05-27_02-38-48PM)
Edited by: TanteKaethe on May 28, 2009 9:54 AM

How to connect from Oracle 11g to SQL Server 2008 R2

Hi,
Is it possible to connect from Oracle 11g on AIX to SQL Server 2008 R2? If so, what is the preferred method?
SQL Server has the original table. From Oracle 11g, we want to access data which is in SQL Server real time.
Thank You
Sarayu

Hi,
Have a look at these Oracle notes for the full information on the gateways -
Master Note for Oracle Gateway Products (Doc ID 1083703.1)
Functional Differences Between DG4ODBC and Specific Database Gateways (Doc ID 252364.1)
Gateway and Generic Connectivity Licensing Considerations (Doc ID 232482.1)
How to Setup DG4MSQL (Oracle Database Gateway for MS SQL Server) 64bit Unix OS (Linux, Solaris, AIX,HP-UX) (Doc ID 562509.1)
How to Configure DG4ODBC on 64bit Unix OS (Linux, Solaris, AIX, HP-UX Itanium) to Connect to Non-Oracle Databases Post Install (Doc ID 561033.1)
The Database Gateway for SQL*Server (DG4MSQL) needs a separate license but the Database Gateway for ODBC (DG4ODBC) is included in your RDBMS license. You only need to provide the third party ODBC driver needed by DG4ODBC.
Regards,
Mike

Unable to connect to SQL Server 2008 from OBIEE 11G(on 64 bit Linux box)

We are unable to connect to connect to SQL Server 2008 from OBIEE 11G which is on 64 bit Red Hat Enterprise Linux.
Infrastructure: OBIEE 11.1.1.5 64bit, on 64 bit Red Hat Linux Enterprise Linux 5.6 , MS SQL Server 2008 on 64 bit Microsoft Windows Server
Issue Description: Unable to connect to SQL Server 2008 from OBIEE11G RPD
Details: We are unable to connect to SQL Server 2008 from OBIEE which is on a 64 bit Linux box. We created the ODBC connection on Linux box to the SQL server. Whenever we try to import metadata it throws an error that says ‘Connection Failed’.
Here are the steps we followed to setup the ODBC connection on Linux box.
1) We updated the user.sh file with the LD_LIBRARY_PATH and LD_LIBRARY_PATH_64 values that point to $ORACLE_HOME/bifoundation/odbc/lib
This is where we found the driver for SQL server SEmsss23.so.
2) We updated the odbc.ini file with the entry for SQL server with the connection details
SI_SQL_Server_DEV = SQL Server
[SI_SQL_Server_DEV]
Driver=/u001_OAS/Oracle/Middleware/Oracle_BI1/bifoundation/odbc/lib/SEmsss23.so
Description=DataDirect 5.1 SQL Server Wire Protocol
Address=10.230.216.52,54970
AlternateServers=
AnsiNPW=Yes
ConnectionRetryCount=0
ConnectionRetryDelay=3
Database=SVBDW_NEW
LoadBalancing=0
LogonID=SIDatavalidation
Password=~~~Password123
QuoteID=No
ReportCodePageConversionErrors=0
3) We updated the IDENTIFIER_QUOTE_CHAR with single quotes instead of double quotes in the DB features of the RPD
4) We updated the bash_profile file to point the ODBCINI variable to the path where the OBIEE odbc.ini file is present.
Export ODBCINI=/u001_OAS/Oracle/Middleware/instances/instance1/bifoundation/OracleBIApplication/coreapplication/setup/odbc.ini
The error in nqsserver.log file says “[nQSError: 16001] ODBC error state: IM002 code: 0 message: [DataDirect][ODBC lib] Data source name not found and no default driver specified.”

Hi,
Make sure SQL Configuration Manager make sure the TCP/IP enabled. please try below method
Method 1
Re Create a new ODBC & Oracle Bi Server DSN Configuration test it and use it in the connection pools.
define your ODBC data source in your server where the BI Server is installed. Check your DB connections in your physical layer and make they are defined on your BI Server as well.
Method 2:
try using the complete TNS in below format in the datasource name section:
(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST =DB IP)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = ORCL) ) and provide the credentials.
Method 3:
To use the OCI call interface you need to have oracle client DB to be installed so that you can establish a connection using that DB credentials and connect to the remote dB and then import the tables.....this is the rule of thumb.
hope helps you.
Thanks
Deva

Unable to connect to sql server 2008

i have windows 8 64-bit on my system, i installed sql server 2008 it installed successfully, but now i'm unable to open server management studio, it is showing error like "provider:named pipes provider, error:40-
could not open a connection to sql server microsoft sql
server, error:2" and in configuration manager there is nothing under "sql server services and sql server network configuration"kindly help me to fix this problem

Hello,
Please run the Discovery Report as shown in the following resource and make sure the Database Engine Services is listed
on the report.
http://blogs.msdn.com/b/petersad/archive/2009/11/13/sql-server-2008-discovery-report.aspx
If the Database Engine Services is listed on the report, please apply SP3 for SQL Server 2008 since SQL Server is not compatible with Windows 8 without that service pack.
http://support.microsoft.com/kb/2681562
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Unable to connect to sql server 2008 r2 after upgrading from framework 4.0 to 4.5.2 in windows 7 environment

Hi All,
BackGround
I used to connect to database with Encrypt set true in sql connection which helps established encrypted data base connection . I verified that created certificate in order
to provide Encrypted connection to database for client is valid.
Issue :Issue
is un-able to connect to sql sever2008 r2 from vs2013 by enforcing encryption to true.
while trying to test the connection from vs2013 error log getting recorded as well as error notification is getting populated as below .
Step1 :
from Vs2013 trying to connect to sql server 2008 r2
step 2: on Click test Connection . getting below mentioned error notification
Event Viewer Log:<o:p></o:p>
<o:p></o:p>
(Process Id: 7472)
<o:p></o:p>
.Net SqlClient Data Provider:<o:p></o:p>
A connection was successfully established with the server, but then an error
occurred during the login process. (provider: SSL Provider, error: 0 - The
target principal name is incorrect.)<o:p></o:p>
   at
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception,
Boolean breakConnection, Action`1 wrapCloseInAction)<o:p></o:p>
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)<o:p></o:p>
   at
System.Data.SqlClient.TdsParserStateObject.SNIWritePacket(SNIHandle handle,
SNIPacket packet, UInt32& sniError, Boolean canAccumulate, Boolean
callerHasConnectionLock)<o:p></o:p>
   at System.Data.SqlClient.TdsParserStateObject.WriteSni(Boolean
canAccumulate)<o:p></o:p>
   at System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte
flushMode, Boolean canAccumulate)<o:p></o:p>
   at System.Data.SqlClient.TdsParser.TdsLogin(SqlLogin rec,
FeatureExtension requestedFeatures, SessionData recoverySessionData)<o:p></o:p>
   at
System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo
serverInfo, String newPassword, SecureString newSecurePassword, Boolean
ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)<o:p></o:p>
   at
System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo
serverInfo, String newPassword, SecureString newSecurePassword, Boolean
redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential
credential, TimeoutTimer timeout)<o:p></o:p>
   at
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer
timeout, SqlConnectionString connectionOptions, SqlCredential credential,
String newPassword, SecureString newSecurePassword, Boolean
redirectedUserInstance)<o:p></o:p>
   at
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, SqlCredential credential,
Object providerInfo, String newPassword, SecureString newSecurePassword,
Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions,
SessionData reconnectSessionData)<o:p></o:p>
   at
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo,
DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions
userOptions)<o:p></o:p>
   at
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool
pool, DbConnection owningObject, DbConnectionOptions options,
DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)<o:p></o:p>
   at
System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection
owningObject, DbConnectionOptions userOptions, DbConnectionInternal
oldConnection)<o:p></o:p>
   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection
owningObject, DbConnectionOptions userOptions, DbConnectionInternal
oldConnection)<o:p></o:p>
   at
System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection
owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate,
Boolean onlyOneCheckConnection, DbConnectionOptions userOptions,
DbConnectionInternal& connection)<o:p></o:p>
   at
System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection
owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions,
DbConnectionInternal& connection)<o:p></o:p>
   at
System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection
owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions
userOptions, DbConnectionInternal oldConnection, DbConnectionInternal&
connection)<o:p></o:p>
   at
System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection
outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1
retry, DbConnectionOptions userOptions)<o:p></o:p>
   at
System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)<o:p></o:p>
   at
System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)<o:p></o:p>
   at System.Data.SqlClient.SqlConnection.Open()<o:p></o:p>
Inner Exception:<o:p></o:p>
:<o:p></o:p>
The target principal name is incorrect

The target principal name is incorrect
Hi Rahul.U,
Are you able to connect to SQL Server successfully from SQL Server Management Studio (SSMS) when enforcing encryption?
According to above error message, it could be caused by the inappropriate server name or incorrect TrustServerCertificate configuration in the connection string from Visual Studio. There are some proposals for you troubleshooting this error.
1. Make sure that you connect to the SQL server using the fully qualified domain name (FQDN).
2. When connecting to a SQL Server instance with a valid certificate, please add the
TrustServerCertificate
parameter and set it to true in the connection string. For more details, please review this
article.
However, if you can successfully connect to SQL Server via SSMS, but still fail to connect to SQL Server from Visual Studio, I would like to recommend you post the question in the .Net Framework forum at
https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?category=netdevelopment . It is appropriate and more experts will assist you.
There are similar articles about error “The target principal name is incorrect” for your reference.
http://serverfault.com/questions/458935/aws-rds-sql-server-ssl-connection-the-target-principal-name-is-incorrect
http://www.derekseaman.com/2013/09/sql-2012-failover-cluster-pt-12-kerberos-n.html
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

JTDS not connecting with SQL Server 2008 R2 SP2 + SSL with Java 6 U34-35

Environment:
Windows 7 Pro 32-bit
SQL Server 2008 R2 SP2 (Forced Encryption = Yes, No Certificate provided to server)
Java 6 Update 27-35 and Java 7 Update 2-7
jTDS 1.2.2 and 1.2.6
Under the following setup, our Java application is able to connect to the SQL Server database:
- SQL Server 2008 R2 SP2
- Java 6 Update 27-33 or Java 7 Update 2-5
just switching the JVM to the following would cause the application to be unable to connect to the database:
- Java 6 Update 34 or 35, or Java 7 Update 6 or 7
Browsing through the Java 6 Update 34 release notes, it looks like nothing big was changed, so I'm wondering what has changed with Java 6 U34 and Java 7 U6. I was also looking through a packet sniffer, and indeed the behavior of Java 6 Update 33 and lower was different from Java 6 Update 34 (although I couldn't understand the messages being passed, the number of connections and messages were different).
* This is different from the issue with Java 6 Update 29-30 and Java 7 wherein they were patched for the BEAST SSL vulnerability. That was fixed with the SP2 patch for SQL Server 2008 R2, and for SQL Server 2008 you'd need a hotfix aside from SP3. After patching the server with those updates, Java 6 Update 29-33 and Java 7 U1-5 should be able to connect to the database.
* If I do switch off Force Encryption, all Java versions are able to connect to the database.
Edited by: user1357749 on Oct 12, 2012 1:20 AM

Hi,
It's four months later, but my colleague and I have reproduced the same behavior in both our commercial product, and a very simple example class. It's exactly as you describe it, where the latest versions of both Java 6 and 7 (and several previous versions) hang during the first jTDS SQL query to the DB (immediately after the SSL and handshake). It also happens with the Microsoft JDBC driver.
If you disable the BEAST SSL fix (-Djsse.enableCBCProtection=false), then the connections work without any problems. So, while this is different from the original BEAST SSL problem and subsequent fix, it really seems like some additional changes were made to the fix in a later Java release that broke things.
My colleague has filed a bug with Oracle, and is awaiting a response. We also filed a bug at the jTDS project (#690 - http://sourceforge.net/p/jtds/bugs/690/) that has simple reproduction steps. A contributer at the jTDS project agrees that this seems to be a problem with the JRE, and is not specific to jTDS.
I hope that Oracle will address this issue soon. We need to periodically update the JRE due to vulnerabilities, and we need to have SSL for our JDBC connections for security reasons. This bug puts us and others in a difficult position.

Unable to upgrade SQL Server 2008 R2 to SQL Server 2012 SP1

I'm encountering error after error, after successfully installing the upgrade advisor (which took some doing) and running it with essentially no warnings/errors (the one warning was on the connection strings, as I recall -- and all of the warnings had a
"fix after" status.
First failure involved SSRS and the inability to create the "managed account". Backed out the upgrade using http://sqldbanotes.blogspot.com/2013/10/how-to-fix-failed-in-place.html
Now the failure involves SSAS and unable to connect to analysis services with name MSSQLServerOLAPService. That is the logical name for the service, although it shows up as just MSSQLServer when looking at it in the services list. I tried
setting the service account to a local account as well as to Local System -- did not make a difference, the upgrade couldn't apparently find it regardless.
Has anybody successfully done an in place upgrade from SQL Server 2008 R2 to SQL Server 2012?

Hi Bob，
Thanks for your post and I am glad to hear that the issue is resolved. Thanks for you posting a reply to share your solution and I had marked it as answer. That way, other community members could benefit from your sharing.
Regards,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support

Crystal Reports XI connection problems - after updating to SQL Server 2008

Hello!
We have some ASP.NET 2.0 Applications that call some CR XI report files with parameters to generate PDF Files. After upgrading from SQL Server 2005 to 2008 the apps hang when trying to generate the PDFs. Some research with Fiddler showed that ever time a 401 Error is raised. Calling the reports directly from CR Designer with the same connection values and Parameter shows the appropriate data that means the log-in data iare functioning.
I already tried switching the data source driver from OLE DB to SQL Native - no effect!
Can it be that CR XI does not work with SQL Server 2008? Or is there an update for CR XI and SQL Server 2008?
Because we are in a hurry I hope somebody can solve my problem(s) ...?!
Thanks in advance,
Frank

Hi Frank,
No CR XI is not supported nor is any version completely at this time. What we've found issues in so far are the Time(7) time is returned as a string value and Stored Procedure Data/time parameter SQL creation. The Time(7) field is an OLE DB driver issue with Microsoft but the Date/time SP issue is our issue and it's currently tracked and escalated. It will be fixed for CR 2008 with SP3 I believe. And I've asked that the same fix be rolled back to CR XI R2 but waiting on the reply from R&D if it can be done.
What you need to do is download the trial version of CR XI R2 ( Release 2 ) and then use your XI Keycode to install it and it will work. Then update to the latest SP 5 Service Pack. XI is past it's end of life support which means there will be no updates or bug fixes any more.
Next, MS SQL Server 2008 does not work with the MDAC version of the Native drivers, you must install the MS SQL Server Client. You'll see the driver name is "MS SQL Server Native client 10". This is the one you need to use.
Another work around is to use ODBC, it seems to resolve all issues, but the client must be installed.
Thank you
Don

Connection pooling with SQL Server 2008 and Tomcat 6.0

Hello Everybody,
I'm creating a web application using struts 2.0 , tomcat 6.0 and sql server 2008.
Everything works fine but i'm unable to create connection pooling with sql server 2008.Please help me to solve this issue.
Code for this is as foolows:
in my META-INF/context.xml
<?xml version="1.0" encoding="UTF-8"?>
<Context path="/spas" docBase="spas"
debug="5" reloadable="true" crossContext="true">
<Resource
name="jdbc/spas_new"
auth="Container"
type="javax.sql.DataSource"
maxActive="20"
maxIdle="10"
maxWait="-1"
user="spas_user"
password="spas123"
driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver"
url="jdbc:sqlserver://HGL-0053\dbo:1433;databaseName=spas_new;responseBuffering=adaptive;"/>
</Context>
in my web.xml
<resource-ref>
<description>SQL Server Datasource</description>
<res-ref-name>jdbc/spas_new</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
and in my ConnectionThread.java file i've used:
Context ctx = new InitialContext();
if(ctx == null )
throw new Exception("Sorry! No Context Exception");
DataSource ds = (DataSource)ctx.lookup("java:/comp/env/jdbc/spas_new");
System.out.println("ds:"+ds);
conn=ds.getConnection();
Following is the exception:
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Login failed for user ''.)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1225)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
at login.V_SPAS_ConnectionThread.getConnection(V_SPAS_ConnectionThread.java:87)
at org.apache.jsp.login.v_005fspas_005flogin_005fpage_jsp._jspService(v_005fspas_005flogin_005fpage_jsp.java:95)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:337)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1085)
at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:263)
at org.apache.struts.action.RequestProcessor.internalModuleRelativeForward(RequestProcessor.java:1023)
at org.apache.struts.tiles.TilesRequestProcessor.internalModuleRelativeForward(TilesRequestProcessor.java:345)
at org.apache.struts.action.RequestProcessor.processForward(RequestProcessor.java:572)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:221)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
at org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:694)
at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:665)
at org.apache.jsp.index_jsp._jspService(index_jsp.java:54)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:337)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at login.V_SPAS_SecurityCheckFilter.doFilter(V_SPAS_SecurityCheckFilter.java:108)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user ''.

Hi Karthikeyan,
This is not the issue at all. I can open the management studio by the same login id and password and also i can make the database jdbc connection from plain java file.
It does not give me any problem by them.
I'm unable to find the actual problem. May be i'm missing something in connection pooling.
Please help.
Regards
Mina

Oracle 11.1.0.7 x64 to SQL Server 2008 connectivity

Hi There,
I'm trying to establish connectivity between oracle database running 11.1.0.7 64bit on windows 2008 server x64 to sql server 2008 database. Both databases (oracle and SQL) are on the same machine.
I know with the older oracle versions, we used to setup hs connection between the two databases, however, I've been reading note 466225.1 (How To : How to Setup DG4ODBC (Oracle Database Gateway for ODBC) on Windows 32bit) on metalink and it states the following:
>
Please be aware:
- DG4ODBC is first ported to 64bit Windows platforms starting with 11.2. Using a 32bit DG4ODBC on a 64bit Windows operating system is NOT certified.
- HSOLEDB is no longer available for 11g on Windows.
>
So, according to the above, I'm guessing that we won't be able to use dg4odbc to establish the connectivity between the two.. how about the old hsodbc setup under ORACLE_HOME\hs\admin ? would that work? or is there another way that w can do this?
I've been working on this and trying to get it going but not sure if I'm doing something wrong or it just doesn't work here..
On the server I did the following:
1. created the sqlserver DSN and tested the connection and it's all ok.
2. added the following to the tnsnames.ora
SQLCentralODBC =
(DESCRIPTION=
    (ADDRESS=(PROTOCOL=tcp)(HOST=188.87.135.90)(PORT=1522))
    (CONNECT_DATA=(SID=SQLCentralODBC))
    (HS=OK)
) 3. added the following to the listener.ora:
LISTENER_ELMSCENTRAL =
(ADDRESS_LIST=
      (ADDRESS=(PROTOCOL=tcp)(HOST=188.87.135.90)(PORT=1522))
SID_LIST_LISTENER_SQLCENTRAL=
(SID_LIST=
      (SID_DESC=
         (SID_NAME=SQLCentralODBC)
         (ORACLE_HOME=C:\oracle\product\11.1.0.7)
         (PROGRAM=hsodbc)
)4. the listener started ok, and I validated the dsn connection and it's all ok:
C:\Users\oracle>tnsping SQLCentralODBC
TNS Ping Utility for 64-bit Windows: Version 11.1.0.7.0 - Production on 21-MAY-2010 15:47:12
Copyright (c) 1997, 2008, Oracle. All rights reserved.
Used parameter files:
C:\oracle\product\11.1.0.7\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=188.87.135.90)(PORT=1522)) (CONNECT_DATA=(SID=SQLCentralODBC)) (HS
=OK))
OK (10 msec)
C:\Users\oracle>5. created the db link:
SQL> create database link LM_SQLC connect to sqlc_user identified by xxx using 'SQLCentralODBC';
Database link created.6. Test the connection:
SQL> select * from event@LM_SQLC;
select * from event@LM_SQLC
ERROR at line 1:
ORA-28545: error diagnosed by Net8 when connecting to an agent
Unable to retrieve text of NETWORK/NCR message 65535
ORA-02063: preceding 2 lines from LM_SQLC
SQL>Any ideas/help will be really appreciated.
Thanks alot.
Edited by: user4415740 on May 21, 2010 12:36 PM
Edited by: user4415740 on May 21, 2010 12:52 PM

They say "Using a 32bit DG4ODBC on a 64bit Windows operating system is NOT certified." but we do it extensively and it works just fine. You need to install a 32-bit home and create a listener for the 32-bit gateway. Only downside (aside from maintaining 2 homes) is that if you need to file an SR, you must prove that you're able to reproduce the problem when the gateway is running on a 32-bit OS. We keep a little 32-bit server around for this purpose and point our gateways to that box to reproduce issues for SR's.
If you want to run "certified" all the time, you could leave the gateways running in Production on a 32-bit OS, but it runs considerably slower this way, and all because Oracle won't support your SR's. You have to decide if you really think you'll hit an issue that wouldn't reproduce on the true 32-bit OS and decide if it's worth the risk. We've made our decision...
Good luck!

Connecting BI Pub with Microsoft SQL server 2008

I am trying to connect Microsoft SQL server 2008 as a Data source in BIP .
Using below info :
Driver Type : Microsoft sql server 2005
Database Driver class : com.microsoft.jdbc.sqlserver.SQLServerDriver
Connection String : jdbc:sqlserver://TXHOURDB71D:1443;DatabaseName=StewartAccessIntegration
I am unable establish the connection and the username and password which I giving is right for the connection.
Please let me know if I am missing any config steps.
AJ

Officially, you got to use Hyperion drivers.
For BIPublisher 10.1.3.4 and ++ to connect to Ms sql server,
use the following
This works well and better.
Driver class = hyperion.jdbc.sqlserver.SQLServerDriver
Connection String = jdbc:hyperion:sqlserver://SERVERNAME:PORT;DatabaseName=DBNAME;
http://winrichman.blogspot.com/2009/04/hyperion-driver-to-connect-to-ms-sql.html
In older versions.
you can also copy the drivers to the lib folder or applib folder and try what you were doing.
http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/b32481/toc.htm#T498352

MS SQL Server 2008 not getting installed properly - MOF compiler could not connect with the WMI server

I am trying to install SQL Server 2008 in my local machine. However, I kept running into errors with the following error message:
"The MOF Compiler could not connect with the WMI Server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such
as the failure of the WMI Server to start".
I also ran "rundll32 wbemupgd, UpgradeRepository" to rebuild WMI repository, it doesn't help either. I got the same error message.
Any ideas what settings I need to change in order to ensure a successful installation of SQL Server 2008?

"The MOF Compiler could not connect with the WMI Server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such
as the failure of the WMI Server to start".
I also ran "rundll32 wbemupgd, UpgradeRepository" to rebuild WMI repository, it doesn't help either. I got the same error message.
Any ideas what settings I need to change in order to ensure a successful installation of SQL Server 2008?
can you check below two links.Make sure previous failed installation is removed completely.
http://connect.microsoft.com/SQLServer/feedback/details/356258/the-mof-compiler-could-not-connect-with-the-wmi-server#
Solution given by Connect MS is:
Possibly the issue was caused by uninstalling from add-remove programs - at any rate, using aaron bertrand's suggestion below fixed the issue. Also of note - I used the local admin for the install.
http://sqlblog.com/blogs/aaron_bertrand/archive/2009/02/20/the-xp-sp3-msxml6-sp2-sql-server-debacle.aspx
yes - remove msxml6 and any other half installed portion of sql 2008 and REBOOT and install sql
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Missing MSI files SQL Server 2008 R2 SP3

I have hit an issue while installing Service Pack 3 for SQL Server 2008 R2. The existing version is
10.50.4295.0 (SP2+CU9)
When running the SP3 file the following error occurs
SQL Server Setup has encountered the following error:
The cached MSI file 'C:\Windows\Installer\91a4f43.msi' is missing.
Its original file is 'sql_engine_core_inst.msi' and it was installed for product 'SQL Server 2008 R2 SP2 Database Engine Services' from '\\ServerName\Share$\SQL\SQL105\ENT\x64\setup\sql_engine_core_inst_msi\', version '10.52.4000.0', language 'ENU'.
To resolve this problem, recover the missing file from the installation media and start setup again.
For more information about how to resolve this problem, see 'Steps to restore the missing Windows Installer cache files' (http://go.microsoft.com/fwlink/?LinkId=144387) in the Microsoft Knowledge Base.
Error code 0x84B20002.
The next I tried to remove CU9 before applying SP3. The following error occurred when CU 9 was attempted to be removed.
The cached patch file 'C:Windows\Installer\483c7040.msp' is missing.

Hello Alberto,
I tried this link
http://support.microsoft.com/kb/969052
Using the VB script FindSQLInstall I tried getting some details about the missing MSI files. Just sharing the details incase you may have some details or better insight on what it says.
!!!! C:\Windows\Installer\91a4f43.msi DOES NOT exist in the Installer cache. !!!!
      Action needed, recreate or re-establish path to the directory:
\\Servername\Sharename$\SQL\SQL105\ENT\x64\setup\sql_engine_core_inst_msi\then rerun this script to update installer cache and results
     The path on the line above must exist at the root location to resolve
     this problem with your msi/msp file not being found or corrupted,
     In some cases you may need to manually copy the missing file or manually
     replace the problem file overwriting it is exist:
      Copy "\\Servername\ShareName$\SQL\SQL105\ENT\x64\setup\sql_engine_core_inst_msi\sql_engine_core_inst.msi" C:\Windows\Installer\91a4f43.msi
It points to a location that doesn’t exist in the central server (servername) from where usually the installation media is present. The folder structures were re-arranged and the path mentioned (\\Servername\ShareName$\SQL\SQL105\ENT\x64\setup\sql_engine_core_inst_msi)
is no longer there.
Now from where do I copy this particular .MSI file? I've tried using search option but I'm unable to find it.
One more update is that I was successfully able to do the SP3 upgrade on another server which was SQL Server 2008R2 SP2 (No CU on it)
Hi Jayakrishna,
After your above steps, please put the SQL Server setup media on the same path
\\Servername\Sharename$\SQL, then run the VB script again and it will recreate the MSI file on the path C:\Windows\Installer with the name “91a4f43.msi“.
If the error still occurs, then you can manually restore the missing MSI file following the steps of Procedure 2 in this article:
http://support.microsoft.com/kb/969052 .
In addition, we recommend you use local copy of media to install SQL Server 2008 R2 SP3.
Thanks,
Lydia Zhang

Unable to connect BO XI3.1 SP3 on linux to sql server 2008

Similar Messages

Maybe you are looking for