Unable to connect DI API-----urgent

Hi experts,
i am using SAP 2007B. When i am trying to connect the xlreporter i am getting the message that
UNABLE TO CONNECT DI API SERVER TYPE MISMATCH
Please help me out to solve this problem urgently
thanks in advance
regards
Ashish gupte

Hi Ashish
As of version 2007 you must specify the server type for the DI API. Here is a sample:
Dim vCmp As SAPbobsCOM.Company
Dim lRetCode, lErrCode As Long
Dim sErrMsg As String
Set vCmp = New SAPbobsCOM.Company
vCmp.Server = "(local)"
vCmp.CompanyDB = "MYDATABASE"
vCmp.UserName = "manager"
vCmp.Password = "manager"
vCmp.DbUserName = "sa"
vCmp.DbPassword = "xxxxxxx"
vCmp.DbServerType = dst_MSSQL2005
vCmp.UseTrusted = False
lRetCode = vCmp.Connect
If lRetCode <> 0 Then
vCmp.GetLastError lErrCode, sErrMsg
End If
Note the line for DbServerType.
Kind regards
Peter Juby

Similar Messages

The WSUS administration console was unable to connect to the WSUS Server via the remote API. (Server 2k8)

I have installed a new server for WSUS on Server 2k8, This is a stand alone server on Internet No client system is connected on this server as I have to copy these updates to my LAN which never connects to internet. (Previously I was using server 2k3. for
online & server 2008 on my LAN , now I have changed the server for Online)
Wsus has finished the synchronization & downloaded updates of around 67GB & its downloading more updates. The server shows me some updates are waiting to approved. but when I click the link for those updates I get following error message.
error code is as follows -
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
System.Net.WebException -- The operation has timed out
Source
System.Web.Services
Stack Trace:
   at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse(WebRequest webRequest)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, Int32 publicationState)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, ExtendedPublicationState publicationState)
   at Microsoft.UpdateServices.Internal.BaseApi.Update.SearchUpdates(UpdateScope searchScope, ExtendedPublicationState publicationState, UpdateServer updateServer)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetUpdates(UpdateScope searchScope)
   at Microsoft.UpdateServices.UI.AdminApiAccess.UpdateManager.GetUpdates(ExtendedUpdateScope filter)
   at Microsoft.UpdateServices.UI.AdminApiAccess.BulkUpdatePropertiesCache.GetAndCacheUpdates(ExtendedUpdateScope updateScope, ComputerTargetScope computerTargetScope)
   at Microsoft.UpdateServices.UI.SnapIn.Pages.UpdatesListPage.GetListRows()
I Have tried desabling the firewall,disabling the antivirus protection. Tried by changing the default rule Please Help.

Hi Sagar,
First, please check if the RAM is exhausted. When there is not enough RAM, this issue may occurs.
Please try to run iisreset on the WSUS server, then try to reconnect.
Also, please try to run the server cleanup wizard to remove the unused update.
Best Regards.
Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

XL Reporter error Unable to Connect to SAP Business One DI API

Hi Experts,
Im getting this error on one of our clients' workstations.
They have SAPB1 2005A PL 31.
We've tried uninstalling and reinstalling the DIAPI and the whole client application as well. Same error.
It als gives an error after the initial error that says:
"Security Settings in Microsoft Excel prohibit XL Reporter from running."
Any suggestions?
Thanks!

hi jairus,
To fix this XLR error 'unable to connect to SAP Business One DI API', do the following:
1. Go to control panel and uninstall SAP DI API
2. Run %temp%
3. Rename the folder SM_OBS_DLL
4. Go to the patch level package of the patch level you are using and install DI API. If you get a message that the installation already exists, ignore the message and proceed to install DI API.
XLR should work properly.
Best Regards,
David

Error Starting XL Reporter - Unable to connect to SAP Business One DI API

Hi Experts,
I am getting the error message...
Unable to connect to SAP Business One DI API
[SAP Business One DI API]
Internal error (-8006) occurred [131-183]
...when trying to start XL Reporter on one client PC. Until today, it has been working OK.
What needs to be done?
Thanks
Greig

Hi Gordon,
I thought that might be the answer. Are there any set instructions for a 'clean' client uninstall?
Thanks
Greig

Remote access VPN-unable to connect inside-URGENT

Hi,
I have configured Remote access VPN in cisco ASA 5520.Whenever I am trying to connect from outside it's connecting fine.It aslo getting IP from pool but prob is i am unable to connect/ping inside nw.
Pls help me...how to resolve this issue.

I had the same problem on an IOS router (871). My solution was one of two things. I downloaded the most up-to-date version of the VPN client (5.0.02.90) as opposed to the version I had or it was a software firewall (Norton 360). I have two different computers. One works just fine...the other connects but no traffic passes through. Here is what I have:
Computer 1 (working)- VPN Client v5.0.02.0090 and Network Associates Enterprise VirusScan.
Computer 2 (not working) - VPN Client v5.0.00.0340 and Norton 360.
I highly doubt it is the VPN Client, but sometimes you never know. Check your software firewall and try disabling it. Let me know how this works.

