Data Source error in Information Discovery

I created a new data source and when I try and look at a data explorer I am seeing the following error:
com.endeca.portal.data.DataSourceException: An error occurred while executing query: Could not send Message.
I am able to view the data through a Results table, but any other components seem to return an error. The data source is defined and looking at the correct port.

not answered but closing the thread.

Similar Messages

OSB: Cannot acquire data source error while using JCA DBAdapter in OSB

Hi All,
I've entered 'Cannot acquire data source' error while using JCA DBAdapter in OSB.
Error infor are as follows:
The invocation resulted in an error: Invoke JCA outbound service failed with application error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/DBAdapter1/RetrievePersonService [ RetrievePersonService_ptt::RetrievePersonServiceSelect(RetrievePersonServiceSelect_inputParameters,PersonTCollection) ] - WSIF JCA Execute of operation 'RetrievePersonServiceSelect' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by Exception [EclipseLink-7060] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Cannot acquire data source [jdbc/soademoDatabase].
Internal Exception: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.soademoDatabase'. Resolved 'jdbc'; remaining name 'soademoDatabase'.
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
JNDI Name for the Database pool: eis/DB/soademoDatabase
JNDI Name for the Data source: jdbc/soademoDatabase
I created a basic DBAdapter in JDeveloper, got the xsd file, wsdl file, .jca file and the topLink mapping file imported them into OSB project.
Then I used the .jca file to generate a business service, and tested, then the error occurs as described above.
Login info in RetrievePersonService-or-mappings.xml
<login xsi:type="database-login">
<platform-class>org.eclipse.persistence.platform.database.oracle.Oracle9Platform</platform-class>
<user-name></user-name>
<connection-url></connection-url>
</login>
jca file content are as follows:
<adapter-config name="RetrievePersonService" adapter="Database Adapter" wsdlLocation="RetrievePersonService.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<connection-factory location="eis/DB/soademoDatabase" UIConnectionName="Connection1" adapterRef=""/>
<endpoint-interaction portType="RetrievePersonService_ptt" operation="RetrievePersonServiceSelect">
<interaction-spec className="oracle.tip.adapter.db.DBReadInteractionSpec">
<property name="DescriptorName" value="RetrievePersonService.PersonT"/>
<property name="QueryName" value="RetrievePersonServiceSelect"/>
<property name="MappingsMetaDataURL" value="RetrievePersonService-or-mappings.xml"/>
<property name="ReturnSingleResultSet" value="false"/>
<property name="GetActiveUnitOfWork" value="false"/>
</interaction-spec>
</endpoint-interaction>
</adapter-config>
RetrievePersonService_db.wsdl are as follows:
<?xml version="1.0" encoding="UTF-8"?>
<WL5G3N0:definitions name="RetrievePersonService-concrete" targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/db/KnowledeMgmtSOAApplication/AdapterJDevProject/RetrievePersonService" xmlns:WL5G3N0="http://schemas.xmlsoap.org/wsdl/" xmlns:WL5G3N1="http://xmlns.oracle.com/pcbpel/adapter/db/KnowledeMgmtSOAApplication/AdapterJDevProject/RetrievePersonService" xmlns:WL5G3N2="http://schemas.xmlsoap.org/wsdl/soap/">
<WL5G3N0:import location="RetrievePersonService.wsdl" namespace="http://xmlns.oracle.com/pcbpel/adapter/db/KnowledeMgmtSOAApplication/AdapterJDevProject/RetrievePersonService"/>
<WL5G3N0:binding name="RetrievePersonService_ptt-binding" type="WL5G3N1:RetrievePersonService_ptt">
<WL5G3N2:binding style="document" transport="http://www.bea.com/transport/2007/05/jca"/>
<WL5G3N0:operation name="RetrievePersonServiceSelect">
<WL5G3N2:operation soapAction="RetrievePersonServiceSelect"/>
<WL5G3N0:input>
<WL5G3N2:body use="literal"/>
</WL5G3N0:input>
<WL5G3N0:output>
<WL5G3N2:body use="literal"/>
</WL5G3N0:output>
</WL5G3N0:operation>
</WL5G3N0:binding>
<WL5G3N0:service name="RetrievePersonService_ptt-bindingQSService">
<WL5G3N0:port binding="WL5G3N1:RetrievePersonService_ptt-binding" name="RetrievePersonService_ptt-bindingQSPort">
<WL5G3N2:address location="jca://eis/DB/soademoDatabase"/>
</WL5G3N0:port>
</WL5G3N0:service>
</WL5G3N0:definitions>
Any suggestion is appricated .
Thanks in advance!
Edited by: user11262117 on Jan 26, 2011 5:28 PM

