Problem while updating the Support Package 17 on my SAP WAS SP9

Hi,
I'm facing problem while updating the Support Package 17 on my SAP WAS SP9
ERROR 2006-10-13 10:23:22
FSL-06002 Error 2 (The system cannot find the file specified.
) in execution of a 'CreateProcess' function, line (284), with parameter (java.exe ...).
Please help me in this regard.....
Thanks in advance...
Satya

Hello gentlemen, I am also having problem with the following running on 64 bit Windows and SQL2005/64 bit. I am erroring in Step 8 'Updating JDBC' driver. I am attempting to update from SP9 to SP18. The WEBAS Jave installed went flawless but I seem to be stuck here. Any help is appreciated...
ERROR 2006-11-22 10:13:57
FSL-06002 Error 2 (The system cannot find the file specified.
) in execution of a 'CreateProcess' function, line (284), with parameter (java.exe ...).

Similar Messages

Problem while updating the forecast value in m.master by direct input menth

Hi All
Good Day
I am updating the forecast value in material master by direct input method.
my program is working fine when I am running it online.
but when i am runnig in back ground I am getting one error which is mentioned below
                                                                                Job ZM_OPTIMIZA_UPLOAD: Data does not match the job definition; job terminated    BD    078     E
Please anyone can help ne in above case.
Thanks in advance.
Cheers
Vallabhaneni

Hi Hakim
How are you
Thanks for your valuable suggestion.
I am executing my program in background with bmv0 transaction with variant, in development I can run this job in background with out any logical errors but in QA I am getting errors.
Can you please help me in the above case.
In Bmv0 transaction first I defined the job and in program rmdatind (execute) screen first I mentioned the Max. no of logical errors as 500 and Transactions per commit unit as 500 and I run the program in background in bmv0 transaction and I am getting the message background job terminated immediately
Because of this again I changed the Max. no of logical errors 500 to 99999 and transaction per commit unit 500 to 999999 and then i scheduled my program in background.
Alomost it ran for 27 hours and then it has given the message background job terminated.
Job log entries are as follows.
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:19:46 Transaction 0000040840; material number SUJ82J8400; error gravity E
22.12.2008 11:19:46 Transaction 0000040840: Taxes for sales org. cannot be transferred
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:19:46 Transaction 0000040841; material number SUJ84G3001; error gravity E
22.12.2008 11:19:46 Transaction 0000040841: Taxes for sales org. cannot be transferred
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:19:46 Transaction 0000040842; material number SUJ84G3002; error gravity E
22.12.2008 11:19:46 Transaction 0000040842: Taxes for sales org. cannot be transferred
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:19:46 Transaction 0000040843; material number SUJ86G0100; error gravity E
22.12.2008 11:19:46 Transaction 0000040843: Taxes for sales org. cannot be transferred
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:19:46 Transaction 0000040844; material number SUJ86G0300; error gravity E
22.12.2008 11:19:46 Transaction 0000040844: Taxes for sales org. cannot be transferred
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:19:46 Transaction 0000040845; material number SUJ86G0900; error gravity E
22.12.2008 11:19:46 Transaction 0000040845: Taxes for sales org. cannot be transferred
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:19:46 Transaction 0000040846; material number SUJ86G9600; error gravity E
22.12.2008 11:19:46 Transaction 0000040846: Taxes for sales org. cannot be transferred
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:19:46 Transaction 0000040847; material number SUJ86G9601; error gravity E
22.12.2008 11:19:46 Transaction 0000040847: Taxes for sales org. cannot be transferred
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:19:46 Transaction 0000040848; material number SUJ86J0000; error gravity E
22.12.2008 11:19:46 Transaction 0000040848: Taxes for sales org. cannot be transferred
22.12.2008 11:19:46 A system error has occurred while locking
22.12.2008 11:20:54 Transaction 0000040848 completed Mat. no. No. of log. errors 0000040848
22.12.2008 11:21:30 ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED
22.12.2008 11:21:30 Job cancelled
I know it has taken long time to process the job because of I changed the transactions per commit unit (500 to 999999) it kills the system
But I am supposed to provide some number < 999999 in transactions per commit unit
actually I haven't tried like I said above < 999999 because i don't have any hopes.
Please look at this problem and help me in this case.
Thanks in advance.
Vallabhaneni

