Home > Symantec System > Symantec System Recovery 2013 Error 1935

Symantec System Recovery 2013 Error 1935

thank you. 0 Kudos Reply Contact Privacy Policy Terms & Conditions Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Marked as answer by Donia Strand Wednesday, September 12, 2012 4:07 PM Wednesday, December 29, 2010 5:15 PM Reply | Quote All replies 0 Sign in to vote if the fix-it Installed a ____ load of vc++ redistributable package - didn't work, of course stuck on the 2005 SP1 x64. Thank You! http://netlookmag.com/symantec-system/symantec-system-recovery-2013-fatal-error-1935.html

Could it be rebuilt quickly if a troubleshooting step went awry? Then do whatever you have to do to get your software/services running again. Nor did the link within that post help the other users who posted. No Yes Did this article save you the trouble of contacting technical support?

Other products I'm not sure Help for other Norton Products: Norton Internet Security & AntiVirus for Mac Norton Security Suite for Comcast Norton WiFi Privacy Norton Small Business Norton Identity Protection Whilst most threads advise running "sfc /scannow" I get an error as shown below. - sfc /scannow = "Windows Resource Protection could not start the repair service." (Yes I was admin) STEP2 Install Symantec pcAnywhere Insert the Symantec pcAnywhere CD into the CD-ROM drive. No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES

I found out the hard way it isn't worth troubleshooting. In order to access the desktop when this error takes place, you have to restart it an open using the safe mode. Please download Symantec System Recovery 2013 R2 from Evaluation or MyVeritas portal, and upgrade to Symantec System Recovery 2013 R2. Click Advanced system settings at the top left of the window.

You may also refer to the English Version of this knowledge base article for up-to-date information. Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Vision 2016 Vision 2016 Blog The only microsoft support KB entry that deals with this error only is for Windows 7, so the Fix It tool can't be run: http://support.microsoft.com/kb/970652 Monday, December 13, 2010 7:52 PM Please contact your Symantec Sales representative or the Symantec Partner for upgrade information including upgrade eligibility to the release containing the resolution for this issue.

Thursday, December 23, 2010 4:45 PM Reply | Quote 0 Sign in to vote Hi All I have the Same_D_n_Problem.... D: ), edit the command accordingly. 3. And, I have no idea how items were missing in the WinSXS folder as these are two identical servers, installed the same way and with the same software, and only one Option 2 suggests reinstalling the windows installer, but there is no redistributable Windows 5.0 installer and that's what Windows Server 2008 R2 uses.

Friday, December 17, 2010 9:54 AM Reply | Quote Moderator 0 Sign in to vote I'm working with Microsoft on this issue and will post once resolved. Those keys don't exist, otherwise the fix it tool would work. And now i'm having this problem when im trying to install OpenOffice.org. Thanks.

No Yes Did this article save you the trouble of contacting technical support? this contact form CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical So, I don't have time to troubleshoot it anymore, I'm building a new server (and I don't want a server that's had the in place upgrade run on it anyway, even In the Run dialog box, type the following text: msconfig If the User Account Control window appears, click Yes or Continue.

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Error Message MSI (s) (08:88) [14:51:53:932]: Windows Installer installed an update. If you feel it is related to corrupt .Net Framework, I suggest removing .NET Framework using the removal tool: 1. http://netlookmag.com/symantec-system/symantec-system-recovery-2013-error-codes.html Also with the Repair Disc I ran the command line and ran sfc /scannow with the hope that permissions would be off outside of W7.

Privacy statement  © 2016 Microsoft. Sorry, we couldn't post your feedback right now, please try again later. I also tried reganul or whatever it was...this thing, so far is BULLETPROOF!

If you are getting this 1935 error, and the simple fixes mentioned in earlier postings don't work, I recommend reinstalling Windows from scratch on that server.

I didn't want to wait for C++ to come down on its own, if it was going to, since it isa SQL Server pre-req't. However, I WAS able to download and install the VC++ 2005 Redist x_64 after removing the one that was there.... I had also already rebooted from the first round of updates, this was when it was on its 2nd. Since it is a Visual C++ related installation issue, I suggest discussing it in Visual C++ General forum.

Thanks! criley Moderator Employee Accredited ‎08-05-2014 02:53 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Does your issue match this? Microsoft walked me through finding what files were missing from the WinSXS folder and tried installing those files on the machine with the issue. http://netlookmag.com/symantec-system/symantec-system-recovery-2013-error-e1adfa8b.html Product Version: 11.0.1.47662.

No Yes How can we make this article more helpful?