CDDL step executet with error

And error message is "no data found". How to find out where is the error?

If this is related to your question in the other thread, then you would need to get a trace of the session executing commitDDL. The trace can be used to determine what is causing the no data found error.
Regards,
Ben

Similar Messages

[USF-XSim-62] 'elaborate' step failed with error(s) at vivado 2015.2 Behavioural Simulation

[USF-XSim-62] 'elaborate' step failed with error(s). Please check the Tcl console output or 'C:/xx/axi_pci/axi_pci.sim/sim_1/synth/func/elaborate.log' file for more information.

As stated above, please provide more information if you need any inputs from our end. As it is Vivado Simulator, you can also refer to the Messages tab and see what is the error. Most of the time if elaboration fails then it is possible that some modules were missing or the component/entity binding has failed or the compilation order is not proper. You can also refer to the compile.log to see if there are any warnings. All the logs can be found in the sim_1/behav folder.

SIL_STANDARDCOSTGENERAL step failed with error

Hi ,
I am working on BI Apps 7.9.5.2 which used ODI 10.1.3.5 on windows
I am running an execution plan which uses "SIL_STANDARDCOSTGENERAL" scenerio.
It failed with error message::
com.sunopsis.tools.core.exception.SnpsSimpleMessageException: Error during task interpretation
Task:61
java.lang.Exception: BeanShell script error: Sourced file: inline evaluation of: ``out.print("BeanShell script error: Sourced file: inline evaluation of: `` String . . . '' Token Parsing Error: Lexical error at line 2, column 5. Encountered: "\\" (92), after : "": <at unknown location>
BSF info: Fix default effective from dates at line: 0 column: columnNo
 at com.sunopsis.dwg.codeinterpretor.a.a(a.java)
 at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
 at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
 at com.sunopsis.dwg.cmd.DwgCommandScenario.treatCommand(DwgCommandScenario.java)
 at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
 at com.sunopsis.dwg.cmd.e.i(e.java)
 at com.sunopsis.dwg.cmd.h.y(h.java)
 at com.sunopsis.dwg.cmd.e.run(e.java)
 at java.lang.Thread.run(Unknown Source)
Text:BeanShell script error: Sourced file: inline evaluation of: `` String sysColumn=odiRef.getColList("","<?if (\\u0022[OLTP_SRC_EFF_FROM_DT]\\u00 . . . '' : reflection error: bsh.ReflectError: Method contains( java.lang.String ) not found in class'java.lang.String' : at Line: 2 : in file: inline evaluation of: `` String sysColumn=odiRef.getColList("","<?if (\\u0022[OLTP_SRC_EFF_FROM_DT]\\u00 . . . '' : .contains ( "YES" )
BSF info: Fix default effective from dates at line: 0 column: columnNo
String sysColumn=odiRef.getColList("","<?if (\\u0022[OLTP_SRC_EFF_FROM_DT]\\u0022.equals(\\u0022YES\\u0022)){?>F.[COL_NAME]<?}?>","","","");
if (!odiRef.getColList("","[OLTP_SRC_EFF_FROM_DT]","","","").contains("YES")){
 sysColumn="%NOW%";
out.print("/* Find cases in the I$ table where the dimension already exists on the target and the effective from and to dates are the default values. For the records found, set the effective from date to LEAST(<system columns where null is replaced by source effective date>)*/\nupdate\t") ;
out.print(snpRef.getTable("L","INT_NAME","A")) ;
out.print(" F\nset\t") ;
out.print(snpRef.getColList("", "F.[COL_NAME]", "", "", "SCD_START")) ;
out.print("=LEAST(\n\t\t") ;
out.print(snpRef.getColList("", "<?if(\\u0022[DEST_DT]\\u0022.equals(\\u0022DATE\\u0022)){?>COALESCE(F.[COL_NAME],"+sysColumn+")<?} else {?>TO_DATE('"+odiRef.getOption("END_DATE")+"', 'YYYY-MM-DD')<?}?>", ",\\n\\t\\t", "", "UD1")) ;
out.print("\n)") ;
if (odiRef.getOption("DAY_GAP").equals("1")){out.print("-1") ;
}out.print("\nwhere\texists\t( /* Look to target to see if dimension exists */\n\tselect\t'X'\n\tfrom\t") ;
out.print(snpRef.getTable("L", "TARG_NAME", "A")) ;
out.print(" T\n\twhere\t") ;
out.print(snpRef.getColList("", "F.[COL_NAME]=T.[COL_NAME]", "\\n\\tand\\t ", "", "SCD_NK")) ;
out.print(")\n") ;
out.print(snpRef.getColList("and\\t", "COALESCE(F.[COL_NAME],TO_DATE('"+odiRef.getOption("START_DATE")+"', 'YYYY-MM-DD'))=TO_DATE('"+odiRef.getOption("START_DATE")+"', 'YYYY-MM-DD')","\\nand\\t","","SCD_START")) ;
out.print("\n") ;
out.print(snpRef.getColList("and\\t", "COALESCE(F.[COL_NAME],TO_DATE('"+odiRef.getOption("END_DATE")+"', 'YYYY-MM-DD'))=TO_DATE('"+odiRef.getOption("END_DATE")+"', 'YYYY-MM-DD')","\\nand\\t","","SCD_END")) ;
****** ORIGINAL TEXT ******
<% String sysColumn=odiRef.getColList("","<?if (\u0022[OLTP_SRC_EFF_FROM_DT]\u0022.equals(\u0022YES\u0022)){?>F.[COL_NAME]<?}?>","","","");
if (!odiRef.getColList("","[OLTP_SRC_EFF_FROM_DT]","","","").contains("YES")){
 sysColumn="%NOW%";
%>/* Find cases in the I$ table where the dimension already exists on the target and the effective from and to dates are the default values. For the records found, set the effective from date to LEAST(<system columns where null is replaced by source effective date>)*/
update <%=snpRef.getTable("L","INT_NAME","A")%> F
set <%=snpRef.getColList("", "F.[COL_NAME]", "", "", "SCD_START")%>=LEAST(
 <%=snpRef.getColList("", "<?if(\u0022[DEST_DT]\u0022.equals(\u0022DATE\u0022)){?>COALESCE(F.[COL_NAME],"+sysColumn+")<?} else {?>TO_DATE('"+odiRef.getOption("END_DATE")+"', 'YYYY-MM-DD')<?}?>", ",\n\t\t", "", "UD1")%>
)<% if (odiRef.getOption("DAY_GAP").equals("1")){%>-1<%}%>
where exists ( /* Look to target to see if dimension exists */
 select 'X'
 from <%=snpRef.getTable("L", "TARG_NAME", "A")%> T
 where <%=snpRef.getColList("", "F.[COL_NAME]=T.[COL_NAME]", "\n\tand\t ", "", "SCD_NK")%>)
<%=snpRef.getColList("and\t", "COALESCE(F.[COL_NAME],TO_DATE('"+odiRef.getOption("START_DATE")+"', 'YYYY-MM-DD'))=TO_DATE('"+odiRef.getOption("START_DATE")+"', 'YYYY-MM-DD')","\nand\t","","SCD_START")%>
<%=snpRef.getColList("and\t", "COALESCE(F.[COL_NAME],TO_DATE('"+odiRef.getOption("END_DATE")+"', 'YYYY-MM-DD'))=TO_DATE('"+odiRef.getOption("END_DATE")+"', 'YYYY-MM-DD')","\nand\t","","SCD_END")%>
 at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
 at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
 at com.sunopsis.dwg.cmd.DwgCommandScenario.treatCommand(DwgCommandScenario.java)
 at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
 at com.sunopsis.dwg.cmd.e.i(e.java)
 at com.sunopsis.dwg.cmd.h.y(h.java)
 at com.sunopsis.dwg.cmd.e.run(e.java)
 at java.lang.Thread.run(Unknown Source)
Pls help on this issue

Hi This error is due to JDK/JRE version you are using which is below 1.5
Please use any version 1.5 and above because 'Reflection' framework is not there in jdk below 1.5
the key error point is '' : reflection error: bsh.ReflectError: Method contains( java.lang.String )
which is because of missing reflection api in ur jdk
regs

Creating Job with CmdExe Step failed with error Reason : 5

Hi, I setup a job with Type = Operating System (CmdExec) and Run as 'SQL Server Agent Service Account' , it failed to run with Message below :
Message
Executed as user: PROD\sqlserveragent. The process could not be created for step 4 of job 0x5A83AE4A12AEF649888E85F4072604F6 (reason: 5). The step failed.
1. I couldn't find what is meaning of Reason 5 here.
2. This step used to work previously and it 'not working' suddenly these few days. I wondering anyone make the changes but I am not able to trace it. Any guide to troubleshoot would be helpful.
Thanks .

Operating System ... (reason: 5). The step failed.
Operating System Error code 5 = Access denied, seems to be a permission issue.
Olaf Helper
[ Blog] [ Xing] [ MVP]

VSB1N--Deleting items which are in status 'Processed with errors.'

Hi Friends,
There is one issue which needs your guidance,
In SAP there is an transaction called VSB1N where all our incoming SBI invoices gets received. When an SBI is received it can end up in either 1."Processed without errors" or 2. "Processed with errors". If the SBI ends up in the second state it requires a manual correction and then it can be processed again so it ends up in state one.
The issue here is with number 2 mentioned above, i.e. "Processed with errors". Some of the items do not belong to this list & will not be corrected. So what client want is to delete them and here is where the problem gets in, they cannot be deleted.
Is there any way to have these items deleted?
Many Thanks!
Sadanand.

Check the following notes:-
a) Note 371489 - SBWAP: Posting step terminates
b) Note 557344 - Processing step ends with errors
c) Note 1605859 - FAQ: Processing step in SD self-billing procedure
G. Lakshmipathi

Error in NetWeaver CE 7.1 Installation: Step importJavaDump with MSS 2005

After a dozen unsuccessful tries to install SAP NetWeaver CE 7.1 onto a Windows platform using the Microsoft SQL Server as the backed I could use help regarding this particular error.
I receive the following error when I try to install the software with MSS as the backend:
ERROR 2008-09-29 10:40:02.319 [sixxcstepexecute.cpp:944]
FCO-00011 The step importJavaDump with step key |CE_DevSystem_App|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Jload|ind|ind|ind|ind|11|0|importJavaDump was executed with status ERROR .
The error occurs only with MSS. I have both my Windows and MSS updates up to date. When I use MaxDB as the backend everything goes nice and smooth (even the java info dump, or whatever that command does). When I use Microsoft SQL Server as the backend this error is printed. I have tried with Microsoft SQL Server 2005 Developer Edition on both Windows 2003 Server and Windows XP Professional SP3.
The following gets printed to jload.log:
29.09.08 10:39:49 com.sap.inst.jload.Jload main
INFO: Jload R 7.10 V 0 A 0
29.09.08 10:39:49 com.sap.inst.jload.Jload main
INFO: Jload -sec CE2,jdbc/pool/CE2,C:/usr/sap/CE2/SYS/global/security/data/SecStore.properties,C:/usr/sap/CE2/SYS/global/security/data/SecStore.key -dataDir C:/Work/Temp/51033845_NW_CE_7.1_Workplace_32-bit\DATA_UNITS\CE71_05_JAVA_JDMP -job C:\Program Files\sapinst_instdir\CE71_DEV_MSS\INSTALL\IMPORT.XML -log jload.log
29.09.08 10:40:02 com.sap.inst.jload.Jload main
SEVERE: couldn't connect to DB
29.09.08 10:40:02 com.sap.inst.jload.Jload logStackTrace
SEVERE: com.microsoft.sqlserver.jdbc.SQLServerException: The connection to the named instance has failed. Error: java.net.SocketTimeoutException: Receive timed out.
 at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown Source)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.getInstancePort(Unknown Source)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source)
 at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
 at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendorConnection(DriverPooledConnectionFactory.java:50)
 at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledConnection(DriverPooledConnectionFactory.java:37)
 at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnection(DBDataSourceImpl.java:677)
 at com.sap.sql.connect.datasource.DBDataSourceImpl.newPooledConnection(DBDataSourceImpl.java:626)
 at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataSourceImpl.java:105)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:202)
 at com.sap.inst.jload.db.DBConnection.connectViaSecureStore(DBConnection.java:109)
 at com.sap.inst.jload.db.DBConnection.connect(DBConnection.java:153)
 at com.sap.inst.jload.Jload.main(Jload.java:702)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:161)