Problem while updating the forecast value in m.master by direct input metho

Hi Hakim
Thanks for your prompt response.
Yeah, I can see the same in St22 as you said, If I contaced the basis team for memory extension
is my problem can get solved?
and I will change the Transactions per commit unit to 100 again.
Is there anything else is causing the background job termination
really I couldn't find anything wrong in my program and it is running successfully in development client
and it is giving the message completed and
Job name Last update Current status
ZM_OPTIMIZA_FORECAST 23.12.2008 09:18:47 C Completed: job executed w/o logical errors
ZM_OPTIMIZA_FORECAST 19.12.2008 11:22:31 C Completed: job executed w/o logical errors
ZM_OPTIMIZA_FORECAST 19.12.2008 11:21:20 C Completed: job executed w/o logical errors
and the job log is as follows in development client.
23.12.2008 09:18:47 The field MARA-FORMT is not ready for input and was therefore not initialized
23.12.2008 09:18:47 The field MARA-KUNNR is not ready for input and was therefore not initialized
23.12.2008 09:18:47 The field MARA-MEINS is not ready for input and was therefore not initialized
23.12.2008 09:18:47 The field MARA-PRZUS is not ready for input and was therefore not initialized
23.12.2008 09:18:47 No changes made
23.12.2008 09:18:47 Transaction 0000000004; material number 2210017320; error gravity W
23.12.2008 09:18:47 Transaction 0000000004: Taxes for sales org. cannot be transferred
23.12.2008 09:18:47 Not possible to transfer tax data
23.12.2008 09:18:47 The field MARA-BEGRU is not ready for input and was therefore not initialized
23.12.2008 09:18:47 The field MARA-BMATN is not ready for input and was therefore not initialized
23.12.2008 09:18:47 The field MARA-FERTH is not ready for input and was therefore not initialized
23.12.2008 09:18:47 The field MARA-FORMT is not ready for input and was therefore not initialized
23.12.2008 09:18:47 The field MARA-KUNNR is not ready for input and was therefore not initialized
23.12.2008 09:18:47 The field MARA-MEINS is not ready for input and was therefore not initialized
23.12.2008 09:18:47 The field MARA-PRZUS is not ready for input and was therefore not initialized
23.12.2008 09:18:47 No changes made
23.12.2008 09:18:47 Transaction 0000000005; material number 6777295J01; error gravity W
23.12.2008 09:18:47 Transaction 0000000005: Taxes for sales org. cannot be transferred
23.12.2008 09:18:47 Not possible to transfer tax data
23.12.2008 09:18:47 The field MARA-BEGRU is not ready for input and was therefore not initialized
23.12.2008 09:18:47 The field MARA-BMATN is not ready for input and was therefore not initialized
23.12.2008 09:18:47 The field MARA-FERTH is not ready for input and was therefore not initialized
23.12.2008 09:18:47 The field MARA-FORMT is not ready for input and was therefore not initialized
23.12.2008 09:18:47 The field MARA-KUNNR is not ready for input and was therefore not initialized
23.12.2008 09:18:47 The field MARA-MEINS is not ready for input and was therefore not initialized
23.12.2008 09:18:47 The field MARA-PRZUS is not ready for input and was therefore not initialized
23.12.2008 09:18:47 No changes made
23.12.2008 09:18:47 Transaction 0000000005 completed Mat. no. T6777295J01 No. of log. errors 0000000000
23.12.2008 09:18:47 Data transfer (job 00000007) completed
23.12.2008 09:18:47 No logical (business) errors occurred
23.12.2008 09:18:47 Job finished
But in QA it is behaving totally different like i said in my earlier threat .
Thanks
Vallabhaneni

Hi Nani,
Dont open multiple threads for the same question. Im requesting you to close your threads similar to this thread.Keep only one thread open for the same issue.
Please read the Rules of Engagement in SCN.
Regards,
Hakim

Problem while updating the domain data of CMS

Hi
I am trying configuring the Chage Management Service. When i am clicking on the <b>"update CMS"</b> button which is under CMS > Landscape Configuratore > Domain Data i am getting the following error...
<b>"Unexpected error; inform your system administrator: No object found exception"</b>
How to resolve this problem?
Best Regards
Ravi Shankar