How to resolve on my iPad: Unable to connect to server error when trying to log into Game Center?

When I try to log into the game center, i get an error message that says: unable to connect to server due to an error communicating with the server.
I have logged off iTune and any other app I was logged in, I have done a hard reset of my iPad, I have reset my modem, but nothing had any impact and I am now frozen out of my game center.
Anybody has an idea of how to resolve this?
Thanks,
J

1) May be there is a mismatch with the jar file name and the filename in the jad properties ( happens only if you rename the jar file)
2) Check hollywood jad properties and the ringtone jad properties. May be the complete url is required for the jar file.
3) If you are using any restricted APIs in your midlet, then make sure your jad properties has the required permissions.

Unable to connect to Services Registry(error) while connecting from NWDS

Hi SDN friends,
I am trying to do WSDL import from NWDS (Developer Studio SAP NetWeaver 7.1 Composition Environment SP03 PAT0000 Build id: 200710302120 ) and i am getting following error
"Unable to connect to Services Registry"
Below are the service regsitry details i am passing
window --> Preferences
Service Registry (UDDI Service)
Server Name:sr.esworkplace.sap.com
Server Port:sr.esworkplace.sap.com
Server Port:50000
Server HTTPS Port:50043
Inquiry Path:uddi/api/inquiry
Publish Path:uddi/api/publish
Security Path:uddi/api/security
Classification Service
Server Name:sr.esworkplace.sap.com
Server Port:50000
Server HTTPS Port:50043
Classification Path:ClassificationService/CS?style=document
I am using the following credentials for login to UDDI Service http://sr.esworkplace.sap.com
login/pwd: sruser
password: esword123
I tried with two different systems (office and Home) , bit still not connecting.
Waiting for experts answer.
Thanks
Aravinda

Hi,
You wrote that you connect to the SAP uddi:
Service Registry (UDDI Service)
Server Name:sr.esworkplace.sap.com
Server Port:sr.esworkplace.sap.com
Server Port:50000
Server HTTPS Port:50043
Inquiry Path:uddi/api/inquiry
Publish Path:uddi/api/publish
Security Path:uddi/api/security
sr.esworkplace.sap.com is not on your home pc. Its a SAP public uddi.
If you want to connect to your own pc than your configuration would be sompething like this:
Server Name:localhost
Server Port:50000
Server HTTPS Port:50043
Inquiry Path:uddi/api/inquiry
Publish Path:uddi/api/publish
Security Path:uddi/api/security
And you shouldn't use this login data
login/pwd: sruser
password: eswork123
regards,
v s
Edited by: v s on Jul 2, 2008 9:31 AM
Edited by: v s on Jul 2, 2008 9:34 AM

Transaction iview Unable to Connect to Backend

Transaction iview Unable to Connect to Backend
Hi guys,
I am new to SAP and i am having several issues.
Right now i am stuck here, in the NetWeaver Portal:
I have created a Transaction iview and a System with Alias "SAP_R3".
When i preview the iview i am getting the following error:-
No user mapping defined for system SAP_R3
Followed by:-
404 Not Found
SAP J2EE Engine/7.00
The requested resource does not exist.
Details:
Go to main page of this application!
An urgent response will be highly appreciated
Thanks much,
B

Hello B,
I see two issues here.
1. User Mapping
2. The requested resource does not exist.
For 1,
First go to System Admin ->System Config search for SAP_R3 system and open it and as told before check the user management property.
also chck taht you should get the System SAP_R3 in personalize user mapping option.
2. The requested resource error can come when the corresponding iview been attached to the role has been moved or deleted.
Request you to clear cache first by system admin -> system config->navigation
then follow this blog:
Create SAP Transaction iView using SAPGUI for Windows
Hope this helps!
If not, please update the message accordingly.
regards
Atul Shrivastava

BPCNW 7.5 SP7 - Unable to connect to backend after installation

Hi Experts,
I have installed the BPC NW 7.5 SP7 with CMS authentication but when i launch the BPC server manager, it ask for user id and password. But when i enter the password for the bpc_sysadm, it gives the error "unable to connect to backend Abap system"
I am stuck and urgent help is required.
In backened, entry in the table UJA_SVR_DEFAULT is the hostname of of CMS.
I dont have sapmsg.ini file under c:
Windows as shown in the below log. Does it matter?
Below is the error log
2.0 #2011 08 14 20:06:39:223#+2:00#Error#ServerMgrService##EPM-BPC-NW##dbaf8fa3-8af1-478e-8091-082680638a84###TestConnection#BPC_SYSADM########Plain##<Exception><ExceptionInfo><exType>SAP.Connector.RfcException</exType><exMessage>Open file 'C:
Windows
sapmsg.ini' failed</exMessage><exSource>SAP.Connector</exSource><assembly>SAP.Connector.Connection, SAP.Connector, Version=2.0.0.0, Culture=neutral, PublicKeyToken=50436dca5c7f7d23</assembly><stackTrace>   at SAP.Connector.Connection.Open()
   at SAP.Connector.Connection.BeforeCall(SAPClient sapclient)
   at SAP.Connector.SAPClient.BeforeCall()
   at SAP.Connector.SAPClient.SAPInvoke(String method, Object[] methodParamsIn)
   at SAPServerMgrProxy.SAPServerMgrProxy.Uja3_Get_User_Langu(UJ0_S_USER Is_User, String& E_Langu, UJ0_T_MESSAGE& Et_Error)
   at OSoft.Services.Common.ApplicationServiceProxy.ContextUser.GetUserLanguageProxy.getABAPUserLanguage()
   at OSoft.Services.Common.ApplicationServiceProxy.ContextUser.init(Hashtable htContext)
   at OSoft.Services.Common.ApplicationServiceProxy.ContextUser..ctor(String contextXML)
   at Osoft.Services.Webservice.ServerMgrService.ServerMgrService.TestConnection(String strParameter, String strContext)