29.09.08 10:40:02 com.sap.inst.jload.Jload printErrorInformation
SEVERE: An error occured during execution. Please consult SAP note 942766 for first steps on troubleshooting the problem.
For one thing, there is no SAP note 942766 when you search for one at SAP Notes. Another thing that is particularly interesting is that the SQL JDBC driver does not get the SQL instance name, or at least does not print that to the exception message but instead leaves there two whitespaces (The connection to the named instance >>Instance name should be here<< has failed).
Any suggestions on how to get pass this error? All help would be appreciated!
Best regards,
Sven

hello,
please check and ensure that:
- your database server is started.
- your database instance is running and you can connect to it through the network interface
- the entries in secure store contain the correct options for
connecting to the database. (These can be checked via configtool and this only applies to the case when JLoad is run using secure store parameters)
hope this helps
kr,
andreas

Lightroom has crashed with error message 'error reading from its preview cache' - this happens every time i try a launch it. I have looked a forum to repair the fault. there are different recommedations.can you tell me step by step how to recify this pro

lightroom has crashed with error message 'error reading from its preview cache' - this happens every time i try a launch it. I have looked a forum to repair the fault. there are different recommedations.can you tell me step by step how to recify this problem. i can not find ircat ir data etc in the programme files. Thanks

robmac76 wrote:
can you tell me step by step how to recify this problem.
Yes:
Step 1: Delete the preview cache.
That's it!
So, the trick is to find the preview cache.
This document gives location:
http://helpx.adobe.com/lightroom/kb/preference-file-locations-lightroom-41.html
To be clear: it's a folder in with your catalog and you want to delete the whole folder but nothing else.
If your catalog file path is "X:\My Catalogs\My Catalog.lrcat", then the preview cache "folder" will be:
X:\My Catalogs\My Catalog Previews.lrdata
So the trick is to find your catalog file, and since Lr won't open your catalog and run, you can't use it to find out.
But you should be able to find it by searching your disks for *.lrcat files - do you know how to do that?
Which OS?
If you know the name of the catalog it will help, but also: it's probably NOT in with your program files.
UPDATE: The above-mentioned document gives default name and location for preview cache, so if you haven't overridden the default, it should be right where that document said it would be - is it? (of course you need to know your user name too, but presumably you do, no?).
R

