Nw 6.0 sp5 Bm 3.7 sp3

I have a new Netware 6.0 sp5 server with the latest TCP610m patch, Bordermanager 3.7, 3.7 SP3, 3.7 fp4e as well. When I unload the filters to test something and try to do the reinitialize system I get the following message:
IPXFLT has error in defining Log file with CSAUDIT.NLM, error=0x24000A.
I found a TID on it (2939144) dealing with CSATPXY.NLM and recopied the following from the BM3.7 CD :
SYS:SYSTEM\CSAUDIT.NLM
SYS:\SYSTEM\NLS\4\CSAUDIT.MSG
SYS:\SYSTEM\NLS\4\CSAUDIT.HLP
I still get this error. Any help would be appreciated. I really do not know if that is a big problem or not. Surely it should not be happening.

jpeteet,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Similar Messages

Import VC7.1 SP5 model into VC7.1 SP3

Hi,
it is not possible to import a model developed with VC7.1 SP5 into Visual Composer SP3. The log file shows the following:
Model Serializer: model not parsed because namespace core.gml2 needs package core.gml2 of version 1.0.3.2, whereas version 1.0.3 is currently loaded(ModelSerializer:0)
Is that intended to be like this and will future SPS releases have the same behavior?
Best regards,
Kevin

Hi Kevin,
Unfortunately, Visual Composer is not forwards compatible. That is to say, models from later SP's cannot be imported into earlier SP's. This behavior is not likely to be changed in the future.
Eyal

Server Hangs while compiling some EJB in Weblogic 6.1 SP5 on AIX 4.3.3

Hi,
Iam not able to deploy a J2EE application in WebLogic 6.1 SP5 on an AIX 4.3.3
box.
CMP is being used and my EJBs are not being compiled( though there are no errors
thrown).
Iam using IBM DB2 ver 8.0 DB as client and server.
While compiling, the server Hangs, displaying the message "<Info> <Management>
<Configuration changes for domain saved to the repository.>"
Is there any configuration Issues with weblogic 6.1 SP5 and AIX 4.3.3?
Because the same EAR works in SP3.
Please help ASAP.
Thanks in advance.
Nagesh

The only thing to do again with "hangs" is to take thread dumps. As for why
things are going wrong...... I am at a loss other than some AIX weirdness.
Cheers
mbg
"Deshpande" <[email protected]> wrote in message
news:[email protected]...
>
Hi Mark,
I tried it out ....I ran EJBC on all my EJB's and then tried to deploy myapplication.
Application got deployed and the server was up, but JSP's dosent getcompiled(
i.e when I want to run my application, my server hangs again).
I tried one more option.. I pointed my JAVAHOME in startweblogic.sh to anSP3
JDK .. and it worked!! Now with this JDK Iam able to deploy my entireapplication
( with out precompiled) also run through the application without anyproblems.
I then over wrote the existing JDK ( of SP5 ) with that of SP3 and thentried.
Which also works fentastically!!!
I can feel something fishy here ....
Any help in this regard is most welcome.
Thanks and Regards...
Nagesh
"Mark Griffith" <[email protected]> wrote:
Deshpande:
"Deshpande" <[email protected]> wrote in message
news:[email protected]...
Hi Mark,
Thanks again.
For
Q1> How much time was between the two dumps?
A1> There was a minute gap B/w the two dumps. ( since it took so longto
write
the Core)
Q2> How long have you waited with no progress seeming to be made?
A1> Over a whole night. ( appx 14 hours).
Now I believe you would have figured out what the problem is.Not sure if this is a statement saying you think I have figured it out,
or a
statement saying you think I should have figured it out but I haven't.
Anyway... Did you try running ejbc on the "app" first?
Meanwhile also it would be great, if you would tell me the proceduresto
get support
form the BEA and AIX to solve the Issue.
http://www.bea.com/framework.jsp?CNT=index.htm&FP=/content/services/custome
r_support/contacts/
>>
I would suggest sending as much detail as possible, including zips of
the
thread dumps and pointers to this newsgroup conversation [email protected]
>>
I do however suggest you first try running ejbc.
Cheers
mbg
Thanks in advance.
R
Deshpande.
"Mark Griffith" <[email protected]> wrote:
Nagesh:
Wow, AXI outputs some interesting thread dumps. ;)
So the interesting thread (and the problem) is:
"main" (TID:0x300C41D8, sys_thread_t:0x30010A60, state:CW, native
ID:0x1)
prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:429)
at java.lang.UNIXProcess.waitFor(UNIXProcess.java:130)
at weblogic.utils.Executable.exec(Executable.java(Compiled Code))
at weblogic.utils.Executable.exec(Executable.java(Inlined CompiledCode))
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.j
a
v
a(Compiled Code))
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java(Inlin
e
d
Compiled Code))
at
weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java(Compiled
Code))
at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java(InlinedCompiled
Code))
at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java(Compiled
Code))
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java(CompiledCode))
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
at weblogic.j2ee.Application.addComponent(Application.java:176)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deploymen
t
T
arget.java(Compiled Code))
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployme
n
t
Target.java:286)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments
D
eploymentTarget.java:239)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deplo
y
m
entTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanIm
p
l
..java(Compiled Code))
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java
C
ompiled Code))
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMB
e
a
nImpl.java:374)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java(Compiled
Code))
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java(Compiled
Code))
at $Proxy34.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployment
s
ServerMBean_CachingStub.java:3015)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Ap
p
l
icationManager.java:376)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationMana
g
e
r.java:164)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanIm
p
l
..java(Compiled Code))
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java
C
ompiled Code))
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMB
e
a
nImpl.java:374)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java(Compiled
Code))
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java(Compiled
Code))
at $Proxy48.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.star
t
ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1309)
at weblogic.management.Admin.finish(Admin.java:650)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:547)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:214)
at weblogic.Server.main(Server.java:35)
So the Server never gets out of the Main thread to run, because theEJBC
compilation is "stuck", ejbc is running because either the EJB being
deployed was previously deployed on a different version of WLS orejbc
had
never been run on those beans. Either there is a problem on the AIX
VM
where execing processes are not returning, OR the ejb that ejbc isrunning
on is huge and is taking a REALLY long time. How much time was
between
the
two dumps? How long have you waited with no progress seeming to bemade?
Depending on the answers to these questions it maybe that there isa
VM bug
and you will need to contact BEA support to see the procedure forworking
with AIX to resolve the issue.
You maybe able to work around the problem by running EJBC on the ejb
in
question prior to starting the server.
http://edocs.bea.com/wls/docs61/ejb/EJB_utilities.html#1075296
Cheers
mbg
"deshpande" <[email protected]> wrote in message
news:[email protected]...
Hi, Mark,
Thanks for the early reply.
I have attached two consecutive dumps Zipped.
Pls look into the same and helpme out.
Thanks in advance.
Regards,
Nagesh
"Mark Griffith" <[email protected]> wrote:
When it hangs, you need to get thread dumps.
"kill -3 PID" is how this works on Solaris. Additionally if the
terminal/shell has focus that started the process you can do "CTRL
Break"
as
well. The thread dumps will go to std-out/err, so you'll have
to
redierect
std-out and err of the shell. (Make sure you don't nohup the
process
(if
AIX even supports that) since this prevents sigquits). When thehang
occurs
take a thread dump, wait 10 seconds and take another one, thenplease
zip
and attach the file in a post.
Cheers
mbg
"Deshpande" <[email protected]> wrote in message
news:[email protected]...
Hi,
Iam not able to deploy a J2EE application in WebLogic 6.1 SP5
on
an
AIX
4.3.3
box.
CMP is being used and my EJBs are not being compiled( though
there
are no
errors
thrown).
Iam using IBM DB2 ver 8.0 DB as client and server.
While compiling, the server Hangs, displaying the message "<Info><Management>
<Configuration changes for domain saved to the repository.>"
Is there any configuration Issues with weblogic 6.1 SP5 and AIX
4.3.3?
Because the same EAR works in SP3.
Please help ASAP.
Thanks in advance.
Nagesh