Hi Anuj,
Thanks for your reply!
I found that the data source is registered on server soa_server1 as follows:
Binding Name: jdbc.soademoDatabase
Class: weblogic.jdbc.common.internal.RmiDataSource_1033_WLStub
Hash Code: 80328036
toString Results: ClusterableRemoteRef(8348400613458600489S:10.2.1.143:[8001,8001,-1,-1,-1,-1,-1]:base_domain:soa_server1 [8348400613458600489S:10.2.1.143:[8001,8001,-1,-1,-1,-1,-1]:base_domain:soa_server1/291])/291
Binding Name: jdbc.SOADataSource
Class: weblogic.jdbc.common.internal.RmiDataSource_1033_WLStub
Hash Code: 92966755
toString Results: ClusterableRemoteRef(8348400613458600489S:10.2.1.143:[8001,8001,-1,-1,-1,-1,-1]:base_domain:soa_server1 [8348400613458600489S:10.2.1.143:[8001,8001,-1,-1,-1,-1,-1]:base_domain:soa_server1/285])/285
I don't know how to determine which server the DBAdapter is targetted to.
But I found the following information:
Under Deoloyment->DBAdapter->Monitoring->Outbound Connection Pools
Outbound Connection Pool Server State Current Connections Created Connections
eis/DB/SOADemo AdminServer Running 1 1
eis/DB/SOADemo soa_server1 Running 1 1
eis/DB/soademoDatabase AdminServer Running 1 1
eis/DB/soademoDatabase soa_server1 Running 1 1
The DbAdapter is related to the following files:
C:\ Oracle\ Middleware\ home_11gR1\ Oracle_SOA1\ soa\ connectors\ DbAdapter. rar
C:\ Oracle\ Middleware\ home_11gR1\ Oracle_SOA1\ soa\ DBPlan\ Plan. xml
I unzipped DbAdapter.rar, opened weblogic-ra.xml and found that there's only one data source is registered:
<?xml version="1.0"?>
<weblogic-connector xmlns="http://www.bea.com/ns/weblogic/90">
<enable-global-access-to-classes>true</enable-global-access-to-classes>
<outbound-resource-adapter>
<default-connection-properties>
<pool-params>
<initial-capacity>1</initial-capacity>
<max-capacity>1000</max-capacity>
</pool-params>
<properties>
<property>
<name>usesNativeSequencing</name>
<value>true</value>
</property>
<property>
<name>sequencePreallocationSize</name>
<value>50</value>
</property>
<property>
<name>defaultNChar</name>
<value>false</value>
</property>
<property>
<name>usesBatchWriting</name>
<value>true</value>
</property>
<property>
<name>usesSkipLocking</name>
<value>true</value>
</property>
</properties>
          </default-connection-properties>
<connection-definition-group>
<connection-factory-interface>javax.resource.cci.ConnectionFactory</connection-factory-interface>
<connection-instance>
<jndi-name>eis/DB/SOADemo</jndi-name>
          <connection-properties>
               <properties>
               <property>
               <name>xADataSourceName</name>
               <value>jdbc/SOADataSource</value>
               </property>
               <property>
               <name>dataSourceName</name>
               <value></value>
               </property>
               <property>
               <name>platformClassName</name>
               <value>org.eclipse.persistence.platform.database.Oracle10Platform</value>
               </property>
               </properties>
          </connection-properties>
