App not versioned error in JDeveloper - ADF with SQL Server 2005

Hello All,
I am developing a sample ADF application. Database is MS SQL Server 2005 SP2. I get below error message. I am trying in parallel to google it... However trying here if any encountered such an issue and had resolved it.
Thanks in advance for your time.
Cheers,
Vagic.
[02:06:19 PM] Deploying Application...
<Feb 23, 2010 2:06:20 PM PST> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application ExmReports is not versioned.>
<Feb 23, 2010 2:06:20 PM PST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1266962779600' for task '0'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
     at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:290)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)

You might need to add the JDBC jar file for SQL Server to the classpath of the integrated WebLogic. See minute 8 here: http://download.oracle.com/otn_hosted_doc/jdeveloper/11gdemos/NBtoJDevProject/NBtoJDevProject.html

Similar Messages

Jdeveloper connecting with SQL Server Express

Hi i am trying to connect jdeveloper with SQL Server Express. At the moment i am getting a TCP/IP connection to the host error message.
My connection string is as follows:
Class.forName("com.micorosoft.sqlserver.jdbc.SQLServerDriver")
Connection conn = DriverManager.getConnection("jdbc:sqlserver://mustang/sqlexpress; database = matt1; Uid = matt; Pwd = matt1")
Can someone please help me!

Enable TCP/IP protocol. Select Microsoft SQL Server 2005>Configuration Tools>SQL Server Configuration Manager. In the SQL Server Configuration Manager select the node SQL Server 2005 Network Configuration>Protocols for SQLEXPRESS. Right-click on the TCP/IP node and select Enable. Restart the SQL Server (SQLEXPRESS) service. In Adminstrative Tools>Services, right-click on the SQL Server (SQLEXPRESS) service and select Restart.
To configure a JDBC connection with SQL Server 2005 Express, add SQL Server 2005 JDBC driver JAR file <Microsoft SQL Server 2005 JDBC Driver>/sqljdbc_1.0/enu/sqljdbc.jar to classpath. <Microsoft SQL Server 2005 JDBC Driver> is the directory in which SQL Server 2005 JDBC Driver zip file is installed.
Driver class for SQL Server 2005 database is com.microsoft.sqlserver.jdbc.SQLServerDriver. Connection URL for the default SQL Server 2005 database is jdbc:sqlserver://localhost:<port>.
In the connection URL, <port> is obtained from the SQL Server configuration Manager. When the SQL Server 2005 SQLEXPRESS is restarted the port number changes.
To obtain the <port> in the SQL Server Configuration Manager, select the node SQL Server 2005 Network Configuration>Protocols for SQLEXPRESS. Right-click on TCP/IP node and select Properties. Select the IP Addresses tab. In IP ALL, the TCP Dynamic Ports specifies the <port> value. The connection URL format for another database name is shown in following listing.

Error While Installing IDES ECC6 with SQL Server 2005

Dear Experts,
I found an error while installing IDES ECC6 with SQL Server 2005. The error is raising at the stage of 17 of 24 processing the procedure of 195 of 197 (sap_z_set_permissions).
I have tried several times by configuring different type of activites but still i am facing the same problem at the same stage. Please help me in thig regard.
I herewith pasted hereunder log files information
Regards,
B.Sudharsan
ERROR 2008-01-17 18:38:47
FCO-00011 The step ExeProcs with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_MSS|ind|ind|ind|ind|2|0|MssProcs|ind|ind|ind|ind|1|0|ExeProcs was executed with status ERROR .
INFO 2008-01-17 18:40:05
An error occured and the user decide to stop.\n Current step "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_MSS|ind|ind|ind|ind|2|0|MssProcs|ind|ind|ind|ind|1|0|ExeProcs".
ERROR 2008-01-17 18:38:47
MDB-05053 Errors when executing sql command: <p nr="0"/> If this message is displayed as a warning - it can be ignored. If this is an error - call your SAP support.

Sudarshan,
Occasionally, mid-way through the upgrade, DB permissions to users might change. Check to see, if the users SAP<SID>, OPS$ users have the DBA privilege. Re-assign the role and try continuing with the upgrade.

ODI 10.1.3.5 with SQL Server 2005

