Nvidia 52.16 with errors

I installed Nvidia's 52.16 twice allready. One just after reformatting my Hard Drive.
My problem is when I'm playing BF the screen starts to get crazy.I can only see colors on the screen lol. With the older version of Nvidia I didn't have any problems.NIVIDIA BUG?? I'm using the older version and i'm happy. Just wanted to let the readers know about this problem and to see if more people are experiencing the same thing
Thanks,

By BF, I assume you mean BattleField 1942? If so, see nVidia's release notes for the 52.16 drivers - under 'open issues' you'll find the following:
"GeForce FX5950 Ultra and GeForce4 Ti4400, Windows XP: Rendering corruption in Battlefield 1942 Desert Combat. A fix for this issue will be included in the next driver release."
Also a mention of Blue-screen crash for BF with GeForce 4MX 440, and Ti4400 under WinXP.
(no mention of the 5900 specifically, but it may affect it as well)
Everyone should check the driver release notes as it may explain problems/symptoms experienced.
nVidia Forceware 52.16 Release Notes (PDF)

Similar Messages

I can register an OCX file in Windows 7 x64 without incident but with Windows 7 x32 I get a p-up that says "DllRegisterServer failed with error code: 0x80004005. What gives???

Hey yeah. not much else to say. The title says it all.
I'm trying to register an OCX file that my video editing application requires to work properly.
I'm using a Registry (Regsvr32 and Regsvr64) tool to Register DLL/OCX files. Both bit Registry tools work fine. I can Register any DLL or OCX file with Windows 7 x64 and everything goes smoothly.
But, when in Windows 7 x32, again, no problem with merging the Regsvr32 tool, but when I go to register the OCX file message says it was loaded but the DllRegisterServer failed with error: 0x80004005.
Why does everything work in Windows 7 RC 7100 x64 but not in Windows 7 RC 7100 x32???GA P35 DQ6 Mb, Intel Wolfdale 8600 3.33Ghz C2D CPU., 4x2Gb Mushkin DDR2 1066 PC2 8500 Ascents Memory Mods., PNY-nVidia GE Force 8800 GTS (640MB), 4-Western Digital Caviar SATA(2) HDD's (internal), 1 EIDE-USB External; Hauppauge PVR 1600 TV tuner, Dual Monitor: (1) Standard up top, (1) WideScreen below; Altec Lansing Speakers. Here Kitty, Kitty...that's my Kitty Kat, he's a Kat, because he is kat...kat.

I don't know what happened.
My Video Editing software was working fine a few days ago in Windows 7 x64. Tried using it this morning....couldn't load the .mpg video clip. Just stood there looking stupid like it does in the 32-bit version of Windows 7.
I was hoping the x64 version of Windows 7 RC 7100 was going to make a decent run against my XP Pro SP3 setup. When I was able to register the required .ocx file for the video editing application, I thought "cool". I made a TV recording then used the Video Editor to edit it and it worked fine. Earlier this morinng I made another TV recording, went to go edit it and the video editing application couldn't load the .mpg file at all. This problem just annihilated any chance of me ever purchasing Windows 7, 32 or 64-bit.GA P35 DQ6 Mb, Intel Wolfdale 8600 3.33Ghz C2D CPU., 4x2Gb Mushkin DDR2 1066 PC2 8500 Ascents Memory Mods., PNY-nVidia GE Force 8800 GTS (640MB), 4-Western Digital Caviar SATA(2) HDD's (internal), 1 EIDE-USB External; Hauppauge PVR 1600 TV tuner, Dual Monitor: (1) Standard up top, (1) WideScreen below; Altec Lansing Speakers. Here Kitty, Kitty...that's my Kitty Kat, he's a Kat, because he is kat...kat.

Encoding failed with "Error Compiling Movie, Unknown Error"

Hi,
I have come across this error while encoding an NTSC STD sequence to H.264 format, NTSC STD preset. The sequence has few simple effects and titles and its lenght is approx 2min. When same sequence is encoded to FLV, the encode passes. Also, when i encode using inline AME through Export Now, the encode passes. The failure is seen when i encode this sequence using Dynamic Link.
System Configuration :
4 GB RAM, Intel I 3 processor, 64bit Win 7, nVidia CUDA card with 512 MB memory.
If any other information is required, please let me know.
Thanks,
Prateek