</stackTrace><exTime>8/14/2011 8:06:39 PM</exTime></ExceptionInfo><WebServiceLayer><machineName>SVRMSA030</machineName><userName></userName><csnComponent>EPM-BPC-NW-SRV</csnComponent><className>ServerMgrService</className><MethodInfo><methodName>TestConnection</methodName><Params><strParameter></strParameter><strContext>
<Context>
<AppSet>
</AppSet>
<UserID><![CDATA[BPC_SYSADM]]></UserID>
<App><![CDATA[]]></App>
<Language><![CDATA[]]></Language>
<Session>
<SessionID><![CDATA[]]></SessionID>
<Machine><![CDATA[]]></Machine>
<Machine_Name><![CDATA[SVRMSA030]]></Machine_Name>
<ModuleName><![CDATA[]]></ModuleName>
</Session>
<CurrentView>
<Dim>
<Name></Name>
<Value></Value>
</Dim>
</CurrentView>
</Context></strContext><strSecurity>
<SECURITY>
<CheckSum><![CDATA[4jyETibRHl1Mk3AfQ/l9m8tNWjE=]]></CheckSum>
<IsZipped><![CDATA[False]]></IsZipped>
<IsEncrypted><![CDATA[True]]></IsEncrypted>
</SECURITY></strSecurity></Params></MethodInfo></WebServiceLayer><additionalInfo></additionalInfo><displayMode>ERROR</displayMode></Exception>#
Regards
Sagar
Edited by: sagar chouhan on Aug 14, 2011 11:30 PM

Thanks for your reply. I tried using "BPC_SYSADM" and "BPC_ADMUSR" but for both the users I am getting the same error. i checked the servername in the connection wizard it is correct. I am doing this for first time after installation.
In the backend, i checked the table UJA_SVR_DEFAULT and the entry for all the 3 fields are as below
ADMIN    -- CMS hostname
SYSADMIN - CMS Hostname
USER -- CMS hostname
Regards,
Sagar

Using Bridge CS5 exporting to flickr get error message "Unable to connect to Flickr, please check your internet connection and try again."?

using Bridge CS5 to exporting to flickr, but get error message "Unable to connect to Flickr, please check your internet connection and try again." please help?

I'm experiencing the same problem. Don't think I can help, but maybe I can offer an explanation. It looks as if Flickr has changed their API and Adobe will need to update the export plugin to comply to get it working again. I found this announcement on Flickr:
Flickr: The Help Forum: [Official Thread] Flickr API switching to https-only on June 27th, 2014!

Possible workaround for: Launch Debugger Error "Unable to connect to the RDS server"

I do not yet have a reproducible case for this. *Sometimes* ColdFusion Builder throws the "Unable to connect to the RDS server" error, when attempting to start a debug session against a remote server. However, "RDS Dataview" and "RDS Fileview" views correctly list the servers and their related data/file, and testing RDS connection result is "Test connection was successful". The workaround is:
1. Login to the ColdFusion Administrator
2. Navigate to "Debugger Settings" page (beneath "Debugging & Logging")
3. Click on "Stop Debugger Server" -or- "Restart Debugger Server"
4. Restart ColdFusion Application Server
Notes:
a) Step #3 must be done via ColdFusion Administrator, not via ColdFusion Admin API (stopLineDebugger()|restartLineDebugger())
b) Step #4 can be done via ColdFusion Administrator -or- ColdFusion Builder
c) Note that there is a CF9 Release Note for Bug #78488: "When a server having "Windows service option" ENABLED is added as a remote server, then Start-Stop-Restart operation cannot be done on it." However, I've found that "Restarting" a remote server, that is running as a Windows service, is possible in ColdFusion Builder (at least this is so on standalone developer edition). Like Bug #78488 says, I am unable to "Stop|Start" a remote server that is running as a Windows service. I'm just mentioning all of this, due to my suggestion in "b", that CF can also be restarted via ColdFusion Builder.
It is interesting that attempts to stop|restart the debugger server, via CF Admin API, do not resolve the issue. So, it seems that the "Stop Debugger Server" and "Restart Debugger Server" buttons, in CF Admin, are doing more than calling the corresponding CF Admin API methods.
Attached is an image of the error.
Just posting all of this as an FYI, in case it helps anyone.
Thanks!,
-Aaron Neff
(OH.. I'm unable to attach images at this time *DOH!* ..well, I'll try to remember to update this post w/ the image, once I see that attachments are allowed.)
I'll try to describe the error message window:
- It is 494x452 pixels
- Title of the window is "Error occurred while launching the Debugger"
- Body content of the window is as follows:
Unable to connect to the RDS server 'ServerNameHere'
Ensure that the server is currently running and that line debugging and RDS are enabled. You may also need to check your RDS connection settings in Eclipse to ensure that they are correct.
Error Message:
-1:Error connecting to JVM for debugging at localhost:5005. Could not attach to the VM at port 5005. You must specify this debugger port in the JVM settings of your application server, for example: -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005. You will also need to make sure that another debugger is not currently connected to the CF JVM at the same port (5005).
Root cause ->
Connect refused: connect