Good afternoon,
We recently installed 10.1.3.5, in a Windows environment with SQL Server 2005 and Hyperion Essbase/Planning/HFM 11.1.1. We were following John Goodwin's infamous blog (thanks, John!), but ran into a number of snags.
For instance, when we set-up interfaces with flat files as the source, loading metadata either to Planning or Essbase, ODI errors out when:
1) our header name in the flat file has spaces (using double quotes didn't work)
2) our header name in the flat file is different than the reverse property name from Essbase/Planning.
Also, we're now seeing an issue in our Flat file to Essbase metadata interface where the SQL used in the IKM seems to be incorrect. Below is the error message we're receiving:
"org.apache.bsf.BSFException: exception from Jython:
Traceback (innermost last):
File "<string>", line 20, in ?
com.microsoft.sqlserver.jdbc.SQLServerException: An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements,
look for empty alias names. Aliases defined as "" or [] are not allowed. Add a name or single space as the alias name."
We are thinking that the culprit may be either the wrong .jar or .jre we're using with SQL Server 2005, as there seem to be inherent issues with the SQL generated in the LKM and IKM. Our questions to you:
1. What sqljdbc.jar driver version are you using?
2. What .jre version are you using?
3. What environment does the above work correctly in? (perhaps an earlier version of ODI against an earlier version of Hyperion?)
FYI - We have tried sqljdbc 1.0 and 2.0, with .jre 1.6.0_10.
Thanks in advance!
-O
Edited by: Alapat on Jan 22, 2009 8:04 AM

Thank you very much for responding!
After a 2 week battle, we are now finally coming to a close on our issues (although we cannot say for sure what all of the causes were).
Here is what we discovered about our questions, through other threads:
1. John Goodwin was using JRE 1.6.x, so we ruled that out as a culprit.
2. Others are using SQL Server 2005 just fine with ODI, so we ruled this out too. We chose to keep the sqljdbc 2.0 driver.
Here are some issues we did uncover during our investigation:
1. We were having issues with our agent, specifically regarding the HFM technology. We created a new one, added a few extra parameters, compiled the agent, and are now back up and running. We realized the problem when we switched to "Local (No Agent)" and saw that we were not having as many issues.
2. We went into the physical agent and pressed "Update Scheduling". We do not know if this had any effect, but we suddenly noticed that our flat file header issues were resolved.
3. The Essbase issue was due to a configuration error with our Hyperion Essbase physical technology. We went into that technology and changed a setting on the "Languages" tab, called "Object Delimiter". It had double-quotes in it - we removed that parameter and instantly saw a change in the SQL being executed.
4. Some of the mappings in our interfaces needed to be executed on different environments. i.e. - We needed to switch to "staging" when the flat file header was different than the target column name. Newbie mistake - we thought ODI had built-in intelligence to choose correctly for us.
5. When doing a reverse on Essbase models, we noticed that the Essbase columns would populate with an "Undefined" datatype, instead of the expected CHAR. We have to manually define all column datatypes after every Essbase reverse now. Must be a bug.
6. We also noticed when doing a flat file reverse that all columns auto-populate with datatype STRING, length 50. We have to manually personalize that option for different Hyperion applications, based on need. i.e. - some require numeric datatypes, or smaller/larger lengths. This was obviously a newbie error. :)
Thank you for your tip on the MS SS2005 JDBC drivers - we will look into your other options - IMHO, JTDS, etc.
-O

EPM 11 Configuration with SQL Server 2005

Hello,
I am having a terrible time trying to get the EPM System Configurer to communicate with SQL Server 2005 Evalution. I keep getting the error "Cannot open database "server" requested by the login. The login failed." I have the windows firewall turned off. The protocol TCPIP is turned on and other protocal are turned off. Any suggestions. Thanks in advance.

As John mentioned it is supposed to be supported in a future release. That version would be 11.2 -- there will be a version coming out before 11.2 and it will not support 2008.
Regards,
John A. Booth
http://www.metavero.com

Crystal Report 8.5 with SQL SERVER 2005 problems

Post Author: AREVA
CA Forum: Data Connectivity and SQL
Hi All !We have some problems with Crystal Reports version 8.5 with SQL Server 2005: 1) When we want to generate a report (using data in SQL Server 2005) we have a popup message error : "impossible to loaded pdssql.dll".2) If we want to use SQL Server 2005, which Crystal Reports version we must used ? Is there any restrictions with this connectivity with 8.5 version ?Please, let me known, all informations about SQL Server 2005 and Crystal Report 8.5.Thanks for all !Best regards Anthony

Hello Kamlesh,
There is no expectation that the ActiveX viewer (RDC?) from CR8.5 will work in any version of Visual Studio .NET. There is also no expectation that the ActiveX viewer from CR8.5 will work on a machine with a 64 bit operating system.
You're using VS2008. You should migrate to the bundled edition of CR for VS2008 (v10.5), the ReportDocument object, and the .NET Windows form viewer or Web form viewer.
Sincerely,
Dan Kelleher

Am failing to install Java IDM in a Windows XP machine with SQL Server 2005