Error when installing SM7 "The step runMigrationMonitor with step key "

Hi all
Please help for the following error when installing
ERROR 2009-06-13 00:27:13.515
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
Regards
Kevin

Hi Uday
import.monitor.java.log
Loading of 'SASACONT1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 4, failed 0, total 29.
Import Monitor jobs: running 3, waiting 22, completed 4, failed 0, total 29.
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 4, failed 1, total 29.
Loading of 'REPOSRC' import package: ERROR
Import Monitor jobs: running 1, waiting 22, completed 4, failed 2, total 29.
Loading of 'SAPAPPL0' import package: ERROR
Import Monitor jobs: running 0, waiting 22, completed 4, failed 3, total 29.
Import Monitor jobs: running 1, waiting 21, completed 4, failed 3, total 29.
Import Monitor jobs: running 2, waiting 20, completed 4, failed 3, total 29.
Import Monitor jobs: running 3, waiting 19, completed 4, failed 3, total 29.
Loading of 'DOKCLU' import package: ERROR
Import Monitor jobs: running 2, waiting 19, completed 4, failed 4, total 29.
Loading of 'SAPAPPL1' import package: ERROR
Import Monitor jobs: running 1, waiting 19, completed 4, failed 5, total 29.
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 0, waiting 19, completed 4, failed 6, total 29.
Import Monitor jobs: running 1, waiting 18, completed 4, failed 6, total 29.
Import Monitor jobs: running 2, waiting 17, completed 4, failed 6, total 29.
Import Monitor jobs: running 3, waiting 16, completed 4, failed 6, total 29.
Loading of 'DD03L' import package: ERROR
Import Monitor jobs: running 2, waiting 16, completed 4, failed 7, total 29.
Loading of 'SAPSSRC' import package: ERROR
Import Monitor jobs: running 1, waiting 16, completed 4, failed 8, total 29.
Loading of 'STERM_TEXT' import package: ERROR
Import Monitor jobs: running 0, waiting 16, completed 4, failed 9, total 29.
Import Monitor jobs: running 1, waiting 15, completed 4, failed 9, total 29.
Import Monitor jobs: running 2, waiting 14, completed 4, failed 9, total 29.
Import Monitor jobs: running 3, waiting 13, completed 4, failed 9, total 29.
Loading of 'SEOSUBCODF' import package: ERROR
Import Monitor jobs: running 2, waiting 13, completed 4, failed 10, total 29.
Loading of 'E071K' import package: ERROR
Import Monitor jobs: running 1, waiting 13, completed 4, failed 11, total 29.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 0, waiting 13, completed 4, failed 12, total 29.
Import Monitor jobs: running 1, waiting 12, completed 4, failed 12, total 29.
Import Monitor jobs: running 2, waiting 11, completed 4, failed 12, total 29.
Import Monitor jobs: running 3, waiting 10, completed 4, failed 12, total 29.
Loading of 'ATAB' import package: ERROR
Import Monitor jobs: running 2, waiting 10, completed 4, failed 13, total 29.
Loading of 'SAPSPROT' import package: ERROR
Import Monitor jobs: running 1, waiting 10, completed 4, failed 14, total 29.
Loading of 'SAPSDOCU' import package: ERROR
Import Monitor jobs: running 0, waiting 10, completed 4, failed 15, total 29.
Import Monitor jobs: running 1, waiting 9, completed 4, failed 15, total 29.
Import Monitor jobs: running 2, waiting 8, completed 4, failed 15, total 29.
Import Monitor jobs: running 3, waiting 7, completed 4, failed 15, total 29.
Loading of 'SAPPOOL' import package: ERROR
Import Monitor jobs: running 2, waiting 7, completed 4, failed 16, total 29.
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 1, waiting 7, completed 4, failed 17, total 29.
Loading of 'SAPSLEXC' import package: ERROR
Import Monitor jobs: running 0, waiting 7, completed 4, failed 18, total 29.
Import Monitor jobs: running 1, waiting 6, completed 4, failed 18, total 29.
Import Monitor jobs: running 2, waiting 5, completed 4, failed 18, total 29.
Import Monitor jobs: running 3, waiting 4, completed 4, failed 18, total 29.
Loading of 'SAPDDIM' import package: ERROR
Import Monitor jobs: running 2, waiting 4, completed 4, failed 19, total 29.
Loading of 'SAPDFACT' import package: ERROR
Import Monitor jobs: running 1, waiting 4, completed 4, failed 20, total 29.
Loading of 'SAPCLUST' import package: ERROR
Import Monitor jobs: running 0, waiting 4, completed 4, failed 21, total 29.
Import Monitor jobs: running 1, waiting 3, completed 4, failed 21, total 29.
Import Monitor jobs: running 2, waiting 2, completed 4, failed 21, total 29.
Import Monitor jobs: running 3, waiting 1, completed 4, failed 21, total 29.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 4, failed 22, total 29.
Loading of 'SAP0000' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 4, fail
ed 23, total 29.
Loading of 'SAPUSER' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 4, failed 24, total 29.
Edited by: Kevin Wong on Jun 18, 2009 11:23 AM
Edited by: Kevin Wong on Jun 18, 2009 11:24 AM