I forgot to mention in my original post I was able to export a microsoft avi file of the movie before I added the after effects sequences it appears the AE portions are causing the encoding errors.
Eric

Anyone familiar with error 4000 while attempting to burn playlist to a cd?

I would like to burn a playlist to a cd, but the process is interrupted everytime with error 4000. I wish I knew what that meant!
I've read other similiar cd burning posts and have read about the filmware possibly needing updating, but I do not understand how to check that. My computer was built by a local company and there would not be updates online.
Here are my cd diagnostics:
Microsoft Windows XP Professional Service Pack 2 (Build 2600)
ASUSTeK Computer INC. A7N8X-X
iTunes 6.0.4.2
CD Driver 2.0.4.3
CD Driver DLL 2.0.3.2
LowerFilters: PxHelp20 (2.0.0.0), drvmcdb (1.0.0.1), Cdr4_xp (5.3.4.21),
UpperFilters: Cdralw2k (5.3.4.21), GEARAspiWDM (2.0.4.3),
Video Driver: NVIDIA GeForce2 MX/MX 400 (Microsoft Corporation)\GeForce2 MX/MX 400
Found aspi32 running.
DOT4\Vid03f0&Pid_3e02&DOT4&STOREHPHI11, Bus Type USB
SCSI\DiskST380011A_____________3.06, Bus Type SCSI, Bus Address [0,0]
USBSTOR\DiskApple__iPod___________1.62, Bus Type USB
SCSI\CdRomTEAC___CD-W552E_______1.09, Bus Type SCSI, Bus Address [0,0]
SCSI\CdRomTOSHIBADVD-ROMSD-M17121004, Bus Type SCSI, Bus Address [1,0]
Current user is administrator.
D: TEAC CD-W552E, Rev 1.09
Audio CD in drive.
Found 19 songs on CD, playing time 66:59 on Audio CD.
Track 1, start time 00:02:00
Track 2, start time 03:57:36
Track 3, start time 07:26:39
Track 4, start time 11:25:12
Track 5, start time 15:03:05
Track 6, start time 18:46:08
Track 7, start time 21:45:19
Track 8, start time 25:43:29
Track 9, start time 30:09:63
Track 10, start time 33:26:62
Track 11, start time 37:08:07
Track 12, start time 40:41:53
Track 13, start time 43:34:34
Track 14, start time 46:43:55
Track 15, start time 49:54:54
Track 16, start time 53:10:37
Track 17, start time 56:37:00
Track 18, start time 60:52:42
Track 19, start time 63:52:11
Audio CD reading succeeded.
Get drive speed succeeded.
The drive CDR speeds are: 4 8 12 16 24 32 40 48.
The drive CDRW speeds are: 4 8 12.
E: TOSHIBA DVD-ROM SD-M1712, Rev 1004
Drive is empty.
The last failed audio CD burn had error code 4000(0x00000fa0). It happened on drive D: TEAC CD-W552E on CDR media at speed 16X.
The tracks that you see listed in the diagnostics do no play. I only hear a screeching sound.
I would appreciate any help!!!
Thank you!
Windows XP