hi,
I have been facing the same problems while connecting to Oracle Web Conferencing and is getting error message :Unable to connect to the server. The Web COnferencing Console will now close. Please try again later. If the problem persist, contact your system administrator.
Diagnostic report shows failed on the connectivity part
Connectivity
mx-direct Failed
0:00:00.719 Connecting to web331.oracle.com:1025
0:00:00.922 Name resolved to 148.87.108.234
0:00:21.906 connect() failed (0x8007274C)
0:00:21.906 Connection failed (0x8007274C)
Pl help me to fix the problem.
Regards
Gobind Ahuja

Unable to connect to SAPNet message server

Hi,
after starting the SAProuter, i have to check if i am able to connect to SAPNet message server.
Here is the message delivered after configuring technical parameters:
Unable to connect to SAPNet message server
Is the problem coming from the saprouttab file?
Here is my configuration of my saprouttab file :
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" <SAProuter's Server IP Adress> <Port Number>
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 194.39.131.34 3299
P <SAProuter's Server IP Adress> 194.39.131.34 3299
D * * *
Thanks for your help.
Pascal.

Hi,
yes when i go to
start -> run -> drivers -> etc -> hosts file and i add the command that you suggested to me.
Here is the log file content :
Fri Mar 21 10:55:17 2008 INIT LOGFILE
Fri Mar 21 10:55:17 2008 READ ROUTTAB ./saprouttab o.k.
Edit :
when i run only those command from the saprouttab fil:
P * sapserv2 sapdp99
P sapserv2 <solution manager IP adress>
and after running the SAProuter, it seems to recognize sapserv2 but still have the problem with sapdp99.
Do i have to add sapdp99 with its 3299 port number in the hosts file?
trc file: "dev_rout", trc level: 1, release: "700"
Fri Mar 21 11:01:29 2008
SAP Network Interface Router, Version 38.10
command line arg 0:     saprouter
command line arg 1:     -r
command line arg 2:     -S
command line arg 3:     3299
command line arg 4:     -G
command line arg 5:     saprouter.log
command line arg 6:     -K
command line arg 7:     p:<Distinguished Name>
SncInit(): Initializing Secure Network Communication (SNC)
      PC with Windows NT (mt,ascii,SAP_UC/size_t/void* = 8/32/32)
SncInit(): Trying environment variable SNC_LIB as a
      gssapi library name: "E:\usr\sap\saprouter\sapcrypto.dll".
File "E:\usr\sap\saprouter\sapcrypto.dll" dynamically loaded as GSS-API v2 library.
The internal Adapter for the loaded GSS-API mechanism identifies as:
Internal SNC-Adapter (Rev 1.0) to SECUDE 5/GSS-API v2
main: pid = 3860, ppid = 0, port = 3299, parent port = 0 (0 = parent is not a saprouter)
reading routtab: './saprouttab'
***LOG Q0I=> NiPGetServByName: service 'sapdp99' not found: getservbyname [ninti.c 489]
ERROR => service 'sapdp99' unknown, skip line 29 [nirout.cpp   7923]
Edited by: Franu00E7ois-Xavier LEVY on Mar 21, 2008 11:02 AM

Unable to connect to 10g database from developer suite 10g

I have loaded oracle 10g on my server with OS windows 2003 and it is working fine.Now I have installed Oracle developer suite 10g on windows XP client . we have configured local listener also and its entry is found in tnsnames.ora
My database name is mbxdata .
I have defined my host name as
MBXDATA.mbxnet.com in tnsnames but I am unable to connect to the database since I get error as ORA-12154 : TNS :could not resolve the connect identifier specified.
Please suggest matter urgent.
Thanks in advance

We are having the same issue now. Was this ever resolved? We created 2 new databases and added those entries in both tnsnames on the local pc, and the tnsnames on the application server. Able to connect via sqlplus, toad, etc. but not through forms developer. We are running 10g app server, 10g developer suite, 10g databases. Any ideas?
Thanks,
Deb

Unable to Connect to the Server and WLI Domain problem