Hi,
I am new to Java IDM . I had downloaded IDM 7.0 and trying to install. But i am failing to install Java IDM in a Windows XP machine with SQL Server 2005.
I used .,
JDK 1.5
Tomcat 6.0
Microsoft SQL Server 2005
Microsoft SQL Server 2005 JDBC driver
I got the following error while trying to connect the waveset database with Repository type as SQL Server 2005(JDBC Driver)
com.waveset.util.ConfigurationError:
==> com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'waveset'. The user is not associated with a trusted SQL Server connection.
what name i can specify in JDBC ... is there any need to create DSN for that ...........
The Parameters that I have given for connection are:
URL: jdbc:sqlserver :1433;DatabaseName=
JDBC Driver: com.microsoft.sqlserver.jdbc.SQLServerDriver
Connect as User:
Connect Password:

Do you have your SQL server set to Windows Authentication mode only?
You should change it to allow mixed authentication. You can do this in SQL Server Management Studio under Server Properties -> Security.

Open (.sdf) file with SQL server 2005 Management Studio

In VS2005, I have created a SQL Mobile database, (.sdf).
Copied that (.sdf) file to Desktop, and when I try to open with SQL Server 2005 management studio, its showing error "make sure the application for the file type (.sdf) is installed."
How can I open this file with SQL server?
Regards
Abinash

You must install SP2 if using Management Studio Express (http://www.microsoft.com/downloads/details.aspx?familyid=6053C6F8-82C8-479C-B25B-9ACA13141C9E&displaylang=en)Erik Ejlskov Jensen, MCTS: WM App, MCITP: SQL 2008 Dev - http://erikej.blogspot.com
Please mark as answer, if this was it.

How can I connect NetBeans 6.1 with SQL Server 2005?

Hello guys...
how can i connect NetBeans 6.1 with SQL Server 2005?
there is no SQL Server in Server list when we create a new Web Project and choose Server.
I'm new to NetBeans and this is my first time of posting.
If has some errors and unwanted disturbing,pls understand me. Thanks.
(If you have references or some snippets, i'll be glad if u can share.)
scsfdev

The JDBC-ODBC bridge wasn't recognizing any of the primary keys I had set up in SQL Server. After lots of head banging, here's the solution I came up with:
1. Download the appropriate driver. SQL Server 2000 requires the SQL Server 2000 JDBC driver (http://www.microsoft.com/downloads/details.aspx?FamilyId=07287B11-0502-461A-B138-2AA54BFDC03A&displaylang=en).
SQL Server 2005 download: (http://www.microsoft.com/downloads/details.aspx?familyid=C47053EB-3B64-4794-950D-81E1EC91C1BA&displaylang=en)
3. After installing, right-click on "Libraries" in your project, and choose "Add Library...". Next, give it a name (i.e. SQLServer2000), and select "Class Libraries".
4. On the next screen, find the JAR files (should be in C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\), and add them under the "Classpath" tab. It will now be available under "Libraries" for future projects.
5. You can now create a connection to a specific database under the "Services" tab (next to "Projects" and "Files" in the top left of the screen). Select "Microsoft Sql Server 2000 (Microsoft Driver)" and format the "Database URL" like this:
jdbc:microsoft:sqlserver//YOURSERVER:1433;DatabaseName=YOURDATABASE
1433 is the default port, though your DBA may have changed it.
I posted a simpler version of this on the NetBeans.org FAQ page - they had the following title with no content on the answer page:
"Cannot Select Tables From MsSql 2000 Because It Says No Primary Key Next To Each Table But The Tables DO Have A Primary Key. What Do I Do?"

Integrate Oracle IDM with Sql Server 2005

Hi Guys,
We maintain the employees information in Oracle IDM and we want to integrate Oracle IDM with Sql server 2005.
how we can this.

The DB connector?
The 9.0.1.4 version supports SQL server 2005.
The latest version of the GTC db connector might also work.
Best regards
/Martin

TopLink with SQL Server 2005

Could someone help answer this question:
Has TopLink 10.1.3.x been certified to support SQL Server 2005?
I appreciate your information.
Haiwei

It is certified on SQL Server 2000.
I know some customers are using it with SQL Server 2005, though.

Breeze with SQL Server 2005

Hi,
it seems that MS SQL Server 2000 isnt available anymore - SQL
Server 2005 is out.
Runs Breeze with SQL Server 2005 also?
thanks

Hi Dav:
SQL Server 2005 won't be officially supported until the next
release
of Breeze, which is expected to ship sometime in the fall.
Hope this helps!
Jeff Von Ward
Breeze Product Support Manager
Adobe Systems, Inc.
On Sat, 1 Jul 2006 12:34:37 +0000 (UTC), "DavHo"
<[email protected]> wrote:
>Hi,
>
>it seems that MS SQL Server 2000 isnt available anymore -
SQL Server 2005 is out.
>Runs Breeze with SQL Server 2005 also?
>
>thanks

Error while Installing WAS with SQL server

Hi all,
   I am trying to install WAS with SQL server as Database. I am getting error at "Register SDM targets" section. We have given SQL server authentication mode to install WAS.
Following is the error Log....
Exception: [DataDirect][SQLServer JDBC Driver][SQLServer]Cannot open database requested in login 'HCL'. Login fails.
     at com.ddtek.jdbc.base.BaseExceptions.createException(Unknown Source)
     at com.ddtek.jdbc.base.BaseExceptions.getException(Unknown Source)
     at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
     at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
     at com.ddtek.jdbc.sqlserver.tds.TDSLoginRequest.processReplyToken(Unknown Source)
     at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
     at com.ddtek.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
     at com.ddtek.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
     at com.ddtek.jdbc.base.BaseConnection.open(Unknown Source)
     at com.ddtek.jdbc.base.BaseDriver.connect(Unknown Source)
     at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:149)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:472)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:253)
     at com.sap.sdm.serverext.servertype.dbsc.extern.DBSCConnectionManager.createSDMVendorConnection(DBSCConnectionManager.java:214)
     at com.sap.sdm.serverext.servertype.dbsc.extern.DBSCConnectionManager.createSDMConnections(DBSCConnectionManager.java:77)
     at com.sap.sdm.serverext.servertype.dbsc.ConnectionManagerDecorator.createSDMConnections(ConnectionManagerDecorator.java:73)
     at com.sap.sdm.serverext.servertype.dbsc.DatabaseTargetSystem.connect(DatabaseTargetSystem.java:140)
     at com.sap.sdm.serverext.servertype.dbsc.DBSCDeploymentActionProcessor.executeAction(DBSCDeploymentActionProcessor.java:115)
     at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:58)
     at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:181)
     at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:51)
     at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:84)
     at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:61)
     at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:78)
     at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:88)
     at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:74)
     at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:121)
     at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:90)
     at com.sap.sdm.control.command.cmds.Deploy.execute(Deploy.java:162)
     at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:54)
     at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)
     at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)
     at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)
     at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)
     at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)
     at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)
     at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)
     at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:52)
     at com.sap.sdm.control.command.Command.exec(Command.java:42)
     at SDM.main(SDM.java:21)