HI
Following are main error i found in log file
<b>Exception in method updateCMSServer
No object found
Could not find clientID</b>
Thanks & Regards
Ravi Shankar B

Problem while updating the records. IN clause no. of items

We have an issue in updating a table when the inside IN more than 1000 numbers are passed ,
it throws error message - ORA-01795 : maximum nunbers of experssions in a list is 1000. Is there any workarround (wihtout using ARRAYs).
experssions list is passed from java.
update <table> c
set c.data='test'
where c.id in (123,345,.... 25,0000 records);We tried this way , it throws error.
DECLARE
txt varchar2(32000):= <Text size 30000>
BEGIN
update <table> c
set c.data='test'
where c.id in (select To_number(REGEXP_SUBSTR (txt, '[^,]+', 1, level)) from dual
connect by level <= regexp_count(txt,',')+1
);thanks in advance..

Hi,
you can use WITH refactoring clause and UNION like shown below:
with gen1 as (select level x from dual connect by level <= 1000),
gen2 as (select level+1000 x from dual connect by level <= 1000),
gen3 as
(select * from gen1
union
select * from gen2)
select * from dual where 1 not in (select x from gen3);Best regards,
Nikolay

& problem while updating the table

SQL> update users set coname='Falcon Minerals & Metals' where co_id=1020;
update users_loc set country='Finland' where co_id=1020;Enter value for metals: old 1: update users set coname='Falcon Minerals & Metals' where co_id=1020
new 1: update users set coname='Falcon Minerals ' where co_id=1020
1 row updated. thanks and best regards

SQL> SET DEFINE OFF

Error while deploying the Bussiness package in CE 7.1 SP5

Hi All,
I am facing the problem while deploying the Bussiness package. The same bussiness package has been deployed on EP 7.0 using SDM. In CE 7.1 while deploying the package we are getting error. Please check the log.
-- Deployment Items -
     1. Client path '
\sapmnt\trans\EPS\in\BPERP5COM03_0-10004453.SCA\DEPLOYARCHIVES\tc~sl.ut.content.erp.bp_erp.sda'
     Sdu info :name 'tc~sl.ut.content.erp.bp_erp', vendor 'sap.com', location 'MAIN_ERP52VAL_C', version '1592825', software type ('J2EE', sub type ''), dependencies :[none]
          Deploy status is 'Aborted'
          Time statistics( ms ):
               1.validate : -1
                    1.1.deployment : 218
                         1.1.1.Notify:Event triggered : 15
                         1.1.2.Disable LCM deployment : 203
                              1.1.2.1.Perform delivery : 203
                                   1.1.2.1.1.Application Deployer : 203
          Description:'1. [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5082] Exception while validating application sap.com/tc~sl.ut.content.erp.bp_erp.
No one of the [developmentserver, com.sap.security.login-modules] containers, which processed it, returned deployed component names.
The registered containers in this moment were [CTCContainer, com.sap.security.ume, developmentserver, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, MigrationContainer, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, SAP-EU-GP, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container].
Possible reasons :
     1.An AS Java service, which is providing a container, is stopped or not deployed.
     2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.'.
I have checked all the services in NWA, they are all running fine but one of the service is not available com.sap.security.login-modules and also in the log file it is saying that nested exeception.
I am Basis consultant i couldnt able to get what is nested exception.
How to undeploy the packages?
In CE there is no SDM is there any alternative tool to undeploy and deploy the Packages like SDM other JSPM.
Please guide on this.
Thanks in Advance.
Mahesh C

Hi,
You can undeploy using the IDE itself.
1. Go to Deploy perspective (Window>open perpective>other-->Deploy)
2. There u can select Deploy view or undeploy view.
Regards,
Srinivasan Subbiah

Problem while executing the package

