cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Sneak Preview Installation Error at "Deploy Online" Step (SQL Syntax Error)

Go to solution
Former Member

on ‎12-30-2004 12:20 AM

0 Kudos

Hi with problems again

As suggested in an earlier thread, I upgraded to <b>768 MB</b> RAM and <b>Java SDK 1.4.2_06</b>. I have an <b>MS Windows XP Professional Service Pack 2</b> system.

At the last step <b>"Deploy Online" of Sneak Preview Installation</b>, I encountered the error with the following log entry. I tried to deploy related archive manually from the SDM, but it gave the same error. Can anybody help me on this?

I wanna welcome the new year with NW

Happy new year...

*--Serdar

<u><b>Log Entry:</b></u>

Dec 30, 2004 2:02:14 AM Info: Start logging to console

Dec 30, 2004 2:02:14 AM Info:

Dec 30, 2004 2:02:14 AM Info: ============================================

Dec 30, 2004 2:02:14 AM Info: = Starting to execute command 'deploy' =

Dec 30, 2004 2:02:14 AM Info: ============================================

Dec 30, 2004 2:02:14 AM Info: Starting SDM - Software Deployment Manager...

Dec 30, 2004 2:02:15 AM Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.3004.00.0000.20040204183620.0000

Dec 30, 2004 2:02:16 AM Info: SDM operation mode successfully set to: Standalone

Dec 30, 2004 2:02:17 AM Info: Initializing Network Manager (50017)

Dec 30, 2004 2:02:17 AM Info: Checking if another SDM is running on port 50018

Dec 30, 2004 2:02:17 AM Info: -

Starting deployment -

Dec 30, 2004 2:02:18 AM Info: Loading selected archives...

Dec 30, 2004 2:02:18 AM Info: Loading archive 'D:\SAPWAS640\SAPinst_WAS\J2EE-CD\J2EE-ENG\ONLINE\SAPJTECHS04_0.SCA'

Dec 30, 2004 2:02:25 AM Info: Selected archives successfully loaded.

Dec 30, 2004 2:02:26 AM Info: Actions per selected component:

Dec 30, 2004 2:02:26 AM Info: development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040203163559.0000': useexisting

Dec 30, 2004 2:02:26 AM Info: development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040120173557.0000': useexisting

Dec 30, 2004 2:02:26 AM Info: development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040120173557.0000': useexisting

Dec 30, 2004 2:02:26 AM Info: development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040203163504.0000': useexisting

Dec 30, 2004 2:02:26 AM Info: development component 'tc/SL/UTIL_JDD'/'sap.com'/'SAP AG'/'6.3004.00.0000.20031022133109.0000': useexisting

Dec 30, 2004 2:02:26 AM Info: software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.30.4.0.20040212152521': deploy

Dec 30, 2004 2:02:26 AM Info: development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040205154547.0000': useexisting

Dec 30, 2004 2:02:26 AM Info: development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040205154547.0000': useexisting

Dec 30, 2004 2:02:26 AM Info: development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204183559.0000': useexisting

Dec 30, 2004 2:02:26 AM Info: development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204183559.0000': useexisting

Dec 30, 2004 2:02:26 AM Info: development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.3004.00.0000.20031118214805.0000': useexisting

Dec 30, 2004 2:02:26 AM Info: development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204185252.0000': deploy

Dec 30, 2004 2:02:26 AM Info: development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040203164404.0000': useexisting

Dec 30, 2004 2:02:26 AM Info: development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040120173557.0000': useexisting

Dec 30, 2004 2:02:26 AM Info: development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040203162838.0000': useexisting

Dec 30, 2004 2:02:26 AM Info: development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.3004.00.0000.20031008103221.0000': useexisting

Dec 30, 2004 2:02:26 AM Info: development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040128131819.0000': useexisting

Dec 30, 2004 2:02:26 AM Info: development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204183559.0000': useexisting

Dec 30, 2004 2:02:26 AM Info: development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204181929.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204183559.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040120173557.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040203163504.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: development component 'tc/SL/UTIL'/'sap.com'/'SAP AG'/'6.3004.00.0000.20031022133109.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040203163438.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040120173114.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040205111447.0000': deploy

Dec 30, 2004 2:02:27 AM Info: development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.3004.00.0000.20031118214805.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040114175434.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040203162810.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040203162810.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204185252.0000': deploy

Dec 30, 2004 2:02:27 AM Info: development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040114175417.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040114180217.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204185252.0000': deploy

Dec 30, 2004 2:02:27 AM Info: development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040205111447.0000': deploy