Unfortunately, that link did not help me. It says that that firmware is not for my version. Here are the results of my diagnostic run from iTunes:
FairPlay 1.10.14
Apple Application Support 1.4.1
iPod Updater Library 10.0d2
CD Driver 2.2.0.1
CD Driver DLL 2.1.1.1
Apple Mobile Device 3.3.0.69
Apple Mobile Device Driver 1.49.0.0
Bonjour 2.0.4.0 (214.3)
Gracenote SDK 1.8.2.457
Gracenote MusicID 1.8.2.89
Gracenote Submit 1.8.2.123
Gracenote DSP 1.8.2.34
iTunes Serial Number 919FC76619A7D699
Current user is not an administrator.
The current local date and time is 2010-12-21 21:07:46.
iTunes is not running in safe mode.
WebKit accelerated compositing is enabled.
HDCP is not supported.
Core Media is supported.
Video Display Information
Intel Corporation, Mobile Intel(R) 965 Express Chipset Family
Intel Corporation, Mobile Intel(R) 965 Express Chipset Family
** External Plug-ins Information **
No external plug-ins installed.
iPodService 10.1.1.4 is currently running.
iTunesHelper 10.1.1.4 is currently running.
Apple Mobile Device service 3.3.0.0 is currently running.
** CD/DVD Drive Tests **
LowerFilters: PxHelp20 (2.0.0.0),
UpperFilters: GEARAspiWDM (2.2.0.1),
D: TSSTcorp CDDVDW TS-L632H, Rev TO01
Audio CD in drive.
Found 11 songs on CD, playing time 34:14 on Audio CD.
Track 1, start time 00:02:00
Track 2, start time 02:19:42
Track 3, start time 04:44:05
Track 4, start time 07:38:58
Track 5, start time 11:24:74
Track 6, start time 14:39:35
Track 7, start time 19:47:45
Track 8, start time 22:48:31
Track 9, start time 24:44:14
Track 10, start time 26:51:59
Track 11, start time 31:22:66
Audio CD reading succeeded.
Get drive speed succeeded.
The drive CDR speeds are: 10 16 20 24.
The drive CDRW speeds are: 10.
The drive DVDR speeds are: 10.
The drive DVDRW speeds are: 10.
The last failed audio CD burn had error code 2131(0x00000853). It happened on drive D: TSSTcorp CDDVDW TS-L632H on CDR media at speed 0X.
Any idea where I should go from here???

Transport control program tp ended with error code 0212

Hi all,
I have created a two system landscape of development & production server. But while I am releasing any request from develpoment server a error is showing: " Transport control program tp ended with error code 0212 Errors: could not access file as supposed (see dev_tp or S".I have chosen development server as domain controller. TMS alert viewer error message also contains the following information------>command: TMS_MGR_READ_TRANSPORT_QUEUE
 service: transport service
 start : online
 Function: TMS_TP_SHOW_BUFFER
 message: TP_REPORTED_ERROR
In import monitor it's showing : "tp finished: could not access file as supposed (see dev_tp or SLOG1113.K"
Can you tell me how to resolve this issue?

dev_tp contains:
This is R3trans.exe version 6.14 (release 700 - 09.04.10 - 11:26:00).
unicode enabled version
usage: R3trans.exe [<options>] <control_file>
The control_file describes what R3trans has to do.
The following options are possible:
-c f1 f2 : Copy file f1 to f2 with character set conversion.
-d : DB connect. Test if SAP database is available.
-i file : Import from file without using a control file.
-l file : List the contents of file to the log file.
-m file : List the contents of file to allow tp to create a cofile.
-t : Test. All database changes are rolled back.
-t4 : Trace level 4. Switch on developer trace.
-u <int> : Unconditional modes. See below.
-v : Verbose. Write more details to the log file.
-w file : Log file. The default log file is 'trans.log'.
-x : DB connect without access on any SAP table.
R3trans.exe finished (0012).
& the slog file is not there in the trans/log directory

Archive file with errors in sender file adapter not working! please help!

Hi Experts,
I have a file to RFC scenario. the input is a XML file. I have setup the flag in sender file adapter channel for archiving the input files with errors. But it is not working.
For testing I have used an invalid xML file for example without the main XML tag. I have also tested with a MSWORD file saved with.xml extension. But in both the cases the files are not getting archived.
My archive location permissions are fine and in fact normal archive operation is happening. That is, if I select the processing mode as "Archive" and gave the Archive directory then files are getting archived. The problem is only with the "Archive faulty source files" option.
What am I missing? DO I need to do some more configurations?
What are the prerequisites if any for this option?
How to test this?
Please help me! I will be greatfull to you all!
Thanks & Regards
Gopal

and go thru this links
Creating a Single Archive of the Version Files
http://help.sap.com/saphelp_nw04/helpdata/en/79/1e7aecc315004fb4966d1548447675/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/31/8aed3ea86d3d67e10000000a114084/frameset.htm
Note: reward points if solution found helpfull
Regards
Chandrakanth.k

Issues in IDoc Sender Scenario:IDoc with errors added