Hi Guys,
I am getting the problem while executin the package for 1 of the interface named PRE_SYNC_EX_ARMY_VEH_DEL.
The source tables are EX_ARMY_VEH_TMP and CONTROL_DEL & target table is CONTROL_DEL
All the three tables are in the same schema named RTO_STAGE.
I am looking in the operator as at the first session is in the process(running mode) with "DROP FLOW TABLE" as the message while all other sessions are in the waiting mode related to that interface PRE_SYNC_EX_ARMY_VEH_DEL.The previous interface before it ie PRE_SYNC_AXLE_DEL & PRE_SYNC_AXLE_DELNR is running okk(with all succesful session).
**In one statement I can summerize that execution of package is halting/stopped at one interface & not showing error in operator(showing running)**
what would be the problem?
Thanx
Edited by: user8849294 on Mar 1, 2010 10:17 PM
Edited by: user8849294 on Mar 2, 2010 9:36 PM
Edited by: user8849294 on Mar 2, 2010 9:43 PM

Hi,
You didn't mention the exact error.
Did you check if your interface succeeds outside the Package?
If yes, have you included any odiFileWait event which's why other tasks are kept in Wait mode?
In any case, if there's an error, the task with the red-colored icon shows the one with problem. Double-click it & go to the Execution tab to get the exact error

Update Java Support Package Stack in JSPM

Hi all,
When i update Java Support Package Stack in JSPM i can't start the dispatcher
[Thr 920] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 920] **********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
[Thr 920] JLaunchCloseProgram: good bye (exitcode = -11113)
When i goto the log-file of the dispatcher (server.0.log):
E:
usr
sap
P01
DVEBMGS01
j2ee
cluster
dispatcher
bin
services
log_configurator
log_configurator.jar
Loading model: {parent,local,references}
The error occurred while trying to load "com.sap.engine.services.log_configurator.LogInterfaceImpl".
     at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
     at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.init(LogConfiguratorServiceFrameImpl.java:156)
     at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.start(LogConfiguratorServiceFrameImpl.java:127)
     at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:228)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:158)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:82)
     at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:154)
#1.5 #0050569379EA000A00000004000010880004B40696AFED19#1323840297756#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:6]_32##0#0#Error#1#/System/Server#Plain###Core service log_configurator failed. J2EE Engine cannot be started.#
#1.5 #0050569379EA000A00000006000010880004B40696AFF1F0#1323840297756#/System/Server/Critical##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:6]_32##0#0#Fatal#1#com.sap.engine.core.Framework#Plain###Critical shutdown was invoked. Reason is: Core service log_configurator failed. J2EE Engine cannot be started.#
Somebody know how to solve this problem?
Thanks in advance,
Cheung