Oddities when serving images via NES from a servlet that is part of a WAR

Just wanted to confirm that the following behavior is normal:
 Environment:
 NT 4.0 SP5
 NES 3.6 SP3
 WLS 5.1 SP3
 jdk 1.2.2
 Goal: When constructing a page that has images embedded in it from my
 servlet, I would like NES to serve the images.
 I've found out that I've to refer to my images with an absolute URL that
 maps to the images directory under Netscape's document root. If I refer to
 my image with a relative URL (request.getContextPath() +
 "/images/cookie.jpg"), then WebLogic tries to retrieve the image from the
 WAR. What is interesting is if I use relative references to images within my
 servlet (minus the WAR, i.e. with the servlet registered in
 weblogic.properties), I see that the image is being served by Netscape.
 Why does the WAR require absolute references to images and the previous
 mechanism does not? Is this behavior consistent with the spec? How are you
 guys handling this (are you using absolute references to static content when
 using WAR?)?
 I'm really baffled by this and wanted to see how others view this. Any
 comments/feedback will be much appreciated.
 Thanks,
 Sanjiv


Hi Cameron,
 You are right but see my "Goal" below. I want to serve my images from my web
 server and NOT by WebLogic. Anyway, I spent too much time on this and found
 out that I was getting inconsistent results during testing different
 approaches because I was not restarting my web server. Once I became
 consistent in restarting my web server and closing all browser windows
 before each test, I got consistent results. So, here's what works for me:
 If I want to have my JSPs/servlets running in WLS to serve images that are
 included in their output from my web server, then I've to use absolute URLs.
 An example would be:
 img src="/images/a.gif"
 On the other hand if I use relative paths like img src="images/a.gif", then
 the browser request for the image is sent to WebLogic, which then looks for
 the image in the WAR (as it should).
 All of this might be common knowledge to most folks but not me.
 Thanks,
 Sanjiv
 Cameron Purdy <[email protected]> wrote in message
 news:[email protected]...
 > The WAR does not require absolute paths. Your JSP must be served from a
 URL
 > that, when combined with a relative path, actually specifies an image in
 the
 > WAR.
 >
 > Cameron Purdy, LiveWater
 >
 > "Sanjiv Gulati" <[email protected]> wrote in message
 > news:[email protected]...
 > > Just wanted to confirm that the following behavior is normal:
 > >
 > > Environment:
 > > NT 4.0 SP5
 > > NES 3.6 SP3
 > > WLS 5.1 SP3
 > > jdk 1.2.2
 > >
 > > Goal: When constructing a page that has images embedded in it from my
 > > servlet, I would like NES to serve the images.
 > >
 > > I've found out that I've to refer to my images with an absolute URL that
 > > maps to the images directory under Netscape's document root. If I refer
 to
 > > my image with a relative URL (request.getContextPath() +
 > > "/images/cookie.jpg"), then WebLogic tries to retrieve the image from
 the
 > > WAR. What is interesting is if I use relative references to images
 within
 > my
 > > servlet (minus the WAR, i.e. with the servlet registered in
 > > weblogic.properties), I see that the image is being served by Netscape.
 > >
 > > Why does the WAR require absolute references to images and the previous
 > > mechanism does not? Is this behavior consistent with the spec? How are
 you
 > > guys handling this (are you using absolute references to static content
 > when
 > > using WAR?)?
 > >
 > > I'm really baffled by this and wanted to see how others view this. Any
 > > comments/feedback will be much appreciated.
 > >
 > > Thanks,
 > > Sanjiv
 > >
 > >
 >
 >

BM 3.8 and legacy VPN

HI
I have a Bm 3.8 sp5 on NetWare 6 sp5. I want to update to Gwava 4 which
needs to be at least on NetWare 6.5 sp5. I am concerned about the legacy
vpn I have that talks to a NetWare 6 sp5 BM 3.7 sp3 slave.
Is this an update I can make? The gwava indicates I might be able to run
on NetWare 6 sp5 but its not tested much.
Thanks,

Originally Posted by mrosen
Hi,
Will K wrote:
>
> HI
>
> I have a Bm 3.8 sp5 on NetWare 6 sp5. I want to update to Gwava 4 which
> needs to be at least on NetWare 6.5 sp5. I am concerned about the legacy
> vpn I have that talks to a NetWare 6 sp5 BM 3.7 sp3 slave.
>
> Is this an update I can make?
Yes, you can, and actually should use Netware 6.5 SP6, not SP5. However,
you can *not* go beyond Netware 6.5 SP6. Starting with SP7, the legacy
VPN (SKIP) breaks completely. SO, SP6 is ok, SP7 isn't.
Is it possible to back out sp7 to get the skip clients working again?
CU,
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
Untitled Document