</connection-instance>
</connection-definition-group>
</outbound-resource-adapter>
</weblogic-connector>
Then I decided to use eis/DB/SOADemo for testing.
For JDeveloper project, after I deployed to weblogic server, it works fine.
But for OSB project referencing wsdl, jca and mapping file from JDeveloper project, still got the same error as follows:
BEA-380001: Invoke JCA outbound service failed with application error, exception:
com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/DBAdapterTest/DBReader [ DBReader_ptt::DBReaderSelect(DBReaderSelect_inputParameters,PersonTCollection) ] - WSIF JCA Execute of operation 'DBReaderSelect' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by Exception [EclipseLink-7060] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Cannot acquire data source [jdbc/SOADataSource].
Internal Exception: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.SOADataSource'. Resolved 'jdbc'; remaining name 'SOADataSource'.
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by Exception [EclipseLink-7060] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Cannot acquire data source [jdbc/SOADataSource].
Internal Exception: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.SOADataSource'. Resolved 'jdbc'; remaining name 'SOADataSource'.
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered not retriable, likely due to a modelling mistake.
It almost drive me crazy!!:-(
What's the purpose of 'weblogic-ra.xml' under the folder of 'C:\Oracle\Middleware\home_11gR1\Oracle_OSB1\lib\external\adapters\META-INF'?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

ODBC Data Source Error

I was having with Crystal communicating with one of my Access databases that had a list box. In Crystal it would take the list box, add and remove letters. It was suggested that I check with my IT department to see if there are any updates. Well they upgraded me from Crystal XI to Crystal XI R2. Things have gone downhill from there. First I couldnu2019t even open the program and they ended up reinstalling everything again. Now I can open Crystal, but all reports I previously created and new ones I try to create cannot make any connection through ODBC. My IT person and I have tried several things even installing a couple new drivers. My IT department does not provide technical support for software so now Iu2019m on my own to figure this out. If anyone can provide me with any assistance or any suggestions where to check I would greatly appreciate it.
My problem is any time I try to make an ODBC connection to either create or update a report I go through the steps and get an error at the connection information page and cannot go any further. This error happens with MS Access or MS Excel. The error is "Login Failed. Details: Cannot obtain error message from server. I have no logins or passwords.

In the Organizer workspace, do a
File > Catalog > Recover
command. That command "cleans up" your Elements catalog and often resolves ODBC data source error messages.

FIM connected Data Source Error

I am having issues with the DS-Export in FIM on SharePoint 2013.
I notice the DS_EXPORT operation is receiving 72 Export Errors... with the Error being 'permission-issue' when running a SharePoint profile synchronization. More specifically the Connected data source error in FIM is: "Insufficient access rights to
perform the operation."
I have granted the farm and synchronization account 'replicate directory changes' in both the domain and the configuration container (netbios and fqdn for domain are different).
What permissions could FIM be referring to?
- Rick

Is your domain running in Active Directory 2003 mode? If so, did you add the sync account to the Pre-Windows 2000 Compatible Access Group?
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Creating new Data Source Error - Database connection Failed

Successfully installed and configured 11.1.1.3.0. Planning and Essbase dev.
Went to Workspace > Administer > Classing Planning Administration > Manage Data Sources > Create Data Source.
Entered all info about the application database , etc. Getting error "The database connection failed" (I was able to connect with no problem during the install)
SQL server 2005 is on the same physical server.
The diagnostic tool shows database connection passed for planning. A new database was created for the new application.
The server event viewer shows these errors.
"Login failed for user 'xxx-hyperion'. The user is not associated with a trusted SQL Server connection."
Group Policy Error "The client-side extension could not apply computer policy settings for 'Default Domain Policy {xxx}' because it failed with error code '0x80070003 The system cannot find the path specified.' See trace file for more details. "
The Group Policy client-side extension Group Policy Services failed to execute. Please look for any errors reported earlier by that extension.
Any help is appreciated.

Datasource for the application.
I have created a sql db for this planning application (my datasource). See my first message for more details.
When you create a new planning application, you need to associate it with a data source. Since this is a new install, I don't have any data sources available yet.
So, "To create, edit or delete data sources, click Manage Data Source."
This page lets you validate your connection to the database and essbase server. My essbase server connection validates! The database connection does not validate after I enter all the relevant information.
SCREEN INFO BELOW
Fields displayed with an asterisk (*) are mandatory.
Data Source Name *:
Data Source Description:
Select Database Platform
Microsoft SQL Server
Application Database
Server * :
Port * :
Database *:
User *:
Password *:
Click "Validate Database Connection"
ERROR ---> Database connection failed.
So it does not let me create a data source for my new planning application, so I cannot create a new planning application.
Thanks in advance.

Cannot Change Data Source - Error The memory could not be "read"

We have some reports that were created under Crystal Reports version 10 using a Sybase 12.5 database as the datasource. We have since upgraded to Sybase 15 ASE and we are also attempting to upgrade these reports to Crystal Reports version 11.5. The reports will convert to version 11.5 but will not work because of the following error:
"Failed to load database information. Details: The database connector 'crdb_p2ssyb10.dll' could not be loaded"
From previous experience we know that Sybase 15 is only supported via ODBC with Crystal Report 11.5, so we tried to change the datasource to ODBC, but when we do that we get the following error:
The instruction at "0x0e864b11" referenced memory at "0x00000004". The memory could not be "read".
Do we have any options at this point besides competely re-creating the reports?

We are using CR 11.5 and trying to change the data source to ODBC. I can create a new report and use the same stored procedures as a datasource via ODBC with no issues. I only have an issue when trying to change the data source on these existing reports.

OBDC Data Source Error - Data source name not found and no default driver specified

Hello,
I get this error whenever I try to use the "Modify Microsoft Access Database" tab to update my
Access 2000 database after a conversion:
Unable to connect to target database.
java.sql.SQLException: [Microsoft] [ODBC Driver Manager]
Data source name not found and no default driver specified
Now, the weird thing is that when I log in as Administrator and go to the "Control Panel" there is
no "ODBC Data Sources" option to chose from. So I went to the "Microsoft ODBC Administrator"
from the "Configuration and Migration Tools" tab instead. I tried configuring "omwb_msaccess"
under the "User DSN" tab with both the name of my Access file, and the "small.mdb" file that was
in the omb directory. No go for either one. Whatever I try I still get the same pop-up box.
Question:
(1) What should I be putting for the "ODBC Data Source" when I try to Migrate my Access Database?
(2) Any other idea/configuration issue I might be missing that could do this? The process works up
to the Access Update point, and I configured the repository correctly.
Thanks
Aaron - [email protected]

Nope, I'd already tried both of those things. I checked again, but no go.
I think the problem may be that I'm not entering the right value in the
"ODBC Data Source" field on the Migration Workbench "Modify Microsoft
Access Database" form - the same one where you enter a "Username" and
"Password" for the conversion. What should I be entering here? What is
the standard filename?
The log files aren't very informative to me. Here is the odbcconf.log:
==============
ODBCConf called with arguments: '/S /Lv odbcconf.log /F C:\WINNT\System32\mdaccore.rsp'
Data Struct:
     Reboot First : 0
     Use Response File : 1
     Response File : 'C:\WINNT\System32\mdaccore.rsp'
     Erase Response File: 0
     Silent : 1
     Continue on Error : 0
     Log Mode : 2
     Log File : 'odbcconf.log'
     Actions:
          8, '(null)', '(null)', ''
          6, 'MS Code Page Translator|Translator=MSCPXL32.dll||', '(null)', '"MS Code Page Translator|Translator=MSCPXL32.dll||"'
          5, 'Microsoft ODBC for Oracle|Driver=msorcl32.dll|Setup=msorcl32.dll||', '(null)', '"Microsoft ODBC for Oracle|Driver=msorcl32.dll|Setup=msorcl32.dll||"'
          1, 'Microsoft ODBC for Oracle', 'CPTimeout=60', '"Microsoft ODBC for Oracle" "CPTimeout=60"'
          17, 'simpdata.tlb', '(null)', '"simpdata.tlb"'
EXECUTING ACTIONS
Executing Action: INSTALLDRVRMGR
          arg1: '(null)'
          arg2: '(null)'
          args: ''
Install Driver Manager succeeded
          Return HR: 0x0
Executing Action: INSTALLTRANSLATOR
          arg1: 'MS Code Page Translator|Translator=MSCPXL32.dll||'
          arg2: '(null)'
          args: '"MS Code Page Translator|Translator=MSCPXL32.dll||"'
INSTALLTRANSLATOR SQLInstallTranslatorEx succeeded
          Return HR: 0x0
Executing Action: INSTALLDRIVER
          arg1: 'Microsoft ODBC for Oracle|Driver=msorcl32.dll|Setup=msorcl32.dll||'
          arg2: '(null)'
          args: '"Microsoft ODBC for Oracle|Driver=msorcl32.dll|Setup=msorcl32.dll||"'
INSTALLDRIVER SQLInstallDriverEx succeeded
          Return HR: 0x0
Executing Action: CONFIGDRIVER
          arg1: 'Microsoft ODBC for Oracle'
          arg2: 'CPTimeout=60'
          args: '"Microsoft ODBC for Oracle" "CPTimeout=60"'
CONFIGDRIVER SQLConfigDriver succeeded
          Return HR: 0x0
Executing Action: REGTYPELIB
          arg1: 'simpdata.tlb'
          arg2: '(null)'
          args: '"simpdata.tlb"'
          Return HR: 0x0
===========
Here is a snippet from the error.log:
==========
** Oracle Migration Workbench
** Release 9.2.0.1.0 Production
** ( Build 20020308 )
** ORACLE_HOME: c:\
** user language: en
** user region: US
** user timezone: PST
** file encoding: Cp1252
** java version: 1.1.8.16
** java vendor: Oracle Corporation
** o.s. arch: x86
** o.s. name: Windows NT
** o.s. version: 5.0
** Classpath:
c:\\Omwb\olite\Oljdk11.jar;c:\\Omwb\olite\Olite40.jar;C:\Program Files\Oracle\jre\1.1.8\lib\rt.jar;C:\Program Files\Oracle\jre\1.1.8\lib\i18n.jar;c:\\Omwb\jlib;c:\\Omwb\jlib\Omwb.jar;c:\\Omwb\jlib\oembase-9_2_0.jar;c:\\Omwb\plugins\SQLServer6.jar;c:\\Omwb\plugins\SQLServer7.jar;c:\\Omwb\plugins\SQLServer2K.jar;c:\\Omwb\plugins\Sybase11.jar;c:\\Omwb\plugins\Sybase12.jar;c:\\Omwb\plugins\MSAccess.jar;c:\\Omwb\plugins\MySQL.jar;c:\\Omwb\drivers\mm.mysql.jdbc-1.2a;c:\\Omwb\plugins\Informix7.jar;c:\\Omwb\drivers\ifxjdbc.jar;c:\\Omwb\plugins\db2400v4r5.jar;c:\\Omwb\drivers\jt400.jar;c:\\lib\xmlparserv2.jar;c:\\rdbms\jlib\xsu111.jar;c:\\jdbc\lib\classes111.zip;c:\\lib\vbjorb.jar;c:\\jlib\netcfg.jar;c:\\jlib\ewt3.jar;c:\\jlib\ewtcompat-3_3_15.jar;c:\\jlib\share.jar;c:\\jlib\help3.jar;c:\\jlib\oracle_ice5.jar;c:\\jlib\kodiak.jar
** Started : Tue Jul 23 12:13:42 PDT 2002
** Workbench Repository : Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
** The following plugins are installed:
** Microsoft Access Release 9.2.0.1.0 Production
** Active Plugin : MSAccess
** Shutdown : Tue Jul 23 12:14:59 PDT 2002
I appreciate any assistance you could render me.
Thanks - Aaron

Cross Domain Data Source Error in SSRS 2008

We have our data warehouse server on a different Windows domain (Domain ABC) to the domain where our end user tools such as SSRS and SSAS sit (DOMAIN 123). Historically we've used SQL server mixed mode authentication to get around any cross domain
authentication issues but to tighten up security we are trying to switch to Windows only. However, I'm unable to my development instance of SSRS to connect to a datasource using credentials from a different domain.
I created a copy of the live data source with the same settings except for the credentials. Here I selected Windows credentials (without impersonation ticked) and put in the username with the format DOMAINABC\DomainAccount with a domain account from
the same domain as our DWH server. However, none of the reports I tested can conect and throw the error below. Please can anyone give me some pointers on things to check? My google research has drawn a blank so far!
An error occurred during client rendering.
An error has occurred during report processing.
Cannot impersonate user for data source 'DWH'.
Log on failed.
Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)