Hi all
Am working on an IDoc to JDBC scenario. In R/3 system, I have created distribution model, partner profile, RFC destination and port.The IDoc is generated and is sent to XI successfully. But in XI , there is no entry in SXI_MONITOR for this (unfortunately IDX5 is not available in the XI server! ;as of now). Instead an entry is made in WE05 and WE02 with stautus 56(IDoc with errors added). In the status record:
status 56 : External segment name E2KOMG003 cannot be interpreted
status 60 : Basic IDoc type COND_A03 could not be found.
And the segments displayed in data record are different from the segments in the data record of the IDoc generated at R/3. (say for E1KOMG at R/3, E2KOMG003 in XI).Earlier the flow was working fine and the DB table was updated successfully. And the entire stuff is believed to be 'unmodified' .
Would any one help in resolving the issue.
Thanks,
Chilanka

Hi,
>>>>I have created partenr profile in R/3.Need I create a partner profile in XI for R/3 system?
no you cannot create any partner profiles in XI
for more about IDOC configuration in XI check :
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

HT1212 I am unable to get our of a continuous cycle when trying to update or restore my iPad 2. Plug in to iTunes 12.0.1 (latest version). Click update, told can't update, have to restore. Restore fails with error 9. Any help appreciated.

When I tried to update my iPad I got an error 9. Now, I am unable to access my iPad. It is in a continuous cycle when I try to update or restore the iPad 2. Plug in to iTunes 12.0.1 (latest version). Click update, told can't update, have to restore. Restore fails with error 9. Any help appreciated.
Here's the cycle:
I plug in my iPad when “cable to iTunes shows on iPad screen. It says "Your iPad can't be updated, you must restore it to factory settings." That bad enough news, but it gets worse.
Click Restore
Extracting software…
Preparing iPad for restore
Waiting for iPad…
Verifying iPad restore with Apple…
(empty bar under the Apple logo…does not show any activity)
“The iPad “iPad” could not be restored. An unknown error occurred (9).”
Notes: I just upgraded to OS X Yosemite 10.10.1 on my iMac (27-inch, Mid 2011) in the last week. It’s the first time I’m tried to backup/update my iPad since the iMac update.
I swapped out the USB cable to a new cable and get the same results.
I also unplugged all other USB devices from the iMac and security on my iPad and still get the same results.
I find it strange that it shows no Serial number for my my iPad 2 when plugged in. It shows “Serial Number: n/a on the screen when it displays: “iPad Recovery Mode To update your iPad without erasing its contents, click Update. To restore your iPad to its factory settings, click Restore iPad.
I prefer to update my iPad, but it displays “Your iPad can’t be updated, you must restore it to factory settings. If you previously backed up the iPad, click Restore Backup after the restore process completes.”
It’s a continuous loop. I get the display on my iPad to plug in the iPad to iTunes, plug it in which ends after going through the above procedure saying an error occurred (9).
So now I cannot use my iPad. When I turn it on I get the display showing me to plug it into iTunes with the cable. Since this is the only option I have I plug it in and the loop begins.
Any advice would be appreciated.
Thanks!

Hello jaybearden,
Thanks for the question. After reviewing your post, it sounds like you are not able to restore the iOS device since you get an error 9. I would recommend that you read this article, it may be able to help the issue.
Resolve iOS update and restore errors - Apple Support
Check your security software
Related errors: 2, 4, 6, 9, 1000, 1611, 9006. Sometimes security software can prevent your device from communicating with either the Apple update server or with your device.
Check your security software and settings to make sure that they aren't preventing a connection to the Apple servers.
Thanks for using Apple Support Communities.
Have a nice day,
Mario

Can't update, get "Photoshop 13.1.2 for Creative Cloud Done with Errors. Error Code: U44M1P6" Help!

Have tried several times to Update Photoshop Mac CS6, always get "
Photoshop 13.1.2 for Creative Cloud
Done with Errors. Error Code: U44M1P6"
What gives and how can I fix?

In this case since it is a feature bearing update for Creative Cloud Bpolatty will need to download the update through the Adobe Application Manager/
Bpolatty I would recommend reviewing the installation log file for the Photoshop 13.1.2 update. You can find details on how to locate and interpret the log file at Troubleshoot with install logs | CS5, CS5.5, CS6 - http://helpx.adobe.com/creative-suite/kb/troubleshoot-install-logs-cs5-cs5.html.