Exchange 5.5 Portlet, versions, etc. UPDATE

I have rectified my other problem but now have a new one. For
those wondering I ended up moving the ASP files to our
production web servers (where OWA is running) as I knew CDO
worked perfectly fine there.
However, the portlets are still not rendering, still displaying
the user authentication problems. I removed and recreated both
the Exchange provider and application, to no avail.
The test.asp script now works fine. I can also run the inbox.asp
script (passing the same parameters) and I get what I assume is
the portlet contents correctly (it displays the inbox with
messages). So it would appear the problem lies somewhere in
passing the login credentials from Login Server to the ASP files.
Any other ideas?

Thanx for the reply.
All machines are on the same domain. Have tried with 3 different
exchange mailboxes and NT accounts, none have worked from Portal
but all work from when passed to inbox.asp or in OWA. All
machines are also on the same subnet. I downloaded the JPDK
yesterday, so I assume it is the latest. Very frustrating! I
have a bit of experience with CDO so this is even more
frustrating!
Summary of machines used(3):
1. Win 2K Server SP1 - Oracle 8.1.7 DB, 9iAS 1.0.2.2.1, Apache
2. Win 2K Server SP1 - IIS 5.0, Outlook Web Access 5.5 SP3
3. Win NT Server SP5 - Exchange 5.5 SP3
-- all on same domain and subnet --
Is there anyway of getting a more specific error back from the
portlet? I assume the portlet simply traps ANY error from the
inbox.asp file and displays the authentication failure message
if it didn't work. I have no experience in Java yet so if you
could tell me a line to go in and add somewhere that would
return the actual output of the inbox.asp file regardless that
might help.

IWS service stops unexpectedly all day