From your inital post, it sounded like you wanted to login to the data source with a remote domain user (123 in your example). Glad to see that's not the case!
When you tested the credentials with SSMS were you on the remote domain?
It looks to me like the impersonation is implicit: https://msdn.microsoft.com/en-us/library/ms160330.aspx
Theres a couple of notes at the top of that page about remote access being enabled, and the ports that should be open too.
Theres a bunch of potentially useful information about what your connection string should look like here too:
https://msdn.microsoft.com/en-us/library/ms156450.aspx

Failed to fetch pluggable data source error

I'm getting this error when creating a report that is connecting to a DB2 table using jdbc. Report builder seems to connect to the database fine, however when I attempt to compile/run the report I get the following error -
'REP-4102: Failed to fetch pluggable data source.
java.lang.AbstractMethodError: COM/ibm/db2/jdbc/app/DB2ResultSet.getStatement'
I'm using the following in my jdbcpds.conf on my local machine.
<driver name = "ibm-db2"
subProtocol = "db2"
connectString = "subProtocol:databaseName"
class = "COM.ibm.db2.jdbc.app.DB2Driver"
connection = "oracle.reports.plugin.datasource.jdbcpds.JDBCConnectionHandling"
loginTimeout = "0">
</driver>
Has anyone experienced this issue or has some insight as to what I need to do to resolve this?
TIA
Brian