SCCM 2012 R2 - Migration TS Failed in Release Request Step with Error Code 0x80004005

Hi
I have Upgraded my lab from SCCM 2012 SP1 to SCCM 2012 R2. Now, While I am running TS for Refresh/Replace Migration, its successfully captures all the Data & settings and can also restores all Data & settings, but at release request Step TS got failed.
In SMSTS log file error was "Release Request Failed with error code 0x80004005".
Is there any KB released by Microsoft to fix this issue?? Due to this issue I am unable to run any other TS.

I've seen a few weird scenarios with task sequences after an upgrade from SP1 to R2.
In most cases I've been able to fix these "problems" by simply creating a new task sequence, and copy all the custom steps to the new task sequence.
Also make sure to update boot images, mdt packages, usmt etc. to new versions.
So thats what I'd try first....
Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
@ronnipedersen

Error msg "FCO-00011 The step createJSF with step key " install SM7

Hi all
The following error msg as when I installing SM7
the error show "The step createJSF with step key " <== what meanings?
Regards
Kevin
WARNING[E] 2009-06-10 21:58:40.890
CJS-30197 User SAPJSF already exists
Diagnosis
You have tried to create or change a user that already exists.
Procedure
Edit the existing user or first delete the user and then recreate it.
Alternatively, you can choose another user name, for example, by
appending part of the first name.
[System: PAS(001), Message: 01 224]
. DIAGNOSIS: For more details see output of log file: User SAPJSF already exists
Diagnosis
You have tried to create or change a user that already exists.
Procedure
Edit the existing user or first delete the user and then recreate it.
Alternatively, you can choose another user name, for example, by
appending part of the first name.
[System: PAS(001), Message: 01 224]
*ERROR 2009-06-10 21:58:41.218*
*FCO-00011 The step createJSF with step key |NW_Onehost|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_CI_Instance_Doublestack|ind|ind|ind|ind|3|0|createJSF was executed with status ERROR .*
Edited by: Kevin Wong on Jun 11, 2009 3:47 AM