Dec 30, 2004 2:02:27 AM Info: development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040120173557.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040114175417.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: development component 'synclog'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204181929.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040205154547.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040203163504.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040120173557.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204183559.0000': useexisting

Dec 30, 2004 2:02:27 AM Info: SDM configuration: Do not automatically start/stop J2EE Engine. Do not save current state of J2EE Engine now.

Dec 30, 2004 2:02:27 AM Info: Error handling strategy: OnErrorStop

Dec 30, 2004 2:02:27 AM Info: Update strategy: UpdateLowerVersions

<b>Dec 30, 2004 2:02:27 AM Info: Starting to execute deployment action (deploy) for "tc/wd/dispwda".

Dec 30, 2004 2:02:27 AM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\dispwda\SAP AG\6.3004.00.0000.20040205111447.0000\WebDynproDispWda.sda

Dec 30, 2004 2:02:27 AM Info: Software type of SDA: J2EE

Dec 30, 2004 2:02:28 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****

Dec 30, 2004 2:03:06 AM Info: Begin of log messages of the target system:

07/10/30 02:02:29 - ***********************************************************

07/10/30 02:02:31 - Start updating EAR file...

07/10/30 02:02:33 - EAR file updated successfully for 1172ms.

07/10/30 02:02:33 - Start deploying ...

07/10/30 02:02:37 - EAR file uploaded to server for 2413ms.

07/10/30 02:03:05 - ERROR: Not deployed. Deploy Service returned ERROR:

java.rmi.RemoteException: Cannot deploy application sap.com/tcwddispwda..

Reason: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Failed to deploy application sap.com/tcwddispwda. Reason = The SQL statement "insert into TC_WDRR_LAYERS (name, version, predecessor, order_index, deployable_object) values (?,?,?,?,?)" contains the syntax error[s]: Entry-SQL syntax error: a query must start with SELECT

SQL syntax error: the token "TC_WDRR_LAYERS" was not expected here

', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Failed to deploy application sap.com/tcwddispwda. Reason = The SQL statement "insert into TC_WDRR_LAYERS (name, version, predecessor, order_index, deployable_object) values (?,?,?,?,?)" contains the syntax error[s]: Entry-SQL syntax error: a query must start with SELECT

SQL syntax error: the token "TC_WDRR_LAYERS" was not expected here

; nested exception is:

com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Failed to deploy application sap.com/tcwddispwda. Reason = The SQL statement "insert into TC_WDRR_LAYERS (name, version, predecessor, order_index, deployable_object) values (?,?,?,?,?)" contains the syntax error[s]: Entry-SQL syntax error: a query must start with SELECT

SQL syntax error: the token "TC_WDRR_LAYERS" was not expected here

', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Failed to deploy application sap.com/tcwddispwda. Reason = The SQL statement "insert into TC_WDRR_LAYERS (name, version, predecessor, order_index, deployable_object) values (?,?,?,?,?)" contains the syntax error[s]: Entry-SQL syntax error: a query must start with SELECT

SQL syntax error: the token "TC_WDRR_LAYERS" was not expected here

at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:469)</b> at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1511)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:268)

at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:165)

at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:102)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)

at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:140)

Caused by: <b>com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Failed to deploy application sap.com/tcwddispwda. Reason = The SQL statement "insert into TC_WDRR_LAYERS (name, version, predecessor, order_index, deployable_object) values (?,?,?,?,?)" contains the syntax error[s]: Entry-SQL syntax error: a query must start with SELECT

SQL syntax error: the token "TC_WDRR_LAYERS" was not expected here

', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Failed to deploy application sap.com/tcwddispwda. Reason = The SQL statement "insert into TC_WDRR_LAYERS (name, version, predecessor, order_index, deployable_object) values (?,?,?,?,?)" contains the syntax error[s]: Entry-SQL syntax error: a query must start with SELECT

SQL syntax error: the token "TC_WDRR_LAYERS" was not expected here

at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:957)

at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:975)

at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:586)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:332)

at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2945)

at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:454)

... 10 more

For detailed information see the log file of Deploy Service.

07/10/30 02:03:06 - ***********************************************************

Dec 30, 2004 2:03:06 AM Info: End of log messages of the target system.

Dec 30, 2004 2:03:06 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

Dec 30, 2004 2:03:06 AM Error: Execution of deployment action for "tc/wd/dispwda" aborted:

Caught exception during application deployment from SAP J2EE Engine's deploy service:

java.rmi.RemoteException: Cannot deploy application sap.com/tcwddispwda..