Hi All
this is the details
I have installed installed WIntegration Server and using
quickstart click the Take to Platform tour I started all the servers
Note-- I have not installed separate weblogic server 7.0 and not started.
whenever I click started WebLogic Integration Studio and it shows
user --admin
password- security
url--t3://localhost:7001
once submit it shows always Unable to connect to the server
please help me ???????????????????????????????????????????/
Server is running fine I used quickstart--- Take the live platform tour to run
the below servers.
C:\bea\weblogic700\samples\platform\e2eDomain>"C:\bea\jdk131_08\bin\java" -hotsp
ot -Xms256m -Xmx256m -XX:MaxPermSize=256m -Xverify:none -Dcommerce.properties="
C:\bea\weblogic700\portal\weblogiccommerce.properties" -Dweblogic.jws.Production
Mode="false" -Dweblogic.servlet.ClasspathServlet.disableStrictCheck="true" -De2e
Sample.b2b.path.data=".\beaApps\e2eApp\data" -Dweblogic.Name=e2eServer -Dbea.hom
e="C:\bea" -Dweblogic.management.username= -Dweblogic.management.password= -Dweb
logic.ProductionModeEnabled=true -Dweblogic.management.discover=false -Djava.sec
urity.policy=="C:\bea\weblogic700\server\lib\weblogic.policy" weblogic.Server
Starting WebLogic Server...
<Aug 5, 2003 1:22:23 PM EDT> <Notice> <Management> <140005> <Loading configurati
on C:\bea\weblogic700\samples\platform\e2eDomain\.\config.xml>
<Aug 5, 2003 1:22:37 PM EDT> <Notice> <Security> <090093> <No configuration data
was found on server e2eServer for realm CompatibilityRealm.>
<Aug 5, 2003 1:22:37 PM EDT> <Notice> <Security> <090082> <Security initializing
using realm CompatibilityRealm.>
<Aug 5, 2003 1:22:38 PM EDT> <Notice> <WebLogicServer> <000327> <Starting WebLog
ic Admin Server "e2eServer" for domain "e2eDomain">
<Aug 5, 2003 1:24:23 PM EDT> <Notice> <B2BIntegration> <000000> <INFO: WebLogic
Integration - B2Bi Server started successfully.>
INFO: WebLogic Integration - B2Bi Server started successfully.
<Aug 5, 2003 1:24:31 PM EDT> <Notice> <AI> <000000> <Started WebLogic Integratio
n - AI Server version 7.0.4.0>
<Aug 5, 2003 1:24:35 PM EDT> <Notice> <BPM> <000000> <Started WebLogic Integrati
on - BPM Server version 7.0.4.0>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
After the server has booted, your browser should
automatically launch and point to the WebLogic Server
Index running on this server. If your browser
fails to launch, point your browser to the URL
"http://Inforicadb:7501/index.jsp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
=============== Initializing Logger ======================
<Aug 5, 2003 1:24:36 PM EDT> <Notice> <Management> <141053> <Application Poller
not started for production server.>
<Aug 5, 2003 1:24:46 PM EDT> <Notice> <WebLogicServer> <000354> <Thread "SSLList
enThread.Default" listening on port 7502>
<Aug 5, 2003 1:24:46 PM EDT> <Notice> <WebLogicServer> <000354> <Thread "ListenT
hread.Default" listening on port 7501>
<Aug 5, 2003 1:24:47 PM EDT> <Notice> <WebLogicServer> <000329> <Started WebLogi
c Admin Server "e2eServer" for domain "e2eDomain" running in Production Mode>
<Aug 5, 2003 1:24:48 PM EDT> <Notice> <WebLogicServer> <000365> <Server state
ch
anged to RUNNING>
<Aug 5, 2003 1:24:48 PM EDT> <Notice> <WebLogicServer> <000360> <Server started
in RUNNING mode>
please help me, urgent
Thanks in advance
Domain problem---------------------------------------------
I created WLI domain like this is it correct ?
Next I used Quick start's --Configure New Server
then single server option radio selected
then
single server name--myserver
server listner address---????????? please tell me
server listening port 7001
ssl listnening port 7002
username bala
password subramaniam
verify password subramaniam
c:\bea\user_projects\CIBC
configure database mail--
email address- [email protected]
email host: what need to give ??????? please tell me----
after I created domain called CBC it is in the
c:\bea\user_projects\CBC
then I saw it consists
1)wlai folder
2)dbinfo
3)application
4)keys
5)scripts
setdatabase.cmd
startweblogic.cmd
startmanagedweblogic.cmd
setwlidomaindata.cmd
wliconfig.cmd
checkdomain.cmd
Wliconfig.jar
startweblogic.cmd
stopweblogic.cmd
I try to startweblogic.cmd it open and closed no action
please tell me what is the problem????????????
with regards
bala

Oh boy! Let me see what's going on. Are you using the VZW Cloud or the BUA app? Please try downloading the VZW Cloud app if you dont already have it. And once downloaded. Tap the 3 bars in the upper corner and go down to "TOOLS", then tap "RESTORE CONTENT". That should do it!
VanetrisC_VZW
Follow us on Twitter @VZWSupport

Petstore - unable to connect to embedded LDAP Server