Installation of Photoshop update 13.1.2 for creative cloud fails with error code U44M1P7 I need help

I need help installing update 13.1.2 for Photoshop creative cloud, installation fails with error code: U44M1P7. Could someone please help?

Sorry to bother you.
I could find the answer after searching previous posts about this language problem.
Had to change my language in AAM profile and then download PS CS6 again ( english version ).
Then open the actual Photoshop and in preferences > interface you can besides the Dutch also option for English.
restart application and Voila.
Greetz, Jeroen

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.

DAG - Backup failing on 1 DB only with error - The Microsoft Exchange Replication service VSS Writer instance ID failed with error code 80070020 when preparing for a backup of database 'DB012'

Hi Board,
i´ve search across the board, technet and symantec sites but did not found a hint about my problem.
we drive a 2 node DAG (Location1-Ex1-mb1
Location2-exc1-mb1), on SP2 RU4 patchlevel with 40 Databases.
Since some time the backup of one - and only one DB - is failing with these events, logged on the Mailboxserver on which the passive DB is hosted.
Log Name:      Application
Source:        MSExchangeRepl
Date:          28.09.2012 00:37:17
Event ID:      2112
Task Category: Exchange VSS Writer
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Location1-Exc1-MB1
Description: The Microsoft Exchange Replication service VSS Writer instance 1ab7d204-609a-4aea-b0a7-70afb0db38de failed with error code 80070020 when preparing for a backup of database 'DB012'.
Followed by
Log Name:      Application
Source:        MSExchangeRepl
Date:
01.10.2012 03:33:06
Event ID:      2024
Task Category: Exchange VSS Writer
Level:         Error
Keywords:      Classic
User:
N/A
Computer:      Location1-Exc1-MB1
Description:
The Microsoft Exchange Replication service VSS Writer (Instance 42916d80-36c1-4f73-86d0-596d30226349) failed with error 80070020 when preparing for a backup.
The backup Application - Symantec Backup Exec 2010 R3 – states, this error
Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
Check the Windows Event Viewer for details.
Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Stable (1).
Symatec suggests within http://www.symantec.com/business/support/index?page=content&id=TECH184095
to restart the MS Exchange Replication Service – BUT the mentioned eventID
8229 isn´t present on any of the both Mailboxservers.
The affected Database is active on Location2-Exc1-Mb1 Server and in an overall healthy state. I found during my research, that below Location2-Exc1-Mb1 Server, there are not removed shadow copies present!
This confuses me, since all Backups are normally taken from the passive copy of a Database.
So my questions to the board are:
* Does anyone is facing similar issues?
* Can someone explain why snapshots are present on the Mailboxserver hosting the Active Database, whilst the errors are logged on the passive one?
-          * Does someone know the conditions, why shadows copies remain and
aren´t removed in a proper manner?
What can cause the circumstance, that only 1 DB is facing such issues?
Any suggestion is welcome!
BR
Markus

Hi Lenora,
I´ve encreases VSS / Exchange Backup Log levels to expert, before starting
those things i´ve all tried now:
- Backup from passive DB (forced within Symantec Backup Exec)
- Backup from active DB (forced within Symantec Backup Exec)
- Backup from passive DB without GRT enabled (forced within Symantec Backup Exec)
- Backup from active DB without GRT enabled(forced within Symantec Backup Exec)
All those attempts failed.
But brought some more details - the backup against the active DB states, that there is still a backup in progress and therefore this backup is cancelled by VSS.
The Solution was, that i´ve needed to restart the Exchange Replication Service on the Mailbox Server hosting the passive DB.
Backups are working again on all DBs!
THX for your replys.
Best regards
Markus

Windows Update Client failed to detect with error 0xc8000247 after using Lenovo System Update 5