Thanks in Advance
Regards
Vasu

Hi Vasudevan,
Does you password contain any special characters?
Try using a simple password.
Regards
Daniel

JDBC Connection Error with Sql Server 2005

Hi
I am trying to connect the Sql Server 2005 thru jdbc but I am getting the following error.
SQLException: The TCP/IP connection to the host usselect.com/x-logs, port 1433 has failed. Error: usselect.com/x-logs. Please verify the connection properties and check that a SQL Server instance is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.
I am using sqljdbc4.jar (driver)
import java.sql.Connection; import java.sql.DatabaseMetaData; import java.sql.DriverManager; import java.sql.SQLException; public class testdb { public static void main(String s[]){ String userid="xxxx", password = "xxxxx"; String url = "jdbc:sqlserver://usselect.com/x-logs:1433"; Connection con = null; try { Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver"); }catch(java.lang.ClassNotFoundException e) { System.err.print("ClassNotFoundException: "); System.err.println(e.getMessage()); } try { con = DriverManager.getConnection(url,userid,password); } catch(SQLException ex) { System.err.println("SQLException: " + ex.getMessage()); } if(con!= null){ System.out.println("Got Connection."+con); }else{ System.out.println("Could not Get Connection"); } } }
Please advise.

srinu1198 wrote:
By using Jdbc thin driver are we able to connect to mssql 2005 through windows authentication or not? "thin driver" refers to a specific Oracle driver.
Far as I know both the current (not older) MS driver supports windows auth. Certianly the jTDS driver does.
If yes what is the procedure. One starts by reading the docs. If necessary then one googles.

Connect jdeveloper with sql server 2005

hello, I don't speak english very well, how I do to connect sql server 2005 with jdeveloper using create connections without username and password, using windows autentication. I downloaded driver jdbc from microsoft pages, when I create the connections and click test connections, the conecctions failed because I don't have username and pass in sql server. Thanks and sorry for my english. Regards

When the SQL Server is installed a password is specified for the 'sa' user, or a new SQL Server user may also be created.
Please refer
http://www.devx.com/dbzone/Article/33681

App not versioned error in JDeveloper - ADF with SQL Server 2005

Similar Messages

Maybe you are looking for