Reason: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Failed to deploy application sap.com/tcwddispwda. Reason = The SQL statement "insert into TC_WDRR_LAYERS (name, version, predecessor, order_index, deployable_object) values (?,?,?,?,?)" contains the syntax error[s]: Entry-SQL syntax error: a query must start with SELECT

SQL syntax error: the token "TC_WDRR_LAYERS" was not expected here

', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Failed to deploy application sap.com/tcwddispwda. Reason = The SQL statement "insert into TC_WDRR_LAYERS (name, version, predecessor, order_index, deployable_object) values (?,?,?,?,?)" contains the syntax error[s]: Entry-SQL syntax error: a query must start with SELECT

SQL syntax error: the token "TC_WDRR_LAYERS" was not expected here

; nested exception is:

com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Failed to deploy application sap.com/tcwddispwda. Reason = The SQL statement "insert into TC_WDRR_LAYERS (name, version, predecessor, order_index, deployable_object) values (?,?,?,?,?)" contains the syntax error[s]: Entry-SQL syntax error: a query must start with SELECT

SQL syntax error: the token "TC_WDRR_LAYERS" was not expected here

', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Failed to deploy application sap.com/tcwddispwda. Reason = The SQL statement "insert into TC_WDRR_LAYERS (name, version, predecessor, order_index, deployable_object) values (?,?,?,?,?)" contains the syntax error[s]: Entry-SQL syntax error: a query must start with SELECT

SQL syntax error: the token "TC_WDRR_LAYERS" was not expected here

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)

Dec 30, 2004 2:03:06 AM Error: Deployment NOT successful for tc/wd/dispwda</b>

Dec 30, 2004 2:03:06 AM Info: SDM configuration: Do not automatically start/stop J2EE Engine. Do not restore state of J2EE Engine now.

Dec 30, 2004 2:03:06 AM Info: -

Deployment was successful -

Dec 30, 2004 2:03:06 AM Info: Summarizing the deployment results:

Dec 30, 2004 2:03:06 AM Error: Admitted: D:\SAPWAS640\SAPinst_WAS\J2EE-CD\J2EE-ENG\ONLINE\SAPJTECHS04_0.SCA

Dec 30, 2004 2:03:06 AM Error: Processing error. Return code: 4

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
‎02-10-2005 11:31 PM
0 Kudos

Hi,

regional settings of the machine should be English..

Show replies
Show replies
ssimsekler
Active Contributor
‎02-11-2005 11:34 AM
0 Kudos

Hi Saban

Thanks for the input. I will try it...

ssimsekler
Active Contributor
‎02-11-2005 7:10 PM
0 Kudos

Hi Saban

Thank you very much for helping me to close this damned issue. Never thought of the existence of the key solution at Regional Settings. The installation was successful with no errors.

Thank you very much again...

*--Serdar

Former Member
‎02-12-2005 2:37 PM
0 Kudos

Hi Serdar,

it's great that you got it working finally. Just one small question, because i'm curious: Which regional setting did lead to the broken installation? I've done multiple installations in the past including German, French, US and more and did never encounter such a strange behaviour.

Regards, Stefan

ssimsekler
Active Contributor
‎02-12-2005 8:36 PM
0 Kudos

Hi Stefan

My region was set to 'TR'. It seems SAP does not want to see Turkey in EU either :).

*--Serdar

ssimsekler@yahoo.com

Answers (2)

Answers (2)

Former Member
‎02-09-2005 5:38 AM
0 Kudos

Hi Serdar,

If u want to install the Sneak Preview in Windows XP Environment, u need Service Pack 1 and not two.

Regards,

Sreenivas.

Show replies
Show replies
ssimsekler
Active Contributor
‎02-09-2005 11:55 PM
0 Kudos

Hi Sreenivas

I now have XP system with only SP1, but the same problem persists...

*--Serdar

daniel_davinci
Active Contributor
‎02-10-2005 5:46 AM
0 Kudos

Have you verified that you are not using any special characters in the password?

Regards

Daniel

ssimsekler
Active Contributor
‎02-10-2005 12:11 PM
0 Kudos

Hi Daniel

Yes, my password is a simple password having no special characters. By the way, what may be the relevance of that. Because the log seems to be something about an SQL error...

Anyways, if you insist on the password's relevance, I can try yours (admin123) and tell whether solves the problem sooner .

*--Serdar

daniel_davinci
Active Contributor
‎02-10-2005 1:35 PM
0 Kudos

Hi Serdar,