defaulttrc.0.trc"
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[./log/defaultTrace.trc]/>
<!PATTERN[defaultTrace.trc]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!FILESET[0, 2, 10485760]/>
<!PREVIOUSFILE[defaultTrace.1.trc]/>
<!NEXTFILE[defaultTrace.1.trc]/>
<!LOGHEADER[END]/>
#1.5 #0050569379EA001500000D53000016300004B40029F81C09#1323812703907#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: [ApplicationItem.release]: SAPJ2EE::sap.com/tcwd4vccorestdinfoactors#
#1.5 #0050569379EA001500000D54000016300004B40029F8209A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:506)#
#1.5 #0050569379EA001500000D55000016300004B40029F82100#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:590)#
#1.5 #0050569379EA001500000D56000016300004B40029F82147#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:672)#
#1.5 #0050569379EA001500000D57000016300004B40029F8218D#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)#
#1.5 #0050569379EA001500000D58000016300004B40029F821D1#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)#
#1.5 #0050569379EA001500000D59000016300004B40029F82215#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)#
#1.5 #0050569379EA001500000D5A000016300004B40029F8225A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)#
#1.5 #0050569379EA001500000D5B000016300004B40029F8229E#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:722)#
#1.5 #0050569379EA001500000D5C000016300004B40029F822E4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)#
#1.5 #0050569379EA001500000D5D000016300004B40029F82329#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5 #0050569379EA001500000D5E000016300004B40029F8236C#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
#1.5 #0050569379EA001500000D5F000016300004B40029F823AF#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)#
#1.5 #0050569379EA001500000D60000016300004B40029F823F3#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)#
#1.5 #0050569379EA001500000D61000016300004B40029F826A8#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during stop of application: SAPJ2EE::sap.com/tcwd4vccorestdinfoactors#
#1.5 #0050569379EA001500000D62000016300004B40029F82700#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:162)#
#1.5 #0050569379EA001500000D63000016300004B40029F82747#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:479)#
#1.5 #0050569379EA001500000D64000016300004B40029F8278A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 12 more#
#1.5 #0050569379EA001500000D65000016300004B40029F82AA4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: java.lang.NullPointerException#
#1.5 #0050569379EA001500000D66000016300004B40029F82AF6#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getSAPJ2EEApplicationState(SAPJ2EEPortalRuntime.java:630)#
#1.5 #0050569379EA001500000D67000016300004B40029F82B41#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.service.sapj2ee.Mediator.getSAPJ2EEApplicationState(Mediator.java:216)#
#1.5 #0050569379EA001500000D68000016300004B40029F82B87#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:121)#
#1.5 #0050569379EA001500000D69000016300004B40029F82BCB#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 13 more#
#1.5 #0050569379EA001500000D6A000016300004B40029F82D15#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: [ApplicationItem.release]: SAPJ2EE::sap.com/com.sapportals.connectors.sap#
#1.5 #0050569379EA001500000D6B000016300004B40029F82FE9#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:506)#
#1.5 #0050569379EA001500000D6C000016300004B40029F8303F#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:590)#
#1.5 #0050569379EA001500000D6D000016300004B40029F83085#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:672)#
#1.5 #0050569379EA001500000D6E000016300004B40029F830E5#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)#
#1.5 #0050569379EA001500000D6F000016300004B40029F8312A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)#
#1.5 #0050569379EA001500000D70000016300004B40029F8316F#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)#
#1.5 #0050569379EA001500000D71000016300004B40029F831B4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)#
#1.5 #0050569379EA001500000D72000016300004B40029F831F8#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:722)#
#1.5 #0050569379EA001500000D73000016300004B40029F8323E#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)#
#1.5 #0050569379EA001500000D74000016300004B40029F83283#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5 #0050569379EA001500000D75000016300004B40029F832C9#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
#1.5 #0050569379EA001500000D76000016300004B40029F8330C#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)#
#1.5 #0050569379EA001500000D77000016300004B40029F83350#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)#
#1.5 #0050569379EA001500000D78000016300004B40029F835C4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during stop of application: SAPJ2EE::sap.com/com.sapportals.connectors.sap#
#1.5 #0050569379EA001500000D79000016300004B40029F8361A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:162)#
#1.5 #0050569379EA001500000D7A000016300004B40029F83662#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:479)#
#1.5 #0050569379EA001500000D7B000016300004B40029F836AA#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 12 more#
#1.5 #0050569379EA001500000D7C000016300004B40029F83A09#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: java.lang.NullPointerException#
#1.5 #0050569379EA001500000D7D000016300004B40029F83A67#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getSAPJ2EEApplicationState(SAPJ2EEPortalRuntime.java:630)#
#1.5 #0050569379EA001500000D7E000016300004B40029F83AAF#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.service.sapj2ee.Mediator.getSAPJ2EEApplicationState(Mediator.java:216)#
#1.5 #0050569379EA001500000D7F000016300004B40029F83AF5#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:121)#
#1.5 #0050569379EA001500000D80000016300004B40029F83B3A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 13 more#

"An error occurred while updating the configuration"

I recieved an Apple Airport Base Station in the mail today. I got it second hand, and I performed a hard-reset since I didn't have the password and stuff. I wanted to update it properly before I started using it.
I have followed the guides in here point by point, but all I get when I am trying to connect with the AirPort Admin Utility is the error in the topic: "An error occurred while updating configuration".
I've been surfing and googling for hours now, and can't seem to find the solution to this.
The Base Station has a model no. M8440, and that's all I know about it. First I thought it was the Snow, then the Graphite and now I don't know. The reason I get confused is because I've read about all these different colored lights.
Here's a description of my Base Station - in case someone recognized it, and can help me identify it:
- It's one of those "UFO's"
- It's all white, with a silver Apple-logo
- It's got three ports: Modem, WAN and LAN
- It's got three lights - ALL WHITE all the time.
I've tried to download firmware - the last I tried was called AirPortFW4.0.9.img - but when I try to run it by clicking it I get the error "The destination folder "AirPort whatever firmware whatever" is on a locked volume.
My computer is a 2,0 HGz MacBook Pro, and int the AirPort Admin Utility the Base Station is said to be V4.0 dev with IP 192.42.249.13 - so it seems to be hard-resat all right...
Please folks...help me out!