Dear Oracle Reports Team,
Can you please help me out ???
Need your help in this regard urgently.
Best Regards,
Ramakrishnan L
Dear Friends,
I am encountering the following the error while running the reports.
REP-4102: Failed to fetch pluggable data source.
java.lang.NumberFormatException: 75,000000
I am using an Express Query in this case.
The same report runs perfectly when connected to the NT server that has the reports server,Http server and the rdf file.The db that the reports uses is on the SOLARIS server.
But when I use the reports server,http server and the rdf file avaiable to me on the SOLARIS server with the db also now on the same machine it does not run and gives the error.
What could be the problem ?
Just to add more clarity below is the URL which I use to display the report
NT URL(This works perfectly)
http://sa560:7778/reports/rwservlet?server=rep_sa560&report=c:\DWHReports\Man_Days_Spent.rdf&express_server="server=ora_ro_tcp:172.20.128.199/sl=-2/st=1/ct=0/st=1/"&destype=cache&desformat=htmlcss&OESHOST=172.20.128.199&SUSR_NAME='oraexp'&PASSWORD='test'
SOLARIS URL(This does not work and gives the error)
http://172.20.128.199:7778/reports/rwservlet?server=rep_gosisvr&report=Man_Days_Spent.rdf&express_server="server=ora_ro_tcp:172.20.128.199/sl=-2/st=1/ct=0/st=1/"&destype=cache&desformat=htmlcss&OESHOST=172.20.128.199&USR_NAME='oraexp'&PASSWORD='test'
Regds,
Ramakrishnan L