I have installed the Petstore 1.3.1 02 demo on a Weblogic 8.1 server on Windows XP. After running the Configuration wizard, when trying to start the PetStore Administration Sever using the startPetStoreWebLogic.cmd file, I receive the following error message:
The WebLogic Server did not start up properly.
weblogic.security.spi.ProviderInitializationException: [Security:090314]Entitlement Engine unable to connect to the embedded LDAP server
netscape.ldap.LDAPException: error result (50)
An LDAPException with error result 50, according to the API Specification, means insufficient access rights, but as I am doing everything according to the readme, I don't know what the problem is.
Has anybody had the same problem or knows what to do to solve this?
Thanks very much!

Hi,
By removing the encrypted 'Credential' for the
EmbeddedLDAP entry in config.xml workaround it,
it went on but the real problem is with the
deployment of the 4 ears inside applications dir.
Would appreciate of anyone could enlighten.
jchintk
####<Jan 28, 2005 2:59:31 PM SGT> <Debug> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149078> <Stack trace for message 149004
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 0
     Module: customer-ejb.jar     Error: [EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
PAction[30633251](.ejb-jar.relationships.ejb-relation.ejb-relation-name.) must be a non-empty string.
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2467)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
>
####<Jan 28, 2005 2:59:31 PM SGT> <Error> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149201> <Failed to complete the deployment task with ID 0 for the application appsdirpetstore_ear.
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 0
     Module: customer-ejb.jar     Error: [EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
PAction[30633251](.ejb-jar.relationships.ejb-relation.ejb-relation-name.) must be a non-empty string.
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2467)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 0
     Module: customer-ejb.jar     Error: [EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
PAction[30633251](.ejb-jar.relationships.ejb-relation.ejb-relation-name.) must be a non-empty string.
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2396)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
>
####<Jan 28, 2005 2:59:34 PM SGT> <Info> <Application Poller> <oakley> <myserver> <Main Thread> <<WLS Kernel>> <> <BEA-149400> <Activating application: appsdirsupplier_ear>
####<Jan 28, 2005 2:59:34 PM SGT> <Info> <Deployer> <oakley> <myserver> <Main Thread> <<WLS Kernel>> <> <BEA-149038> <A deployment task with ID 1 for application appsdirsupplier_ear is being initiated.>
####<Jan 28, 2005 2:59:34 PM SGT> <Warning> <DRS> <oakley> <myserver> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-002506> <The current version 0 for DataIdentifier DataIdentifierID: 1 does not match with incoming version 1 for a one-phase update.>
####<Jan 28, 2005 2:59:34 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149033> <preparing application appsdirsupplier_ear on myserver>
####<Jan 28, 2005 2:59:34 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149033> <failed application appsdirsupplier_ear on myserver>
####<Jan 28, 2005 2:59:34 PM SGT> <Warning> <Deployer> <oakley> <myserver> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149004> <Failures were detected while initiating Deploy task for application appsdirsupplier_ear.>
####<Jan 28, 2005 2:59:34 PM SGT> <Debug> <Deployer> <oakley> <myserver> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149078> <Stack trace for message 149004
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 1
     Module: supplierpo-ejb.jar     Error: [EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
PAction[30633251](.ejb-jar.relationships.ejb-relation.ejb-relation-name.) must be a non-empty string.
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2467)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
>
####<Jan 28, 2005 2:59:34 PM SGT> <Error> <Deployer> <oakley> <myserver> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149201> <Failed to complete the deployment task with ID 1 for the application appsdirsupplier_ear.
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 1
     Module: supplierpo-ejb.jar     Error: [EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
PAction[30633251](.ejb-jar.relationships.ejb-relation.ejb-relation-name.) must be a non-empty string.
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2467)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 1
     Module: supplierpo-ejb.jar     Error: [EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
PAction[30633251](.ejb-jar.relationships.ejb-relation.ejb-relation-name.) must be a non-empty string.
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2396)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
>
####<Jan 28, 2005 2:59:38 PM SGT> <Info> <Application Poller> <oakley> <myserver> <Main Thread> <<WLS Kernel>> <> <BEA-149400> <Activating application: appsdirpetstoreadmin_ear>
####<Jan 28, 2005 2:59:38 PM SGT> <Info> <Deployer> <oakley> <myserver> <Main Thread> <<WLS Kernel>> <> <BEA-149038> <A deployment task with ID 2 for application appsdirpetstoreadmin_ear is being initiated.>
####<Jan 28, 2005 2:59:38 PM SGT> <Warning> <DRS> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-002506> <The current version 0 for DataIdentifier DataIdentifierID: 1 does not match with incoming version 2 for a one-phase update.>
####<Jan 28, 2005 2:59:55 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149033> <preparing application appsdirpetstoreadmin_ear on myserver>
####<Jan 28, 2005 2:59:56 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149059> <Module admin of application appsdirpetstoreadmin_ear is transitioning from unprepared to prepared on server myserver.>
####<Jan 28, 2005 2:59:56 PM SGT> <Warning> <HTTP> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-101304> <Webapp: ServletContext(id=12397950,name=admin,context-path=/admin), the role: administrator defined in web.xml has not been mapped to principals in security-role-assignment in weblogic.xml. Will use the rolename itself as the principal-name.>
####<Jan 28, 2005 2:59:56 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149060> <Module admin of application appsdirpetstoreadmin_ear successfully transitioned from unprepared to prepared on server myserver.>
####<Jan 28, 2005 2:59:56 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149059> <Module asyncsender-ejb.jar of application appsdirpetstoreadmin_ear is transitioning from unprepared to prepared on server myserver.>
####<Jan 28, 2005 2:59:56 PM SGT> <Info> <EJB> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-010008> <EJB Deploying file: asyncsender-ejb.jar>
####<Jan 28, 2005 2:59:56 PM SGT> <Info> <EJB> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-010087> <The EJB deployment named: asyncsender-ejb.jar is being recompiled within the WebLogic Server. Please consult the server logs if there are any errors. It is also possible to run weblogic.ejbc as a stand-alone tool to generate the required classes. The generated source files will be placed in C:\bea\user_projects\domains\petstore\.\myserver\.wlnotdelete\EJBCompilerCache\283hhgsoep72.>
####<Jan 28, 2005 3:00:00 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149061> <Module asyncsender-ejb.jar of application appsdirpetstoreadmin_ear failed to transition from unprepared to prepared on server myserver.>
####<Jan 28, 2005 3:00:00 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149059> <Module admin of application appsdirpetstoreadmin_ear is transitioning from prepared to unprepared on server myserver.>
####<Jan 28, 2005 3:00:00 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149060> <Module admin of application appsdirpetstoreadmin_ear successfully transitioned from prepared to unprepared on server myserver.>
####<Jan 28, 2005 3:00:00 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149033> <failed application appsdirpetstoreadmin_ear on myserver>
####<Jan 28, 2005 3:00:02 PM SGT> <Info> <Application Poller> <oakley> <myserver> <Main Thread> <<WLS Kernel>> <> <BEA-149400> <Activating application: appsdiropc_ear>
####<Jan 28, 2005 3:00:02 PM SGT> <Info> <Deployer> <oakley> <myserver> <Main Thread> <<WLS Kernel>> <> <BEA-149038> <A deployment task with ID 3 for application appsdiropc_ear is being initiated.>
####<Jan 28, 2005 3:00:00 PM SGT> <Warning> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149004> <Failures were detected while initiating Deploy task for application appsdirpetstoreadmin_ear.>
####<Jan 28, 2005 3:00:06 PM SGT> <Debug> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149078> <Stack trace for message 149004
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for asyncsender-ejb.jar
     Module: asyncsender-ejb.jar     Error: Exception preparing module: EJBModule(asyncsender-ejb.jar,status=NEW)