Installed 6.0 SP5 on Windows 2000 SP2. Web server service iWS will stop and of course the site fails... The event viewer only shows two error messages, one is event id 0 (The description for Event ID ( 0 ) in Source ( https-webserv ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: startup: server started successfully, . )
and the other is event id 25
(The description for Event ID ( 25 ) in Source ( WebServer 6.0 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: https-webserv, 0. )
I have no idea what to look for or why it keeps stopping... Help...

I am seeing this same problem with the same setup (v6.0 SP5 on Windows 2000 SP3). I get event id 0 and event id 25 in the Windows Event Log, with no information in the server's logs, and the server restarts.
This happens when I run stress testing against my web server, with 5 different users constantly making requests to the server. Sometimes the server will run for an hour before crashing, and other times it will run for 5 or 6 hours. It seems very random. I am not seeing a noticeable memory leak in the httpd.exe process that is running, and my CPU usage is only at about 40-50 % (nothing else is running on the machine).
Manish's link in his reply to the original posting is no longer a valid URL. Is there somewhere else where I can see the information he was referencing from the old iplanet web site? Or does anyone know what may be causing this?

ERROR IN WAS 6.4 SNEAK PREVIEW INSTALL DURING SP3 - SP5 DEPLOY ONLINE STAG

Hi All,
I have installed WAS 6.4 SP3 sneak preview over SQL server 2000. I get the following error message while patching from WAS SP3 to SP5 ( this patch is included as part of the sneak preview zip package) during DEPLOY ONLINE stage.
ERROR
MUT-02041 SDM call of deploySdaList ends with returncode 4. See output of logfile D:\Program Files\sapinst_instdir\PATCH\MSS\callSdmViaSapinst.log.
Also find below the log file :
Aug 23, 2004 4:09:51 PM Info: Start logging to console
Aug 23, 2004 4:09:51 PM Info:
Aug 23, 2004 4:09:51 PM Info: ============================================
Aug 23, 2004 4:09:51 PM Info: = Starting to execute command 'deploy' =
Aug 23, 2004 4:09:51 PM Info: ============================================
Aug 23, 2004 4:09:51 PM Info: Starting SDM - Software Deployment Manager...
Aug 23, 2004 4:09:53 PM Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.3005.00.0000.20040414093518.0000
Aug 23, 2004 4:09:55 PM Info: SDM operation mode successfully set to: Standalone
Aug 23, 2004 4:09:57 PM Info: Initializing Network Manager (50017)
Aug 23, 2004 4:09:59 PM Info: Checking if another SDM is running on port 50018
Aug 23, 2004 4:09:59 PM Info: -
Starting deployment -
Aug 23, 2004 4:09:59 PM Info: Loading selected archives...
Aug 23, 2004 4:09:59 PM Info: Loading archive 'C:\WebAS640_Java_SP5\WebAS640SP3toSP5_Patch\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS05_0.SCA'
Aug 23, 2004 4:12:27 PM Info: Selected archives successfully loaded.
Aug 23, 2004 4:12:33 PM Info: Actions per selected component:
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' updates currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133140.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040330113610.0000' updates currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031112163623.0000'.
Aug 23, 2004 4:12:33 PM Info: No action: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000' will not update currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000'.
Aug 23, 2004 4:12:33 PM Info: No action: Selected development component 'tc/SL/UTIL_JDD'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000' will not update currently deployed development component 'tc/SL/UTIL_JDD'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040309120341.0000' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031119160521.0000'.
Aug 23, 2004 4:12:33 PM Info: Initial deployment: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326170320.0000' will be deployed.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031223155421.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' updates currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133140.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322170150.0000' updates currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031007124738.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040413165121.0000' updates currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031210162516.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215150458.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' updates currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031223155421.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' updates currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031223155421.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000' updates currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031103173534.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'tc/SL/UTIL'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000' updates currently deployed development component 'tc/SL/UTIL'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031015103253.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165832.0000' updates currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133611.0000'.
Aug 23, 2004 4:12:33 PM Info: No action: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000' will not update currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000'.
Aug 23, 2004 4:12:35 PM Info: No action: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155127.0000' will not update currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155127.0000'.
Aug 23, 2004 4:12:36 PM Info: Initial deployment: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165540.0000' will be deployed.
Aug 23, 2004 4:12:36 PM Info: No action: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000' will not update currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000'.
Aug 23, 2004 4:12:36 PM Info: Update: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164312.0000' updates currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031001180520.0000'.
Aug 23, 2004 4:12:36 PM Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326170320.0000' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031020134252.0000'.
Aug 23, 2004 4:12:36 PM Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040415171020.0000' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031125134518.0000'.
Aug 23, 2004 4:12:37 PM Info: Update: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164521.0000' updates currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031007125447.0000'.
Aug 23, 2004 4:12:37 PM Info: Update: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040413165121.0000' updates currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031210162516.0000'.
Aug 23, 2004 4:12:37 PM Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000'.
Aug 23, 2004 4:12:37 PM Info: Initial deployment: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will be deployed.
Aug 23, 2004 4:12:37 PM Info: Update: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' updates currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133140.0000'.
Aug 23, 2004 4:12:37 PM Info: No action: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
Aug 23, 2004 4:12:37 PM Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031007124656.0000'.
Aug 23, 2004 4:12:37 PM Info: Update: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' updates currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133140.0000'.
Aug 23, 2004 4:12:37 PM Info: Update: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.30.5.0.20040420063500' updates currently deployed software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'3.20040113043717'.
Aug 23, 2004 4:12:37 PM Info: Update: Selected development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' updates currently deployed development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.3003.00.0000.20040108174709.0000'.
Aug 23, 2004 4:12:38 PM Info: Update: Selected development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' updates currently deployed development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.3003.00.0000.20040108174709.0000'.
Aug 23, 2004 4:12:38 PM Info: No action: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
Aug 23, 2004 4:12:38 PM Info: Update: Selected development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164312.0000' updates currently deployed development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031001180520.0000'.
Aug 23, 2004 4:12:38 PM Info: Update: Selected development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155127.0000' updates currently deployed development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031119155233.0000'.
Aug 23, 2004 4:12:38 PM Info: Initial deployment: Selected development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165540.0000' will be deployed.
Aug 23, 2004 4:12:38 PM Info: Update: Selected development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164151.0000' updates currently deployed development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031007124708.0000'.
Aug 23, 2004 4:12:38 PM Info: Update: Selected development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164054.0000' updates currently deployed development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.3003.00.0000.20040112231712'.
Aug 23, 2004 4:12:38 PM Info: Update: Selected development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164228.0000' updates currently deployed development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031001181052.0000'.
Aug 23, 2004 4:12:39 PM Info: Initial deployment: Selected development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165855.0000' will be deployed.
Aug 23, 2004 4:12:39 PM Info: Update: Selected development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' updates currently deployed development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133140.0000'.
Aug 23, 2004 4:12:39 PM Info: Update: Selected development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165842.0000' updates currently deployed development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133723.0000'.
Aug 23, 2004 4:12:39 PM Info: Update: Selected development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040415171020.0000' updates currently deployed development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031125134518.0000'.
Aug 23, 2004 4:12:39 PM Info: Update: Selected development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163618.0000' updates currently deployed development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031001180219.0000'.
Aug 23, 2004 4:12:39 PM Info: Update: Selected development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165540.0000' updates currently deployed development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031218123529.0000'.
Aug 23, 2004 4:12:39 PM Info: Update: Selected development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164521.0000' updates currently deployed development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031007125447.0000'.
Aug 23, 2004 4:12:39 PM Info: Update: Selected development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322170316.0000' updates currently deployed development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031007124545.0000'.
Aug 23, 2004 4:12:40 PM Info: Update: Selected development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' updates currently deployed development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133140.0000'.
Aug 23, 2004 4:12:40 PM Info: Update: Selected development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326170320.0000' updates currently deployed development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031020134252.0000'.
Aug 23, 2004 4:12:40 PM Info: Update: Selected development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155021.0000' updates currently deployed development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031117101211.0000'.
Aug 23, 2004 4:12:40 PM Info: Update: Selected development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' updates currently deployed development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.3003.00.0000.20040108174709.0000'.
Aug 23, 2004 4:12:40 PM Info: Update: Selected development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000' updates currently deployed development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031103173534.0000'.
Aug 23, 2004 4:12:40 PM Info: Update: Selected development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' updates currently deployed development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.3003.00.0000.20040108174709.0000'.
Aug 23, 2004 4:12:53 PM Error: An error occured while storing the cluster instances!
Aug 23, 2004 4:12:53 PM Error: JStartup Framework is not able to deliver an information about the cluster control instances!
Please check the status of the J2EE Engine
Aug 23, 2004 4:12:53 PM Error: Received exception when saving current Engine state: JStartup Framework is not able to deliver an information about the cluster control instances!
Please check the status of the J2EE Engine
Aug 23, 2004 4:12:53 PM Info: Error handling strategy: OnErrorStop
Aug 23, 2004 4:12:53 PM Info: Update strategy: UpdateLowerVersions
Aug 23, 2004 4:12:53 PM Info: Starting: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215150458.0000'.
Aug 23, 2004 4:12:53 PM Info: SDA to be deployed: D:\usr\sap\P64\JC00\SDM\root\origin\sap.com\SQLTrace\SAP AG\6.3005.00.0000.20040401154008.0000\SQLTrace.ear
Aug 23, 2004 4:12:53 PM Info: Software type of SDA: J2EE
Aug 23, 2004 4:12:59 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Aug 23, 2004 4:13:00 PM Info: Starting cluster instance processes.
Aug 23, 2004 4:13:00 PM Error: An error occured while starting a cluster instance!
Aug 23, 2004 4:13:00 PM Error: JStartup Framework is not able to deliver an information about the cluster control instances!
Please check the status of the J2EE Engine
Aug 23, 2004 4:13:00 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Aug 23, 2004 4:13:00 PM Error: Aborted: development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000':
SDM could not start the J2EE cluster on the host aol! The online deployment is terminated.
JStartup Framework is not able to deliver an information about the cluster control instances!
Please check the status of the J2EE Engine
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Aug 23, 2004 4:13:01 PM Error: An error occured while restoring the cluster instances states
Aug 23, 2004 4:13:01 PM Error: JStartup Framework is not able to deliver an information about the cluster control instances!
Please check the status of the J2EE Engine
Aug 23, 2004 4:13:01 PM Error: Received exception when restoring Engine state: JStartup Framework is not able to deliver an information about the cluster control instances!
Please check the status of the J2EE Engine
Aug 23, 2004 4:13:01 PM Info: -
Deployment was successful -
Aug 23, 2004 4:13:02 PM Info: Summarizing the deployment results:
Aug 23, 2004 4:13:02 PM Error: Admitted: C:\WebAS640_Java_SP5\WebAS640SP3toSP5_Patch\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS05_0.SCA
Aug 23, 2004 4:13:02 PM Error: Processing error. Return code: 4
Appreciate your prompt help.
Thanks.
Nirmal

Hi,
I am getting the folloing error message now : below is the log file :
Aug 24, 2004 2:36:53 PM Info: Start logging to console
Aug 24, 2004 2:36:53 PM Info:
Aug 24, 2004 2:36:53 PM Info: ============================================
Aug 24, 2004 2:36:53 PM Info: = Starting to execute command 'deploy' =
Aug 24, 2004 2:36:53 PM Info: ============================================
Aug 24, 2004 2:36:53 PM Info: Starting SDM - Software Deployment Manager...
Aug 24, 2004 2:36:54 PM Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.3005.00.0000.20040414093518.0000
Aug 24, 2004 2:36:56 PM Info: SDM operation mode successfully set to: Standalone
Aug 24, 2004 2:36:57 PM Info: Initializing Network Manager (50017)
Aug 24, 2004 2:36:57 PM Info: Checking if another SDM is running on port 50018
Aug 24, 2004 2:36:57 PM Info: -
Starting deployment -
Aug 24, 2004 2:36:58 PM Info: Loading selected archives...
Aug 24, 2004 2:36:58 PM Info: Loading archive 'C:\WebAS640_Java_SP5\WebAS640SP3toSP5_Patch\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS05_0.SCA'
Aug 24, 2004 2:37:17 PM Info: Selected archives successfully loaded.
Aug 24, 2004 2:37:22 PM Info: Actions per selected component:
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' will not update currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040330113610.0000' will not update currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040330113610.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000' will not update currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'tc/SL/UTIL_JDD'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000' will not update currently deployed development component 'tc/SL/UTIL_JDD'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000'.
Aug 24, 2004 2:37:22 PM Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040309120341.0000' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031119160521.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
Aug 24, 2004 2:37:22 PM Info: Initial deployment: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326170320.0000' will be deployed.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' will not update currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322170150.0000' will not update currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322170150.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040413165121.0000' will not update currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040413165121.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000' will not update currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000' will not update currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'tc/SL/UTIL'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000' will not update currently deployed development component 'tc/SL/UTIL'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165832.0000' will not update currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165832.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000' will not update currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155127.0000' will not update currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155127.0000'.
Aug 24, 2004 2:37:22 PM Info: Initial deployment: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165540.0000' will be deployed.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000' will not update currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000'.
Aug 24, 2004 2:37:22 PM Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326170320.0000' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031020134252.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164312.0000' will not update currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164312.0000'.
Aug 24, 2004 2:37:22 PM Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040415171020.0000' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031125134518.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164521.0000' will not update currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164521.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040413165121.0000' will not update currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040413165121.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000'.
Aug 24, 2004 2:37:23 PM Info: Initial deployment: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will be deployed.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' will not update currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000' will not update currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' will not update currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000'.
Aug 24, 2004 2:37:23 PM Info: Update: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.30.5.0.20040420063500' updates currently deployed software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'3.20040113043717'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will not update currently deployed development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will not update currently deployed development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164312.0000' will not update currently deployed development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164312.0000'.
Aug 24, 2004 2:37:23 PM Info: Update: Selected development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155127.0000' updates currently deployed development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031119155233.0000'.
Aug 24, 2004 2:37:23 PM Info: Initial deployment: Selected development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165540.0000' will be deployed.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164151.0000' will not update currently deployed development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164151.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164054.0000' will not update currently deployed development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164054.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164228.0000' will not update currently deployed development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164228.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165855.0000' will not update currently deployed development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165855.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' will not update currently deployed development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165842.0000' will not update currently deployed development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165842.0000'.
Aug 24, 2004 2:37:23 PM Info: Update: Selected development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040415171020.0000' updates currently deployed development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031125134518.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163618.0000' will not update currently deployed development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163618.0000'.
Aug 24, 2004 2:37:23 PM Info: Update: Selected development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165540.0000' updates currently deployed development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031218123529.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164521.0000' will not update currently deployed development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164521.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' will not update currently deployed development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000'.
Aug 24, 2004 2:37:23 PM Info: Update: Selected development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326170320.0000' updates currently deployed development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031020134252.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322170316.0000' will not update currently deployed development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322170316.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155021.0000' will not update currently deployed development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155021.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will not update currently deployed development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will not update currently deployed development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000' will not update currently deployed development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000'.
Aug 24, 2004 2:37:23 PM Error: Could not create JStartupClusterController: No route to host: connect Throwable: java.net.NoRouteToHostException Throwable message: No route to host: connect
Aug 24, 2004 2:37:23 PM Error: Received exception when saving current Engine state: Could not create JStartupClusterController: No route to host: connect
Aug 24, 2004 2:37:24 PM Info: Error handling strategy: OnErrorStopAug 24, 2004 2:37:24 PM Info: Update strategy: UpdateLowerVersions
Aug 24, 2004 2:37:24 PM Info: Starting: Initial deployment: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will be deployed.
Aug 24, 2004 2:37:24 PM Info: SDA to be deployed: D:\usr\sap\P64\JC00\SDM\root\origin\sap.com\tc\monitoring\systeminfo\SAP AG\6.3005.00.0000.20040419174536.0000\SystemInfo.ear
Aug 24, 2004 2:37:24 PM Info: Software type of SDA: J2EE
Aug 24, 2004 2:37:25 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Aug 24, 2004 2:37:28 PM Error: Could not create JStartupClusterController: No route to host: connect Throwable: java.net.NoRouteToHostException Throwable message: No route to host: connect
Aug 24, 2004 2:37:28 PM Info: No information about the J2EE engine cluster is available.
The online deployment process is continuing.
Aug 24, 2004 2:37:30 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Aug 24, 2004 2:37:30 PM Error: Aborted: development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000':
Caught exception while checking the login credentials from SAP J2EE Engine's deploy API:
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [aol] with UserName: [Administrator]
 Check your Login Info.
 Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext instance.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
Aug 24, 2004 2:37:30 PM Error: Could not create JStartupClusterController: No route to host: connect Throwable: java.net.NoRouteToHostException Throwable message: No route to host: connect
Aug 24, 2004 2:37:30 PM Error: Received exception when restoring Engine state: Could not create JStartupClusterController: No route to host: connect
Aug 24, 2004 2:37:31 PM Info: -
Deployment was successful -
Aug 24, 2004 2:37:31 PM Info: Summarizing the deployment results:
Aug 24, 2004 2:37:31 PM Error: Admitted: C:\WebAS640_Java_SP5\WebAS640SP3toSP5_Patch\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS05_0.SCA
Aug 24, 2004 2:37:31 PM Error: Processing error. Return code: 4

Upgrade from SAP BO 3.1 SP3 to SAP BO 3.1 SP5

Hi
We are doing upgrade from SAP BO 3.1 SP3 to SAP BO 3.1 SP5, can you please help in below points
1. How much time does it take to run SP5 upgrade service pack for servers and client tools. The server need to be upgraded only on weekend, is it possible to upgrade in 1.5 days?
2. The OS is Windows 2008 server. what should be the rollback plan in case of upgrade failure ? One of server uses VM image while Production server doesnt have any VM image.
3. If BO client tools are on SP3, can they still connect to BO server components on SP5 - (for interim period when servers are upgraded first)
Thanks
anu

Hi Anu,
1. The upgarde should be completed in 1.5 days for the server and client componenets depending upon the number of servers you have in the cluster . If you are planning for upgarde do it successfully first on TEST , DEV and then proceed with PROD servers
2. The roll back plan includes thebackup of the CMS database , the filestore directory and the complete installation folder . In case of any issue , you can the place the backup . If the servers are on the VM , it is always recommeded to have the snapshot of the images before the upgrade
3. Yes, they can connect to the SP3 servers , but always recommeded to upgarde and have servers and client tools on same patch .
Thanks,
Sneha

Upgrading of WLS 6.1 from SP3 to SP5

Can anyone help me.
I am going to upgrade WLS 6.1 from SP3 to SP5.
How can i do this ?
From where do i download the ServicePack (SP5) ?
Is there someting i have to be aware off, about the license ?

Hi Paul
This is a JVM bug, Upgrade to 1.3.1_08 jvm from sun
Contact weblogic support for temporary workaround
Paul Wilson wrote:
We've a client running 6.1 sp2 on Solaris, who is experiencing
Weblogic hanging for roughly 10 minutes at a time. On resumption they
get:
####<06-May-03 16:28:50 BST> <Critical> <WebLogicServer> <edox>
<Mendel> <ListenThread> <system> <> <000204> <Failed to listen on port
80, failure count: 1, failing for 1,052,234,928 seconds,
java.net.SocketException: Software caused connection abort>
####<06-May-03 16:28:51 BST> <Notice> <WebLogicServer> <edox> <Mendel>
<ListenThread> <system> <> <000205> <After having failed to listen,
the server is now listening on port 80>
The last time it occurred, I got them to take a thread dump and all
but one execution thread and the listener threads were idle. One
execution thread was busy reloading (or loading) a class from the war.
I've asked them to ensure that the reload period is -1, but that
shouldn't cause a 10 minute hang; plus nothing had changed. Red
herring?
As an experiment I wrote a servlet that just blocks its execution
thread: after about a thousand calls to this on our dev box, we get
<May 14, 2003 5:45:42 PM BST> <Critical> <WebLogicServer> <Failed to
listen on port 6001, failure count: 3, failing for 1,052,930,739
seconds, java.net.SocketException: Too many open files>
AFAIK this means that we've run out of file descriptors. Our client
doesn't get this, so I don't think that is happening to them.
A number of people on weblogic.* groups reported similar problems
about a year ago, but without any really definitive resolutions.
Anyone solved this, even by upgrading?

Need new license for upgrade of Sun Web 6.1 SP3 to SP5?

I want to update my Sun Java System Web Server 6.1 2004Q3 SP3 to Sun Java System Web Server (Multi-Platform) 6.1 SP5 International Edition (essentially going from 6.1 SP3 to SP5). Will this version work with the license that I purchased last November 2005? It seems some of these downloads have a trial license that expires, since it is a full-install rather than just an upgrade piece.

None of the Web Server 6.1 downloads are crippled or time bombed in any way. If you have a license for 6.1, you can (and should!) apply the latest 6.1 service pack without purchasing an additional license.
The 6.1 service pack downloads can be used for new installations or to upgrade an existing 6.1 installation. To upgrade an existing installation, run the setup program and instruct it to install to the directory that contains the existing installation.

Application starts and works with SP3 but SP5 throws this error when starting up

See attached, any help would be greatly appreciated.
Thanks,
Don
[hs_err_pid6776.log]

Hi
Welcome to Apple discussions
My first iBook suffered from persistent KPs on start up. Eventually I resolved the issue by cleaning the cache files. There are a number of cheap/free share ware apps. My favourite is Tiger (or Leopard) Cache Cleaner from here: http://www.northernsoftworks.com/
For more general info on resolving KPs, try here: http://www.thexlab.com/faqs/kernelpanics.html
Good luck
Bob

JAX-WS Client throws NULL Pointer Exception in NW 7.1 SP3 and higher

All,
My JAX-WS client is throwing an exception when attempting to create a client to connect to the calculation service. The exception is coming out of the core JAX-WS classes that are part of NetWeaver. (see exception below)
Caused by: java.lang.NullPointerException
 at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.createDispatchContextExistingPort(SAPServiceDelegate.java:440)
 at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.createDispatchContext(SAPServiceDelegate.java:475)
 at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.createDispatch(SAPServiceDelegate.java:492)
 at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.createDispatch(SAPServiceDelegate.java:484)
 at javax.xml.ws.Service.createDispatch(Service.java:166)
I have done some research and it appears that as of NetWeaver 7.1 SP3 SAP stopped using the SUN JAX-WS runtime and implemented their own SAP JAX-WS runtime. I also took the time to decompile the jar file that contained the SAPServiceDelegate class which is throwing the null pointer exception. (see method from SAPServiceDelegate below)
 private ClientConfigurationContext createDispatchContextExistingPort(QName portName, JAXBContext jaxbContext)
 BindingData bindingData;
 InterfaceMapping interfaceMap;
 InterfaceData interfaceData;
 bindingData = clientServiceCtx.getServiceData().getBindingData(portName);
 if(bindingData == null)
 throw new WebServiceException((new StringBuilder()).append("Binding data '").append(portName.toString()).append("' is missing!").toString());
 QName bindingQName = new QName(bindingData.getBindingNamespace(), bindingData.getBindingName());
 interfaceMap = getInterfaceMapping(bindingQName, clientServiceCtx);
 interfaceData = getInterfaceData(interfaceMap.getPortType());
 ClientConfigurationContext result = DynamicServiceImpl.createClientConfiguration(bindingData, interfaceData, interfaceMap, null, jaxbContext, getClass().getClassLoader(), clientServiceCtx, new SOAPTransportBinding(), false, 1);
 return result;
 WebserviceClientException x;
 x;
 throw new WebServiceException(x);
The exception is being throw on the line where the interfaceMap.getPortType() is being passed into the getInterfaceData method. I checked the getInterfaceMapping method which returns the interfaceMap (line above the line throwing the exception). This method returns NULL if an interface cannot be found. (see getInterfaceMapping method below)
 public static InterfaceMapping getInterfaceMapping(QName bindingQName, ClientServiceContext context)
 InterfaceMapping interfaces[] = context.getMappingRules().getInterface();
 for(int i = 0; i < interfaces.length; i++)
 if(bindingQName.equals(interfaces.getBindingQName()))
 return interfaces;
 return null;
What appears to be happening is that the getInterfaceMapping method returns NULL then the next line in the createDispatchContextExistingPort method attempts to call the getPortType() method on a NULL and throws the Null Pointer Exception.
I have included the code we use to create a client below. It works fine on all the platforms we support with the exception of NetWeaver 7.1 SP3 and higher (I already checked SP5 as well)
 //Create URL for service WSDL
 URL serviceURL = new URL(null, wsEndpointWSDL);
 //create service qname
 QName serviceQName = new QName(targetNamespace, "WSService");
 //create port qname
 QName portQName = new QName(targetNamespace, "WSPortName");
 //create service
 Service service = Service.create(serviceURL, serviceQName);
 //create dispatch on port
 serviceDispatch = service.createDispatch(portQName, Source.class, Service.Mode.PAYLOAD);
What do I need to change in order to create a JAX-WS dispatch client on top of the SAP JAX-WS runtime?

Hi Guys,
I am getting the same error. Any resolution or updates on this.
Were you able to fix this error.
Thanks,
Yomesh

[BO XI 3.1] BO Designer not starting after installing SP5

Hello All!
I installed SP5 on top of BO XI 3.1 SP3 (Windows Server 2008 R2 64bit) on server. There is an issue that Designer is not starting. The process designer.exe shows up in "Task manager" for 1-2 second and disappear. No entries in Event Viewer and in BO logs. I also installed SP5 on client desktop machine and the same happens.
Do you have any tips/advices? Thanks for that!
Bartosz

Hello,
we are not aware of such type of problem and it is most likely something peculiar to the configuration or architecture of your deployment.
I would analyze trace logs from Designer and from Process Monitor ( [http://technet.microsoft.com/en-us/sysinternals/bb896645] )
My advice is to open a support message because is a complicated investigation that probably will need some remote support as well
Thanks
Best regards,
Simone

Problem in Installation of SAP Netweaver CE 7.1 SP3

Hi,
I am trying to install SAP Netweaver CE 7.1 SP3 on Windows XP Professional. All the steps are executed sucessfully till Step 26 where it gives an error when it tries to
"Creating SAP start service of instance CE1 SCS01"
It says that the "Service didn't come up in 40 seconds" and if you retry the installation is terminated in 1 min with the error :
Selfextractor error
iaextract.c:888: child has signaled an exec error. Keeping directory C:/DOCUME1/I047488/LOCALS1/Temp/sapinst_exe.2620.1195815840
In the SAP MMC only one server can be seen with the processes;
msg_server.exe
enserver.exe
gwrd.exe
All these processes are running in green.
Please reply ASAP.
The last part of the sapinstdev_log is :
TRACE 2007-11-23 16:56:02.317
NWInstance.getSAPLocExeDir() done: C:/usr/sap/CE1/SYS/exe/uc/NTI386
TRACE 2007-11-23 16:56:02.317
NWInstanceInstall.createServiceWindows(): going to run <C:\usr\sap\CE1
\SYS\exe\uc\NTI386\sapstartsrv.exe -stdin> with input <-r -q -p C:\usr\sap\CE1\SYS\profile\CE1_SCS01_AGRD50051628A -s CE1 -n 01 -U "NT Authority\LocalService" -P "XXXXXX" -e SAP_ALL\I047488>
TRACE 2007-11-23 16:56:02.317
lognode: undefined, append: false
INFO 2007-11-23 16:56:02.348 [synxcpath.cpp:815]
 CSyPath::createFile() lib=syslib module=syslib
Creating file C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\sapstartsrv.exe.log.
TRACE 2007-11-23 16:56:02.348 [synxcchapp.cpp:264]
 CSyChildApplicationImpl::doStart() lib=syslib module=syslib
Going to call CreateProcess/CreateProcessAsUser for 'C:\usr\sap\CE1\SYS\exe\uc\NTI386\sapstartsrv.exe' now.
TRACE 2007-11-23 16:56:02.348 [synxcchapp.cpp:560]
 CSyChildApplicationImpl::doStart() lib=syslib module=syslib
Trying to start C:\usr\sap\CE1\SYS\exe\uc\NTI386\sapstartsrv.exe using CreateProcess(NULL, <command line for executable C:\usr\sap\CE1\SYS\exe\uc\NTI386\sapstartsrv.exe, NULL, NULL, TRUE, 0x420, NULL, NULL, &StartupInfo, &ProcessInfo)
TRACE 2007-11-23 16:56:02.535 [synxcchapp.cpp:638]
 CSyChildApplicationImpl::doStart() lib=syslib module=syslib
A child process has been started. Pid = 2480. Executable name: C:\usr\sap\CE1\SYS\exe\uc\NTI386\sapstartsrv.exe
INFO 2007-11-23 16:56:02.535
 CJSlibModule::writeInfo_impl()
Output of C:\usr\sap\CE1\SYS\exe\uc\NTI386\sapstartsrv.exe -stdin is written to the logfile sapstartsrv.exe.log.
TRACE 2007-11-23 16:56:45.170 [synxcpipe.cpp:195]
 CSyStdOutErrPipe::onUnderflow(void * buf, int maxBytes, int timeout)
 lib=syslib module=syslib
Syslib info about system call. OS message 109 (The pipe has been ended.
) after execution of system call 'ReadFile' with parameter ((read end of child process output pipe)), line (403) in file (synxcpipe.cpp).
WARNING 2007-11-23 16:56:45.170
 CJSlibModule::writeWarning_impl()
Execution of the command "C:\usr\sap\CE1\SYS\exe\uc\NTI386\sapstartsrv.exe -stdin" finished with return code -1. Output:
Service not started within 40 seconds.
TRACE 2007-11-23 16:56:45.170
NWInstance.getSAPLocExeDir()
TRACE 2007-11-23 16:56:45.170
NWInstance.getProfiles()
TRACE 2007-11-23 16:56:45.170
NWInstance.getProfiles(): profiles object exists
TRACE 2007-11-23 16:56:45.170
NWInstance.getProfiles() done
TRACE 2007-11-23 16:56:45.170
NWProfiles(CE1.SCS01).getProfile()
TRACE 2007-11-23 16:56:45.170
NWProfiles(CE1.SCS01)._getProfile(INSTANCE)
TRACE 2007-11-23 16:56:45.170
NWProfiles(CE1.SCS01).getPersistentDefaultProfile()
TRACE 2007-11-23 16:56:45.170
NW.getPersistentDefaultProfile()
TRACE 2007-11-23 16:56:45.186
NW.isUnicode(true)
TRACE 2007-11-23 16:56:45.186
NW.isUnicode() done: true
TRACE 2007-11-23 16:56:45.186
NW.getPersistentDefaultProfile() done
TRACE 2007-11-23 16:56:45.186
NWProfiles(CE1.SCS01).getPersistentDefaultProfile() done
TRACE 2007-11-23 16:56:45.201
NWProfiles(CE1.SCS01)._getPersistentProfile(INSTANCE)
TRACE 2007-11-23 16:56:45.217
NWProfiles(CE1.SCS01).getPersistentDefaultProfile()
TRACE 2007-11-23 16:56:45.217
NW.getPersistentDefaultProfile()
TRACE 2007-11-23 16:56:45.232
NW.isUnicode(true)
TRACE 2007-11-23 16:56:45.232
NW.isUnicode() done: true
TRACE 2007-11-23 16:56:45.232
NW.getPersistentDefaultProfile() done
TRACE 2007-11-23 16:56:45.232
NWProfiles(CE1.SCS01).getPersistentDefaultProfile() done
TRACE 2007-11-23 16:56:45.232
NWProfiles(CE1.SCS01)._getPersistentProfile(INSTANCE) done
TRACE 2007-11-23 16:56:45.264
NWInstance.isAlwaysUnicode()
TRACE 2007-11-23 16:56:45.264
NWInstance.isAlwaysUnicode(SCS)
TRACE 2007-11-23 16:56:45.264
NWInstance.isAlwaysUnicode() done: true
TRACE 2007-11-23 16:56:45.264
NWInstance.isAlwaysUnicode() done: true
TRACE 2007-11-23 16:56:45.264
NWProfiles(CE1.SCS01)._getProfile(INSTANCE) done
TRACE 2007-11-23 16:56:45.264
NWProfiles(CE1.SCS01).getProfile() done
TRACE 2007-11-23 16:56:45.326
NWInstance.getSAPLocExeDir() done: C:/usr/sap/CE1/SYS/exe/uc/NTI386
WARNING[E] 2007-11-23 16:56:45.326
 CJSlibModule::writeError_impl()
MOS-01011 'C:/usr/sap/CE1/SYS/exe/uc/NTI386/sapstartsrv.exe' returned with '-1'.
TRACE 2007-11-23 16:56:45.326 [iaxxejsbas.hpp:408]
 handleException<ESAPinstJSError>()
Converting exception into JS Exception EJSException.
TRACE 2007-11-23 16:56:45.326
Function setMessageIdOfExceptionMessage: osmod.applicationReturn
WARNING[E] 2007-11-23 16:56:45.326
 CJSlibModule::writeError_impl()
MOS-01011 'C:/usr/sap/CE1/SYS/exe/uc/NTI386/sapstartsrv.exe' returned with '-1'.
TRACE 2007-11-23 16:56:45.326 [iaxxejsbas.hpp:483]
 EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
ERROR 2007-11-23 16:56:45.357 [sixxcstepexecute.cpp:891]
FCO-00011 The step createService with step key |CE_DevSystem_App|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_Instance|ind|ind|ind|ind|1|0|createService was executed with status ERROR .
TRACE 2007-11-23 16:56:45.373 [iaxxgenimp.cpp:761]
 CGuiEngineImp::showMessageBox
<html> <head> </head> <body> An error occurred while processing service SAP NetWeaver CE Developer Edition > SAP NetWeaver CE Development System. You may now <ul> <li> choose Retry to repeat the current step. </li> <li> choose View Log to get more information about the error. </li> <li> stop the task and continue with it later. </li> </ul> Log files are written to C:\Program Files/sapinst_instdir/CE71_DEV_ADA/INSTALL. </body></html>
TRACE 2007-11-23 16:56:45.373 [iaxxgenimp.cpp:1257]
 CGuiEngineImp::acceptAnswerForBlockingRequest
waiting for an answer from gui

Hi All,
I faced the same problem on WinXP Pro SP2, SP3 and on Win2k3Server although all the installation requirements are fulfilled. I have the same problem with SP5 downloaded from SDN which was released recently.
I could install successfully SP1(Trial Version) from a DVD that came with the book "Developer's Guide to SAP NetWeaver Composite Environment". This was packaged using "Install Anywhere".
So, I think it is a problem with SAPInst. Could anyone help to solve this problem?
Your suggestion is highly appreciated.
Thanks & Regards - Tarini P Mohanty

Nw 6.0 sp5 Bm 3.7 sp3

Similar Messages

Maybe you are looking for