Hi
anyone can help me or having the same problems?
*ERROR 2009-06-10 21:58:41.218*
*FCO-00011 The step createJSF with step key |NW_Onehost|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_CI_Instance_Doublestack|ind|ind|ind|ind|3|0|createJSF was executed with status ERROR .*
Regard,

HT1386 Pleae help connecting my iPhone4 5.1.1 to my laptop with error 0xE8000012, I tried the the mentioned steps in this regard, but hopless.

Pleae help connecting my iPhone4 5.1.1 to my laptop with error 0xE8000012, I tried the the mentioned steps in this regard, but hopless.

If you have some idea where the problem might be, you can get finer-grained control over what goes into the error log by setting nsslapd-errorlog-level appropriately. For the settings, see http://docs.sun.com/source/816-5608-10/config.htm#140331

Terminating Activity step with error

Hi,
I have an Activity step which task executes a method of a class. This method returns result code (and I do binding to WF) and if it is not 0 I would like to terminate this step (workitem) in error status. How is the best and easiest way to do this?
Thank you in advance,
Anna

Thank you.
But I am not able to set any handling in case of error of this step - if this fails it must be possible to see in worfklow log as error. If I set an exception in method and later not catch it in workfow, would I see it as erroneus?
Anna

SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

SAP ECC error:'Migration Monitor' exits with error code 103.