Data Source Error in infopackage level

HI experts,
Please guide me to resolving this issues.
When I am trying to load CSV dta through infopackage and when i clicked preview button , it is throwing an error.
Error : Data source DS_PROFIT not available in source system of Avtive Version A.
This data source created by me.
Please help me.
Regards,
subhendu

pls activate your data source first then try to preview the data...........
Edited by: JAIGUPTA on Jan 12, 2012 10:16 PM

Data Source errors with OLE DB for Oracle

We tried to install Oracle 10g 10.2.0.1.0 x64 Client for Windows on:
Microsoft Windows Server 2003 Enterprise x64 Edition Service Pack 1 (64 bit)
SqlServer 2000 Enterprise Edition SP4 (32-bit)
When trying to create a Data Source (from a UDL file or Analysis Services) we get the following errors:
"Provider is no longer available. Ensure that the Provider is installed properly"
"Test connection failed because not all properties can be set. Window Handle (BAD VALUE)"
The Oracle Client install completed "Successfully" and ODBC connections work fine. Also, tnsping works fine. Just the OLE DB connections are failing.
Any help greatly appreciated.
Thanks,
J

Maybe you can try the below method to configure the oracle provider for OLEDB.
1.Open SQL Server Management Studio
Click on the + to expand the tree for the <Machine Name> SQL Server. Where <Machine Name> is the name of the machine where Microsoft SQL Server is installed on.
The first level of the tree is called <Machine Name> SQL Server,
The second level of the tree is called Linked Servers,
The third level of the tree is called Providers.
a list of Providers are shown.
Right click on the Oracle Provider for OLEDB and select Properties.
Check the check boxes for "Dynamic Parameters" and "Allow InProcess".

Can no longer upload photos - ODBC data source error [was: Photoshop Album Starter Edition 3.2]

Hi everyone! Thanks in advance for any help somone can provide!
I can no longer upload photos, which sucks. I get an error message thats says : The ODBC data source returned the following error: "[Microsoft][ODBC Microsoft Access Driver] The search key was not found in any record."
I understand adobe is no longer issuing updates for this program, but is there anything I can do to salvage it? Oh I hope there is. Thanks again!

[Moved from Photoshop forum to Photoshop Album Starter Edition forum]

Initialize Data Source errors

Hello,
We are running EP6 SP2 Patch34. We have a custom DataSource xml file so that we can connect to 2 different MSAD Domains.
This morning the account we use in one of the domains was set to expired so we were getting the following errors in the console logs
<i><b>Warning data source is not initialized</b></i>
We have since fixed the issue with the ID, but we are still getting these errors in the logs.
Does anyone know how to Initialize the datasource again without restarting the portal?
Thanks,
Keith
Message was edited by: Keith Crossett

Thank you for reminding me what I already knew but in my haste to post out a reply I had forgotten to consider looking at the provider properties.
Today I did and the linked database still failed. The though occurred to me a little later to delete and recreate the linked db and bingo I had a working linked database to Oracle. Now I have three of them and the developer should be working with them now.
This is the first time I ever had to change a provider property to get the provider to work. I would have thought that when the Oracle client install process registered the OLE provider with SQL Server 2005 it would be set with the proper defaults to work.
Thanks again to everyone
-- Mark D Powell --

DATA Source error JNDI at WLS