My Windows 7, SP1 was running fine, until I installed few updates on 10/15 using Lenovo System Update 5 then Windows Update stopped working, shows as RED:
{CE3119AD-35EF-41CF-9C21-C7698FEB8393}   2013-10-14 21:53:00:256-0700   1   147   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Software Synchronization   Windows Update Client successfully detected 4 updates.
{EB17A01A-EB6E-49FF-9EA2-AA0DD063B4B1}   2013-10-15 04:15:54:069-0700   1   162   101   {C61A0D00-3E51-48AC-B0AF-1D3E02B9E5D3}   201   0   AutomaticUpdates   Success   Content Download   Download succeeded.
{77DAE88F-2795-4258-8BBF-8D27E53662CF}   2013-10-15 12:10:38:196-0700   1   193   102   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Content Install   Restart Required: To complete the installation of the following updates, the computer must be restarted. Until this computer has been restarted, Windows cannot search for or download new updates: - Security Update for Windows 7 for x64-based Systems (KB2862330)
{1398F777-3AEF-4D1D-BE4C-407EC4AEAD4C}   2013-10-15 12:15:25:676-0700   1   183   101   {C61A0D00-3E51-48AC-B0AF-1D3E02B9E5D3}   201   0   AutomaticUpdates   Success   Content Install   Installation Successful: Windows successfully installed the following update: Security Update for Windows 7 for x64-based Systems (KB2862330)
{A220898A-E5FE-4FE7-8413-2B0C7B4013D0}   2013-10-15 12:15:25:766-0700   1   202   102   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Content Install   Reboot completed.
{A5400FF2-33ED-4A47-8409-13E5DFE16A6D}   2013-10-15 19:29:31:486-0700   1   147   101   {00000000-0000-0000-0000-000000000000}   0   0   ChkWuDrv   Success   Software Synchronization   Windows Update Client successfully detected 0 updates.
{43C533EE-775D-445E-A652-06648B72DE65}   2013-10-15 19:29:49:702-0700   1   147   101   {00000000-0000-0000-0000-000000000000}   0   0   ChkWuDrv   Success   Software Synchronization   Windows Update Client successfully detected 0 updates.
{D6AAAFFB-7F18-4A7E-B39D-1BA09CDC5E6D}   2013-10-15 19:30:05:744-0700   1   147   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Software Synchronization   Windows Update Client successfully detected 3 updates.
{4E73B1C1-5BA2-415D-AB34-92F7AB3DB418}   2013-10-15 19:30:08:753-0700   1   147   101   {00000000-0000-0000-0000-000000000000}   0   0   ChkWuDrv   Success   Software Synchronization   Windows Update Client successfully detected 0 updates.
{51248882-41AC-4E59-B813-87AD326310AD}   2013-10-15 20:00:05:044-0700   1   183   101   {DBD3B4E9-0357-47DA-8317-D0CF2163BFE6}   501   0   wusa   Success   Content Install   Installation Successful: Windows successfully installed the following update: Hotfix for Windows (KB2661796)
{FB2B8E5E-442C-4E76-B23D-6A41B4324C9D}   2013-10-16 00:11:39:832-0700   1   148   101   {00000000-0000-0000-0000-000000000000}   0   c8000247   AutomaticUpdates   Failure   Software Synchronization   Windows Update Client failed to detect with error 0xc8000247.
Lenovo Thinkpad W500, Intel (R), Windows 7, SP1, latest updates as of Oct 15
(1) Checked Setting, set to automatic update whenever, even changed to never update, rebooted the OS and changed back to automatic update and rebooted the OS.
(2) Stopped Windows Update Services, renamed SoftwareDistribution folder and started the window update services and rebooted.
(3) Ran MS FIXIT
(4) Ran System File checker Scan (sfc /scannow)
(5) Ran CHKDSK /F
(6) Installed "Intel Rapid Storage Technology" drivers from Lenovo site
(7) Ran Update for Windows 7 for x64-based Systems (KB971033)
None of the above possible recommended solutions were able to fix the issue yet and now I am getting a message your Window is Not Genuine!
Any help or guidance is appreciated.
Solved!
Go to Solution.

The Lenovo System Update installed the "Intel Matrix Storage Manager driver 8.9.2.1002" right before the Windows Upgrade got broken. So in the Device Manager under IDE ATA/ATAPI Controllers, I choose Intel ICH9M-E/M SATA AHCI Controller, on the Driver Tab, I choose the option "Roll Back Driver" and after rolling back the driver and restarting the OS, now Windows Update is working like a Champ!
The End!

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.

Nvidia 52.16 with errors

Similar Messages

Maybe you are looking for