Hi All,
I am doing SAP ECC installation for windows 32 bit with MAXDB as backend.
I am stuck at the import ABAP.Getting error
ERROR 2008-08-08 16:10:53
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
1) imort_monitor.java.log-->contains
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 0, completed 18, failed 0, total 19.
Loading of 'SAPVIEW' import package: ERROR
Import Monitor jobs: running 0, waiting 0, completed 18, failed 1, total 19.
2)import_monitor.log
ERROR: 2008-08-08 16:10:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPVIEW' import package is interrupted with R3load error.
Process 'D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -nolog -c 0' exited with return code 2.
For mode details see 'SAPVIEW.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
INFO: 2008-08-08 16:10:52
All import packages are processed.
WARNING: 2008-08-08 16:10:52
1 error(s) during processing of packages.
INFO: 2008-08-08 16:10:52
Import Monitor is stopped.
3)SAPVIEW.log
error message returned by DbSl:
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE VIEW "Z_T_CO_BW" ( "KOKRS" , "KOSTL" , "VERSN" , "KSTAR" , "WOG001" , "MEG001" ) AS SELECT T0002."KOKRS", T0002."KOSTL", T0001."VERSN", T0001."KSTAR", T0001."WOG001", T0001."MEG001" FROM "COSS" T0001, "CSKS" T0002 WHERE T0002."MANDT" = T0001."MANDT")
DbSlExecute: rc = 103
(SQL error -942)
error message returned by DbSl:
(DB) INFO: disconnected from DB
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: job finished with 3108 error(s)
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20080808174211
Only SAPDB: SAPSID srvice of SAP DB is only up.
No other services of database are up.And i am not able to up the other services also.
Is it required to up the other services?
If not?
Why this error is occuring?
Any help will be appreciated.
Thanks&Regards
Manisha das

Hello Manisha,
The one of the possible reasons for this is due to lack of H/W.
Increase your RAM size to atleast 2GB and utilise the same while you are installing ECC in database parameters step..
If the issue is with H/W, then this should fix the issue.
Hope it helps,
Regards,
Satish.