I've also encountered the same problem with an older dual ethernet airport.
I first started having problems with the original one about 8 months ago, and after spending a ridiculous three hours on the phone with AppleCare they sent me out a refurbished replacement. That one worked fine for about 5 months, but then started dropping the signal again, before becoming "unfindable". I went through the same processes, (soft reset, then hard reset etc.) which sometimes solved the problem. I eventually I took it to an Apple Store and of course, it worked fine once I got there. Strange thing is, I took it home and it continued working without incident...for a month. When it happened again, I decided to forgo all the the diagnostic work and just take it back to the store. Sure enough, it fixed itself again, then broke again a few weeks later (now).
Unfortunately, I just had knee surgery and can't get down there now, (which was getting ridiculous anyway), so I went through everything again for the first time on the MBP. I ended up getting the "An error occurred while updating the configuration" message, and after reading this thread started up the old TiBook. The reconfig worked on there, but it still isn't visible on either computer. In fact, it then becomes inaccesible even through LAN on the TiBook through either the AirPort Admin or the dropdown, though it did appear on the MBP via AirPort Admin. However, it says the software on the airport cannot be uploaded or changed due to out of date software on my computer, and suggests I go to apple.com/support to update my computer's software, which is already current. It does however say that I may be able to change the settings and so forth, which I was able to do. Unfortunately, it still does not show up anywhere else on either computer, no matter how much I tinker with the settings.
Any ideas? I suppose I'll just stick with built-in ethernet till I am mobile again.
MacBook Pro 15 Intel Duo Core 2.16GHz 2GB/100GB Serial ATA drive@7200rpm Mac OS X (10.4.7) '02 Titanium Powerbook G4 1GHz 1GB/60GB/Superdrive (currently awaiting a new hard drive)

RFC_ERROR_SYSTEM_FAILURE error while updating the sick leave in MSS

Hi Guru ,
We are getting RFC_ERROR_SYSTEM_FAILURE error while updating the Sick leave for team member from portal .
Please tell how to resolve this .
Dump part :
Runtime Errors         MESSAGE_TYPE_X
Error analysis
    Short text of error message:
    System error
    Long text of error message:
    Technical information about the message:
    Message class....... "HRTIM00BUFMSG"
    Number.............. 001
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
Information on where terminated
    Termination occurred in the ABAP program "SAPLHRTIM00_TMWBUFFER" - in
     "INITIALIZE".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 55
    of the (Include) program "LHRTIM00_TMWBUFFERCB5".

When an RFC fails from the portal to an SAP Backend, probably ECC 6.0 in your case, there are a few options that I use to troubleshoot:
      1. Ensure that all your jco's are set up ok, passwords, ect. JCOs do not appear to be the problem here
      2. Have an ABAP programmer review where the RFC is failing on the Backend System
      3. Set up an External Breakpoint in the backend RFC. Step to do this:
               a. Get the Backend UserID of a test portal user that is having this issue.
               b. Ensure that test user has "Debug Display" access in the Backend System
               c. Log into the Backend system, go to SE 37 and display your RFC
               d. Go to Utilities --> Settings --> Debugging in the top menu and add the Test User ID to the "Users" field.
               e. Set an external breakpoint any where you want in the RFC.
               f. Run the Leave request as the test user.
               g. a new SAP GUI screen will popup once it hits the breakpoint. The portal browser will stay frozen until you step thru the ABAP program.
Option 3 may sound like alot at first if you never used it, but if you are responsible for troubleshooting portal issues like this one, it is a skill you must have. You can also have an ABAP resource responsible for external debugging when you come accross issues like these. It helps you see exactly what data is being passed in from the portal and what is happening to cause the error.
Regards,
Tom

Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site