Hi everyone.
I have a problem. I created a data source (REMATES_Desarrollo) at agent and deployed at WLS but from Topology when I test that data source with the agent deplyed at WLS give a error, the Data Source at WLS and Conection at Topology are the same even in the name (REMATES_Desarrollo). Somebody knows how can I fix the next error. Thank you so much.
oracle.odi.core.exception.OdiRuntimeException: oracle.odi.core.exception.OdiRuntimeException: Failed to lookup dataSource from JNDI for name {java:comp/env/REMATES_Desarrollo}
     at oracle.odi.core.datasource.provider.AbstractDataSourceProvider.configure(AbstractDataSourceProvider.java:107)
     at oracle.odi.core.DataSourceManager$LoginTimeoutDataSourceProviderProxy.configure(DataSourceManager.java:303)
     at oracle.odi.core.DataSourceManager.createAndConfigureDataSourceProvider(DataSourceManager.java:226)
     at oracle.odi.core.DataSourceManager.access$0(DataSourceManager.java:206)
     at oracle.odi.core.DataSourceManager$1.create(DataSourceManager.java:76)
     at org.springframework.util.CachingMapDecorator.get(CachingMapDecorator.java:253)
     at java.util.Collections$SynchronizedMap.get(Collections.java:1979)
     at oracle.odi.core.DataSourceManager.getDataSource(DataSourceManager.java:155)
     at oracle.odi.core.OdiInstance.lookupDataSource(OdiInstance.java:788)
     at oracle.odi.core.datasource.dwgobject.support.DwgConnectConnectionCreatorImpl.createDwgConnectConnection(DwgConnectConnectionCreatorImpl.java:82)
     at com.sunopsis.dwg.dbobj.SnpSession.createDwgConnectConnection(SnpSession.java:3567)
     at com.sunopsis.dwg.dbobj.SnpSessTask.getDefaultDwgConnectConnection(SnpSessTask.java:513)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.getExecutor(SnpSessTaskSql.java:2953)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2894)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2609)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:540)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:453)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1740)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1596)
     at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$2.doAction(StartScenRequestProcessor.java:582)
     at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:214)
     at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:513)
     at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:1070)
     at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:123)
     at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$1.run(DefaultAgentTaskExecutor.java:50)
     at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:50)
     at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor.executeAgentTask(DefaultAgentTaskExecutor.java:41)
     at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.doExecuteAgentTask(TaskExecutorAgentRequestProcessor.java:93)
     at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.process(TaskExecutorAgentRequestProcessor.java:83)
     at oracle.odi.runtime.agent.support.DefaultRuntimeAgent.execute(DefaultRuntimeAgent.java:79)
     at oracle.odi.pubws.jaxws.service.OdiInvokeServiceImpl.doInvokeStartScen(OdiInvokeServiceImpl.java:353)
     at oracle.odi.pubws.jaxws.service.OdiInvokeServiceImpl.invokeStartScen(OdiInvokeServiceImpl.java:312)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:92)
     at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:74)
     at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:151)
     at com.sun.xml.ws.server.sei.EndpointMethodHandlerImpl.invoke(EndpointMethodHandlerImpl.java:268)
     at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:100)
     at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:866)
     at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:815)
     at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:778)
     at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:680)
     at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:403)
     at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:532)
     at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:253)
     at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:141)
     at weblogic.wsee.jaxws.WLSServletAdapter.handle(WLSServletAdapter.java:172)
     at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:708)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.wsee.util.ServerSecurityHelper.authenticatedInvoke(ServerSecurityHelper.java:103)
     at weblogic.wsee.jaxws.HttpServletAdapter$3.run(HttpServletAdapter.java:311)
     at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:337)
     at weblogic.wsee.jaxws.JAXWSServlet.doRequest(JAXWSServlet.java:95)
     at weblogic.servlet.http.AbstractAsyncServlet.service(AbstractAsyncServlet.java:99)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: oracle.odi.core.exception.OdiRuntimeException: Failed to lookup dataSource from JNDI for name {java:comp/env/REMATES_Desarrollo}
     at oracle.odi.core.datasource.provider.JndiDataSourceProvider.doCreateDataSource(JndiDataSourceProvider.java:58)
     at oracle.odi.core.datasource.provider.AbstractDataSourceProvider.configure(AbstractDataSourceProvider.java:98)
     ... 81 more