SharePoint 2013 site collection 'upgrade completed with errors'

Hi All,
I am in process to upgrade SharePoint 2010 to SharePoint 2013 with all steps as mentioned in TechNet.
I was able to get all the SP2010 UI in SP2013 environment. However, when I navigated to top level site and clicked on “Site
Collection health checks”. In SP2010 environment I never used (as Farm Admin) any Video content type. It belongs
to out-of-the-box "digital asset content types" and cannot be deleted.
Therefore I changed the name of Video to our department name like "Video - Company" and ran the site collection health check again. This time there was no conflict for content types.
After ran the site collection upgrade I got following error.
-------------------------------------------START------------------------------------------
05/05/2014 14:34:28.66 OWSTIMER (0x1474)
0x123C SharePoint Foundation Upgrade
SPFeatureDefinition aj2bj
ERROR Feature upgrade action 'AddContentTypeField' threw an exception upgrading Feature 'CTypes' (Id: 15/'695b6570-a48b-4a8e-8ea5-26ea7fc1d162') in Site 'http://sp13fe01-dev': Field type
Rating is not installed properly. Go to the list settings page to delete this field.
32d48d9c-70d4-f09a-6073-526808f844be
05/05/2014 14:34:53.04 OWSTIMER (0x1474)
0x123C SharePoint Foundation Upgrade
SPSiteWssSequence2 ajy6m
ERROR Feature upgrade incomplete for Feature 'CTypes' (Id: 15/'695b6570-a48b-4a8e-8ea5-26ea7fc1d162') in Site 'http://sp13fe01-dev'. Exception: Field type Rating is not installed properly. Go to the list settings
page to delete this field. 32d48d9c-70d4-f09a-6073-526808f844be
05/05/2014 15:18:43.95 OWSTIMER (0x1474)
0x123C SharePoint Foundation Upgrade
SPManager ajxoe
ERROR RunUpgradeSiteSession [SPSite Url=http://sp13fe01-dev] failed.
32d48d9c-70d4-f09a-6073-526808f844be
05/05/2014 15:18:44.16 OWSTIMER (0x1474)
0x123C SharePoint Foundation Upgrade
SPManager ajxoe
ERROR Exception: Upgrade completed with errors. Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS\SiteUpgrade-20140505-143330-61.log. The
number of errors and warnings is listed at the end of the upgrade log file.
32d48d9c-70d4-f09a-6073-526808f844be
05/05/2014 15:18:44.16 OWSTIMER (0x1474)
0x123C SharePoint Foundation Upgrade
SPManager ajxoe
ERROR at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CheckPoint() at Microsoft.SharePoint.Upgrade.SPUpgradeSession.LogEnd() at Microsoft.SharePoint.Upgrade.SPManager.RunUpgradeSiteSessionCore(Object
lockObject, SPSite site, SPUpgradeOperationFlags upgradeOperationFlags, Boolean checkConcurrentSiteUpgradeSessi
32d48d9c-70d4-f09a-6073-526808f844be
-----------------------------------END-------------------------------------
Feature ID 695b6570-a48b-4a8e-8ea5-26ea7fc1d162 is Standard Content Type Definitions https://social.technet.microsoft.com/wiki/contents/articles/7695.sharepoint-2010-list-of-features-id-displayname-and-scopes.aspx.
Any expert to solve the issue??
Thank you.
regards,
Aroh Shukla

Hi All and Inderjeet,
Thanks for your reply and pointers.
I did follow the steps as mentioned in the links above. I used some third party solutions but not for any Video solution. I was able to successfully migrated the SP2010 (WSS_Content) to SP2013 (WSS_Content) environment a few weeks back with exactly same
third party solutions and no site collection error:
I renamed the default and out-of-the box video site content type as shown:
I ran the "Site Collection Health Check" and did not receive any error as in my second screenshot.
But, after upgrade the Site Collection Upgrade and got the same errors.
I don't know if there is any SharePoint Server 2013 patch gave this error as I keep run the Windows Server 2012 (not running R2) and SharePoint Server 2013 regularly.
Can suggest how to resolve this error?
Many Thanks!!
--Aaroh
Aroh Shukla
The same here. Opening a support ticket with MS.

CDDL step executet with error

Similar Messages

Maybe you are looking for