Have an existing ex2010 sp3 organization.
Could not run ex2013cu1 setup from my newly built 2012 server, getting the error in the subject line. I used the command line to run the AD preparation steps successfully from my 2012 DC/GC, then tried to run setup again from the new 2012 server and
still get the same error. The error itself in the log is pretty useless:
[05/07/2013 01:19:13.0137] [0] **********************************************
[05/07/2013 01:19:13.0137] [0] Starting Microsoft Exchange Server 2013 Cumulative Update 1 Setup
[05/07/2013 01:19:13.0137] [0] **********************************************
[05/07/2013 01:19:13.0152] [0] Local time zone: (UTC-08:00) Pacific Time (US & Canada).
[05/07/2013 01:19:13.0152] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[05/07/2013 01:19:13.0152] [0] Setup version: 15.0.620.29.
[05/07/2013 01:19:13.0152] [0] Logged on user: DOMAIN\ADMINISTRATOR.
[05/07/2013 01:19:13.0168] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[05/07/2013 01:19:13.0168] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[05/07/2013 01:19:13.0215] [0] Command Line Parameter Name='sourcedir', Value='\\h1\f$\junk\installers\server\Exchange\2013cu1'.
[05/07/2013 01:19:13.0215] [0] Command Line Parameter Name='mode', Value='Install'.
[05/07/2013 01:19:13.0215] [0] RuntimeAssembly was started with the following command: '/sourcedir:\\SERVER\f$\junk\installers\server\Exchange\2013cu1 /mode:Install'.
[05/07/2013 01:19:13.0215] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[05/07/2013 01:19:13.0793] [0] Finished loading screen CheckForUpdatesPage.
[05/07/2013 01:19:38.0762] [0] Finished loading screen UpdatesDownloadsPage.
[05/07/2013 01:19:40.0496] [0] Starting file's copying...
[05/07/2013 01:19:40.0496] [0] Setup copy files from '\\SERVER\f$\junk\installers\server\Exchange\2013cu1\Setup\ServerRoles\Common' to 'C:\Windows\Temp\ExchangeSetup'
[05/07/2013 01:19:40.0700] [0] Finished loading screen CopyFilesPage.
[05/07/2013 01:19:40.0840] [0] Disk space required: 1292445007 bytes.
[05/07/2013 01:19:40.0840] [0] Disk space available: 23767240704 bytes.
[05/07/2013 01:19:59.0762] [0] File's copying finished.
[05/07/2013 01:19:59.0965] [0] Finished loading screen InitializingSetupPage.
[05/07/2013 01:20:02.0934] [0] Setup is choosing the domain controller to use
[05/07/2013 01:20:09.0325] [0] Setup is choosing a local domain controller...
[05/07/2013 01:20:11.0794] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency.
See the Exchange setup log for more information on this error.
[05/07/2013 01:20:11.0794] [0] [ERROR] Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency.
[05/07/2013 01:20:11.0809] [0] Setup will use the domain controller ''.
[05/07/2013 01:20:11.0809] [0] Setup will use the global catalog ''.
[05/07/2013 01:20:11.0825] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local'.
[05/07/2013 01:20:11.0919] [0] Exchange organization container for the organization is 'CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local'.
[05/07/2013 01:20:11.0966] [0] Setup will search for an Exchange Server object for the local machine with name 'WEX1'.
[05/07/2013 01:20:12.0028] [0] No Exchange Server with identity 'WEX1' was found.
[05/07/2013 01:20:12.0044] [0] The following roles have been unpacked:
[05/07/2013 01:20:12.0044] [0] The following datacenter roles are unpacked:
[05/07/2013 01:20:12.0044] [0] The following roles are installed:
[05/07/2013 01:20:12.0059] [0] The local server does not have any Exchange files installed.
[05/07/2013 01:20:12.0075] [0] Server Name=WEX1
[05/07/2013 01:20:12.0137] [0] Setup will use the path '\\SERVER\f$\junk\installers\server\Exchange\2013cu1' for installing Exchange.
[05/07/2013 01:20:12.0137] [0] The installation mode is set to: 'Install'.
[05/07/2013 01:20:27.0591] [0] An Exchange organization with name 'DOMAIN' was found in this forest.
[05/07/2013 01:20:27.0591] [0] Active Directory Initialization status : 'False'.
[05/07/2013 01:20:27.0591] [0] Schema Update Required Status : 'False'.
[05/07/2013 01:20:27.0591] [0] Organization Configuration Update Required Status : 'False'.
[05/07/2013 01:20:27.0591] [0] Domain Configuration Update Required Status : 'False'.
[05/07/2013 01:20:27.0841] [0] Applying default role selection state
[05/07/2013 01:20:27.0872] [0] Setup is determining what organization-level operations to perform.
[05/07/2013 01:20:27.0872] [0] Because the value was specified, setup is setting the argument OrganizationName to the value DOMAIN.
[05/07/2013 01:20:27.0872] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[05/07/2013 01:20:27.0888] [0] InstallModeDataHandler has 0 DataHandlers
[05/07/2013 01:20:27.0888] [0] RootDataHandler has 1 DataHandlers
[05/07/2013 01:20:27.0903] [0] Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency. See
the Exchange setup log for more information on this error.
[05/07/2013 01:20:27.0935] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency.
See the Exchange setup log for more information on this error.
[05/07/2013 01:21:04.0154] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[05/07/2013 01:21:04.0154] [0] End of Setup
[05/07/2013 01:21:04.0154] [0] **********************************************