At least in the early releases of sneak preview using special characters in your passwords caused problems. I have had another look at the error message and it may be that the SQL errors that you are seeing is a red herring.

What state does the MMC indicate the server is in at this point of the install?

If you have not already I would stop the installation (Not reset), reboot the machine and then resume the installation.

Also did you install the correct collation and service packs etc on the database?

There is nothing magic about my password unfortunately. So I doubt that if you are not using special characters that using it will help.. sorry

Off course you are welcome to try!

Cheers

Daniel

P.S. Please consider assigning points if this helps.

Former Member
‎02-10-2005 2:40 PM
0 Kudos

Hi Daniel,

the password error, if your password contains special characters, occurs at the very beginning of the installation. Web Dynpro deployment is definitely <b>not</b> at the very beginning, the complete core services are already deployed then. So imho it's simply impossible, that special password characters are a possible error reason here.

I suggested Serdar to post this in the WD forum, since there seems to be something wrong with the install-script especially regarding WD deployment (an INSERT statement seems to be used instead of a SELECT, which is really weird and TC_WDRR_LAYERS is a table of the Web Dynpro customizing layer). So, sorry, but i don't think, that rebooting will really help here

Regards, Stefan

ssimsekler
Active Contributor
‎02-10-2005 9:45 PM
0 Kudos

Hi

I am afrais Stefan is right. Rebooting does not make any sense.

By the way, whilw installing I inspected the status of J2EE and saw that one of them can not be started (yellow or red), it includes "jcontrol.exe". Couldn't relate with an SQL error, however, does this have a relation with the problem?

*--Serdar

daniel_davinci
Active Contributor
‎02-10-2005 10:14 PM
0 Kudos

Sure it seems unlikely that the password is the problem and it might not make any sense to re-boot the machine.

If you don’t like the suggestions then don’t try them. But if you are stuck now with this problem for days(weeks?) and still not getting past it I would think that it’s worth a try.

In regards to the error that is being shown, I have performed a number of portal installations and many times have encountered errors and know well enough that they do not always point to the exact problem or don’t make a lot of sense at all, in fact many times errors are thrown that the installation passes without issue. The fact that we only look at the log files during an install is when the installation fails could be considered observational selection.

Good luck with getting the issue resolved.

Cheers

Daniel

ssimsekler
Active Contributor
‎02-11-2005 11:33 AM
0 Kudos

Hi Daniel

I didn't mean to break you heart. Your suggestions are always valuable for me. Sorry since I make you misunderstand. But I've tried rebooting and continuing the installation hundred times. That is why, I told that rebooting is not a solution (at least for my case). Anyways, at the end I think I will try to get another installation DVD and try it.

Thank you...

*--Serdar

daniel_davinci
Active Contributor
‎02-12-2005 4:01 AM
0 Kudos

Lets not get carried away.. Broken heart? This is not a valentine day forum is it??

Glad to see the problem is resolved for you.

Cheers

Daniel

ssimsekler
Active Contributor
‎02-06-2005 12:48 AM
0 Kudos

Hi again

Still struggling with the same problem. Any comments???

*--Serdar

Show replies
Show replies
Former Member
‎02-06-2005 9:27 AM
0 Kudos

Hi Serdar,

the problem you are facing is definitely raised by deployment of core Web Dynpro components. I suggest to repost the question in the <a href="https://www.sdn.sap.com/sdn/collaboration.sdn?node=linkFnode2-6&contenttype=url&content=https%3A%2F%2Fforums.sdn.sap.com%2Fforum.jspa%3FforumID%3D52">Web Dynpro forum</a>, maybe one of the internal experts there knows the reason.

Hope that helps.

Regards,

Stefan

ssimsekler
Active Contributor
‎02-06-2005 5:01 PM
0 Kudos

Hi Stefan

OK I will also post about this problem to the forum you've stated. However, it is weird that it seems there is noone faced with this before. Since it is at the installation process, still I have the hope to get an answer here, too.

Thanks...

*--Serdar

daniel_davinci
Active Contributor
‎02-06-2005 9:43 PM
0 Kudos

Hi Serdar,

I agree I believe that this problem is best suited to being posted here.

Take a look at:

Interestingly this problem occurred for this user after changing the memory configuration on the host.

Check that you did not use special characters in your passwords etc.

If you did not then try stopping the installation (not reset) reboot the machine and try again... What happens if you try the "Retry" option in the error dialogue box? In the early installs problems like this could be resolved by hitting the retry option a few times, but there is no sense in doing this if it just throws the same error again and again...

Good luck.

Ask a Question