Caused by: javax.naming.NameNotFoundException: While trying to look up comp/env/REMATES_Desarrollo in /app/webapp/oraclediagent/43653673.; remaining name 'comp/env/REMATES_Desarrollo'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
     at weblogic.jndi.internal.ApplicationNamingNode.lookup(ApplicationNamingNode.java:144)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
     at weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWrapper.java:45)
     at weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:130)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at oracle.odi.core.datasource.provider.JndiDataSourceProvider.doCreateDataSource(JndiDataSourceProvider.java:46)
     at oracle.odi.core.datasource.provider.AbstractDataSourceProvider.configure(AbstractDataSourceProvider.java:98)
     at oracle.odi.core.DataSourceManager$LoginTimeoutDataSourceProviderProxy.configure(DataSourceManager.java:303)
     at oracle.odi.core.DataSourceManager.createAndConfigureDataSourceProvider(DataSourceManager.java:226)
     at oracle.odi.core.DataSourceManager.access$0(DataSourceManager.java:206)
     at oracle.odi.core.DataSourceManager$1.create(DataSourceManager.java:76)
     at org.springframework.util.CachingMapDecorator.get(CachingMapDecorator.java:253)
     at java.util.Collections$SynchronizedMap.get(Collections.java:1979)
     at oracle.odi.core.DataSourceManager.getDataSource(DataSourceManager.java:155)
     at oracle.odi.core.OdiInstance.lookupDataSource(OdiInstance.java:788)
     at oracle.odi.core.datasource.dwgobject.support.DwgConnectConnectionCreatorImpl.createDwgConnectConnection(DwgConnectConnectionCreatorImpl.java:82)
     at com.sunopsis.dwg.dbobj.SnpSession.createDwgConnectConnection(SnpSession.java:3567)
     at com.sunopsis.dwg.dbobj.SnpSessTask.getDefaultDwgConnectConnection(SnpSessTask.java:513)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.getExecutor(SnpSessTaskSql.java:2953)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2894)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2609)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:537)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:453)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1740)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1595)
     at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$2.doAction(StartScenRequestProcessor.java:580)
     at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:214)
     at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:513)
     at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:1070)
     at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:123)
     at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$1.run(DefaultAgentTaskExecutor.java:49)
     at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
     at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor.executeAgentTask(DefaultAgentTaskExecutor.java:41)
     at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.doExecuteAgentTask(TaskExecutorAgentRequestProcessor.java:92)
     at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.process(TaskExecutorAgentRequestProcessor.java:83)
     at oracle.odi.runtime.agent.support.DefaultRuntimeAgent.execute(DefaultRuntimeAgent.java:79)
     at oracle.odi.pubws.jaxws.service.OdiInvokeServiceImpl.doInvokeStartScen(OdiInvokeServiceImpl.java:353)
     at oracle.odi.pubws.jaxws.service.OdiInvokeServiceImpl.invokeStartScen(OdiInvokeServiceImpl.java:312)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:92)
     at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:74)
     at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:151)
     at com.sun.xml.ws.server.sei.EndpointMethodHandlerImpl.invoke(EndpointMethodHandlerImpl.java:268)
     at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:100)
     at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:866)
     at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:815)
     at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:778)
     at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:680)
     at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:403)
     at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:532)
     at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:253)
     at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:140)
     at weblogic.wsee.jaxws.WLSServletAdapter.handle(WLSServletAdapter.java:171)
     at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:708)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.wsee.util.ServerSecurityHelper.authenticatedInvoke(ServerSecurityHelper.java:103)
     at weblogic.wsee.jaxws.HttpServletAdapter$3.run(HttpServletAdapter.java:311)
     at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:336)
     at weblogic.wsee.jaxws.JAXWSServlet.doRequest(JAXWSServlet.java:95)
     at weblogic.servlet.http.AbstractAsyncServlet.service(AbstractAsyncServlet.java:99)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     ... 9 more
Edited by: Ariel Lopez on 7/05/2013 02:35 PM

Hi Ariel,
Please make sure to uncheck the "JNDI Standard" check box while generating the template for the data source.
Please refer to Support note [ID 1300550.1]
"While generating the WLS Template please be aware that the "JNDI Standard" box is required to be unchecked in the ODI WLS Template Generation Wizard > "DataSources" step, or WLS will use the standard naming conventions, which automatically prefix the dataSource names by "comp/env", resulting in issues when starting the J2EE Agent."
Note [ID 1362119.1] also talks about the same.
Thanks,

Data source error in Tomcat

I have encountered a puzzle question with Tomcat,I setup a DSN with Microsoft OLE DB Provider for ODBC Drivers,when I start tomcat with C:\Tomcat5.5\bin\tomcat5w.exe,I get a error:
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
Then I don't open the page "http://localhost:8080"
But when I start tomcat with C:\Tomcat5.5\bin\tomcat5.exe,I can start tomcat and I don't get above error,and I can visit "http://localhost:8080"
Why I can't start Tomcat with tomcat5w.exe and can start Tomcat with tomcat5.exe?
I am puzzled with this question for a several days! I don't know how to solve it. Any body meet with my question?
Any idea will be appreciated!
Thanks in advance

I use Microsoft Access Database,is it a bug of Tomcat?

Data Source error in Information Discovery

Similar Messages

Maybe you are looking for