Hi,
The cause is clearly described in the log:
[05/07/2013 01:20:11.0794] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency.
See the Exchange setup log for more information on this error.
[05/07/2013 01:20:11.0794] [0] [ERROR] Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency.
I'd suggest you check NIC settings and AD configuration.
Hope it is helpful.
Fiona Liao
TechNet Community Support

"Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master. Run se

Team,
I am trying to Install Exchange on my Lab, getting below error
message.
The Schema Role is installed on Root Domain and trying to install
exchange on Child domain.
1 Root Domain - 1 Child domain. both are located on single site.
“Setup encountered a problem while validating
the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master. Run setup with the /prepareAD parameter and wait for
replication to complete.”
Followed below articles:
http://support.risualblogs.com/blog/2012/02/21/exchange-2010-sp2-upgrade-issue-exchange-organization-level-objects-have-not-been-created-and-setup-cannot-create-them-because-the-local-computer-is-not-in-the-same-domain-and-site-as-the-sche/
http://www.petenetlive.com/KB/Article/0000793.htm
transferred the schema roles to different server on root domain, still no luck.
can someone please help me.
regards
Srinivasa k
Srinivasa K

Hi Srinivasa,
I guess, you didn't completed the initial setup schemaprep and adprep before starting the installation. You can do it as follows:
1. Open command Prompt as administrator and browse to the root of installation cd and run Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
After finishing this,
2. Setup.exe /PrepareAD /OrganizationName:"<organization name>" /IAcceptExchangeServerLicenseTerms
3. To prepare all domains within the forest run Setup.exe /PrepareAllDomains /IAcceptExchangeServerLicenseTerms. If you want to prepare a specific domain run Setup.exe /PrepareDomain:<FQDN of the domain you want to prepare> /IAcceptExchangeServerLicenseTerms
4. Once you complete all of the 3 steps, install the pre-requisities for Exchange 2013
5. Finally, run the setup program
Hope this will help you
Regards from Visit ExchangeOnline |
Visit WindowsAdmin

ITunes freezes on backing up iPad while updating the software to ios 8.

iTunes freezes on backing up iPad while updating the software to ios 8. Please help asap

Hi tac.sharma,
Welcome to the Apple Support Communities!
I know circumstances that keep you from updating your iPad can be frustrating. In this situation I would make sure your iPad is backed up to the iCloud, just to make sure your information is safe. After you have that backup, I would suggest following the steps in the attached article to help you through this update process with iTunes.
If you can't update or restore your iPhone, iPad, or iPod touch - Apple Support
Best regards,
Joe

My Apple TV froze up while updating the software. What should I do?

My Apple TV froze up while updating the software. What should I do?

You can't do much else besides pull the plug. If it causes further problems you should be able to restore as below:
Get yourself a micro USB cable (sold separately), you can restore your Apple TV from iTunes:
Remove ALL cables from Apple TV. (if you don't you will not see Apple TV in the iTunes Source list)
Connect the micro USB cable to the Apple TV and to your computer.
Reconnect the power cable (only for Apple TV 3)
Open iTunes.
Select your Apple TV in the Devices list, and then click Restore.
On the other hand you may be able to simply start the update again. If however the update continues to fail, you should try the restore routine above.

Problem while updating the Support Package 17 on my SAP WAS SP9

Similar Messages

Maybe you are looking for