Unable to deploy EJB: AsyncSenderEJB from asyncsender-ejb.jar:
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
weblogic.deployment.EnvironmentException: [EJB:010174]The resource-ref 'jms/QueueConnectionFactory' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor.
     at weblogic.ejb20.deployer.EnvironmentBuilder.addJMSConnectionFactoryRef(Lweblogic.management.descriptors.ejb11.ResourceRefMBean;Ljava.util.Map;)V(EnvironmentBuilder.java:439)
     at weblogic.ejb20.deployer.EnvironmentBuilder.addResourceReferences(Ljava.util.Collection;Ljava.util.Map;)V(EnvironmentBuilder.java:226)
     at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentContext(Ljavax.naming.Context;Lweblogic.ejb20.interfaces.BeanInfo;Ljava.lang.String;Ljava.lang.String;)Ljavax.naming.Context;(EJBDeployer.java:379)
     at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentFor(Lweblogic.ejb20.interfaces.BeanInfo;Lweblogic.ejb20.interfaces.DeploymentInfo;Lweblogic.management.configuration.EJBComponentMBean;Ljavax.naming.Context;)Ljavax.naming.Context;(EJBDeployer.java:1172)
     at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(Lweblogic.management.configuration.EJBComponentMBean;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;)V(EJBDeployer.java:943)
     at weblogic.ejb20.deployer.EJBDeployer.prepare(Lweblogic.utils.jars.VirtualJarFile;Ljava.lang.ClassLoader;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;Ljava.util.Map;)V(EJBDeployer.java:1345)
     at weblogic.ejb20.deployer.EJBModule.prepare(Ljava.lang.ClassLoader;)V(EJBModule.java:498)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModule(Lweblogic.utils.classloaders.GenericClassLoader;Lweblogic.j2ee.J2EEApplicationContainer$Component;Z)V(J2EEApplicationContainer.java:3142)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModules([Lweblogic.j2ee.J2EEApplicationContainer$Component;Ljava.lang.String;Z)V(J2EEApplicationContainer.java:1583)
     at weblogic.j2ee.J2EEApplicationContainer.prepare([Lweblogic.j2ee.J2EEApplicationContainer$Component;[Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(J2EEApplicationContainer.java:1227)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(Ljava.lang.String;[Lweblogic.management.configuration.ComponentMBean;[Ljava.lang.String;)V(J2EEApplicationContainer.java:1070)
     at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer()V(SlaveDeployer.java:2513)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2463)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2467)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
>
####<Jan 28, 2005 3:00:06 PM SGT> <Error> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149201> <Failed to complete the deployment task with ID 2 for the application appsdirpetstoreadmin_ear.
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for asyncsender-ejb.jar
     Module: asyncsender-ejb.jar     Error: Exception preparing module: EJBModule(asyncsender-ejb.jar,status=NEW)
Unable to deploy EJB: AsyncSenderEJB from asyncsender-ejb.jar:
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
weblogic.deployment.EnvironmentException: [EJB:010174]The resource-ref 'jms/QueueConnectionFactory' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor.
     at weblogic.ejb20.deployer.EnvironmentBuilder.addJMSConnectionFactoryRef(Lweblogic.management.descriptors.ejb11.ResourceRefMBean;Ljava.util.Map;)V(EnvironmentBuilder.java:439)
     at weblogic.ejb20.deployer.EnvironmentBuilder.addResourceReferences(Ljava.util.Collection;Ljava.util.Map;)V(EnvironmentBuilder.java:226)
     at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentContext(Ljavax.naming.Context;Lweblogic.ejb20.interfaces.BeanInfo;Ljava.lang.String;Ljava.lang.String;)Ljavax.naming.Context;(EJBDeployer.java:379)
     at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentFor(Lweblogic.ejb20.interfaces.BeanInfo;Lweblogic.ejb20.interfaces.DeploymentInfo;Lweblogic.management.configuration.EJBComponentMBean;Ljavax.naming.Context;)Ljavax.naming.Context;(EJBDeployer.java:1172)
     at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(Lweblogic.management.configuration.EJBComponentMBean;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;)V(EJBDeployer.java:943)
     at weblogic.ejb20.deployer.EJBDeployer.prepare(Lweblogic.utils.jars.VirtualJarFile;Ljava.lang.ClassLoader;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;Ljava.util.Map;)V(EJBDeployer.java:1345)
     at weblogic.ejb20.deployer.EJBModule.prepare(Ljava.lang.ClassLoader;)V(EJBModule.java:498)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModule(Lweblogic.utils.classloaders.GenericClassLoader;Lweblogic.j2ee.J2EEApplicationContainer$Component;Z)V(J2EEApplicationContainer.java:3142)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModules([Lweblogic.j2ee.J2EEApplicationContainer$Component;Ljava.lang.String;Z)V(J2EEApplicationContainer.java:1583)
     at weblogic.j2ee.J2EEApplicationContainer.prepare([Lweblogic.j2ee.J2EEApplicationContainer$Component;[Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(J2EEApplicationContainer.java:1227)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(Ljava.lang.String;[Lweblogic.management.configuration.ComponentMBean;[Ljava.lang.String;)V(J2EEApplicationContainer.java:1070)
     at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer()V(SlaveDeployer.java:2513)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2463)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2467)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for asyncsender-ejb.jar
     Module: asyncsender-ejb.jar     Error: Exception preparing module: EJBModule(asyncsender-ejb.jar,status=NEW)
Unable to deploy EJB: AsyncSenderEJB from asyncsender-ejb.jar:
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
weblogic.deployment.EnvironmentException: [EJB:010174]The resource-ref 'jms/QueueConnectionFactory' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor.
     at weblogic.ejb20.deployer.EnvironmentBuilder.addJMSConnectionFactoryRef(Lweblogic.management.descriptors.ejb11.ResourceRefMBean;Ljava.util.Map;)V(EnvironmentBuilder.java:439)
     at weblogic.ejb20.deployer.EnvironmentBuilder.addResourceReferences(Ljava.util.Collection;Ljava.util.Map;)V(EnvironmentBuilder.java:226)
     at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentContext(Ljavax.naming.Context;Lweblogic.ejb20.interfaces.BeanInfo;Ljava.lang.String;Ljava.lang.String;)Ljavax.naming.Context;(EJBDeployer.java:379)
     at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentFor(Lweblogic.ejb20.interfaces.BeanInfo;Lweblogic.ejb20.interfaces.DeploymentInfo;Lweblogic.management.configuration.EJBComponentMBean;Ljavax.naming.Context;)Ljavax.naming.Context;(EJBDeployer.java:1172)
     at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(Lweblogic.management.configuration.EJBComponentMBean;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;)V(EJBDeployer.java:943)
     at weblogic.ejb20.deployer.EJBDeployer.prepare(Lweblogic.utils.jars.VirtualJarFile;Ljava.lang.ClassLoader;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;Ljava.util.Map;)V(EJBDeployer.java:1345)
     at weblogic.ejb20.deployer.EJBModule.prepare(Ljava.lang.ClassLoader;)V(EJBModule.java:498)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModule(Lweblogic.utils.classloaders.GenericClassLoader;Lweblogic.j2ee.J2EEApplicationContainer$Component;Z)V(J2EEApplicationContainer.java:3142)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModules([Lweblogic.j2ee.J2EEApplicationContainer$Component;Ljava.lang.String;Z)V(J2EEApplicationContainer.java:1583)
     at weblogic.j2ee.J2EEApplicationContainer.prepare([Lweblogic.j2ee.J2EEApplicationContainer$Component;[Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(J2EEApplicationContainer.java:1227)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(Ljava.lang.String;[Lweblogic.ma

Unable to connect DI API-----urgent

Similar Messages

Maybe you are looking for