Attended #MVPTour today, in Po…

Attended #MVPTour today, in Portland Tomorrow is Redmond.
Posted in Uncategorized. Comments Off »

Attended #MVPTour today, in Po…

Attended #MVPTour today, in Portland Tomorrow is Redmond.
Posted in Uncategorized. Comments Off »

Attended #MVPTour today, in Po…

Attended #MVPTour today, in Portland Tomorrow is Redmond.
Posted in Uncategorized. Comments Off »

Attended #MVPTour today, in Po…

Attended #MVPTour today, in Portland Tomorrow is Redmond.
Posted in Uncategorized. Comments Off »

Attended #MVPTour today, in Po…

Attended #MVPTour today, in Portland Tomorrow is Redmond.
Posted in Uncategorized. Comments Off »

Attended #MVPTour today, in Po…

Attended #MVPTour today, in Portland Tomorrow is Redmond.
Posted in Uncategorized. Comments Off »

Attended #MVPTour today, in Po…

Attended #MVPTour today, in Portland Tomorrow is Redmond.
Posted in Uncategorized. Comments Off »

SBS Backup Fails With Error Code “2155348010″

Those that use Windows Backup some FYI’s
SBS2008 SBS2011 and Windows Server Backup is limited to 2TB in total

http://www.sbsfaq.com/?p=2353
So no 2.5 TB Drives in SBS

 In addition Issues with 4096 byte sector size drives…

Microsoft Backup is not designed to work with the large block sector only the 512 byte block sector drives.
(So any drive that has 4096 drives you will NOT be able to back up to it.)

Backup Fails With Error Code “2155348010″
This error doesn’t occur when are using that byte sector as the OS but as a backup drive.

In addition:

Some of these drives you buy for backups are designed for PC Backups (Yes PC’s not servers) Which they will sometime Auto Shutdown, to save energy, and also have other “Energy” saving Features. (Software and sometimes firmware on the drive)

This means that they will sometimes SHUTOFF When they don’t detect I/O for some time and thus you do not get a backup. (This IMO is why you should avoid “GREEN” USB Drives for backups.)

When the HD shuts down of course BACKUPS WILL FAIL!!

This is not Microsoft’s Fault!!!

In addition to shutting down another common issue with these is when you power cycle your server and the USB External Drive does not show up. (Because of the “POWER Save Feature of the drive.)

Because these “Features” are not a Microsoft Issue or there is no way they can fix your drive.

I recommend getting a Drive that is either designed for Server backup, or get a simple USB External Drive case, (Generic with no Energy saving) and put in your own drive.

 Just as a FYI!
Russ
Posted in Uncategorized. Comments Off »

SBS2008 Backup Fails VSS and The wizard cannot retrieve backup settings

I ran into this last week

I was getting VSS errors, So After my usually things I resorted to Try and Reconfigure Backups
However I got Error “The wizard cannot retrieve backup settings”

So I found this KB
http://support.microsoft.com/kb/2001010
But it didn’t help at all!

Writing to Microsoft Shawn Song, Supplied this as an answer I’m posting it here for others to gain from it.

(And this worked)

Suggestion
===========
a. register the dlls with the following command:

Open a DOS Window (Run As Administrator)
Paste the below in it, (Or run each line I just like to copy and paste it does the same thing.)

 cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 ole32.dll
regsvr32 oleaut32.dll
regsvr32 vss_ps.dll
vssvc /register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml3.dll

(You have to select OK for eachone>)
Then do this.

Make sure the following key is correct:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\EventClasses\{FAF53CC4-BD73-4E36-83F1-2B23F46E513E}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}

“TypeLib”=”C:\\Windows\\system32\\EVENTCLS.DLL”

Then right-click it select Permissions.
1.       Make sure these object listed in the Permissions dialog box.

CREATOR OWNER = Special permissions
SYSTEM = FULL CONTORL
Administrators (domain\administrators) = FULL CONTROL
Users (domain\Users) = Read & Special permissions
EventSystem = Read & Special permissions

2.       Then, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VSSAccessControl, below sub-key list here.

NT AUTHORITY\LOCAL SERVICE     [REG_DWORD] 1 (0×00000001)
NT AUTHORITY\NETWORK SERVICE     [REG_DWORD] 1 (0×00000001)
NT Authority\NetworkService     [REG_DWORD] 1 (0×00000001)

3.       If there are other keys listed except above three, please export whole VSSAccessControl key to a *.reg file then remove all key except above three keys. If the value of above three keys isn’t 1, please change to 1.

c. Restart the server and check if the issue persists.
Posted in Uncategorized. Comments Off »

Error returned while creating the volume shadow copy ffffffff

On a Microsoft Windows Server 2003-based computer that is running the Volume Shadow Copy Service (VSS), you experience one of the following symptoms:
  • When you perform a backup operation by using the NTBackup tool, the following event is logged in the Application log: Event Type: Error Event Source: NTBackup Event ID: 8019 Description: End Operation: Warnings or errors were encountered. Consult the backup report for more details.Note If you view the backup log file, the following information is displayed:
    Error returned while creating the volume shadow copy:0xffffffff
  • If you access the properties of a volume and then click Shadow Copies, you receive one of the following error messages:
    Error 0x8004230F: The shadow copy provider had an unexpected error while trying to process the specified operation.
    Error 0×80004002: No such interface supported
  • One of the following events is logged in the Application log:Event Type: Error Event Source: VSS Event ID: 20 Description: Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy Service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance on class with CLSID {faf53cc4-bd73-4e36-83f1-2b23f46e513e} and Name VSSEvent is [0x80040154].Event Type: Error Event Source: VSS Event ID: 20 Description: Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy Service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance on class with CLSID {faf53cc4-bd73-4e36-83f1-2b23f46e513e} and Name VSSEvent is [0x80004002]. Event Type: Error Event Source: VSS Event ID: 8193 Description: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0×80040154. Event Type: Error Event Source: VSS Event Category: None Event ID: 8193 Description: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0×80004002. Event Type: Error Event Source: VSS Event ID: 12302 Description: Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers. Please check to see that the Event Service and Volume Shadow Copy Service are operating properly.

CAUSE
This issue occurs because the VSS system files are not registered….

This issue occurs because the VSS system files are not registered.

RESOLUTION
Note This article is not for use with Windows Vista, with Windows Server 2008, o…

Note This article is not for use with Windows Vista, with Windows Server 2008, or with later operating systems. Starting with Windows Vista and with Windows Server 2008, Windows component installation is manifest based. If you try to manually register specific components, such as those that are described in this “Resolution” section, in the operating systems that are mentioned in this note, unexpected results may occur that may require reinstalling Windows to resolve.
To have us fix this problem for you, go to the “Fix it for me” section. If you prefer to fix this problem yourself, go to the “Let me fix it myself” section.

Fix it for me

To fix this problem automatically, click the Fix it button or link. In the File Download dialog box, click Run and then follow the steps in the Fix it Wizard.
Fix this problem
Microsoft Fix it 50633


Notes
  • This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
  • If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.

Then, go to the “Did this fix the problem?” section.


Let me fix it myself


To resolve this issue, follow these steps:
  1. Click Start, click Run, type cmd, and then click OK.
  2. Type the following commands at a command prompt. Press ENTER after you type each command.
    • cd /d %windir%\system32
    • Net stop vss
    • Net stop swprv
    • regsvr32 ole32.dll
    • regsvr32 oleaut32.dll
    • regsvr32 vss_ps.dll
    • vssvc /register
    • regsvr32 /i swprv.dll
    • regsvr32 /i eventcls.dll
    • regsvr32 es.dll
    • regsvr32 stdprov.dll
    • regsvr32 vssui.dll
    • regsvr32 msxml.dll
    • regsvr32 msxml3.dll
    • regsvr32 msxml4.dll
    Note The last command may not run successfully.
  3. Perform a backup operation to verify that the issue is resolved.


Did this fix the problem?


  • Check whether the problem is fixed. If the problem is fixed, you are finished with this section. If the problem is not fixed, you can contact support (http://support.microsoft.com/contactus) .
  • We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the “Fix it for me (http://blogs.technet.com/fixit4me/) ” blog or send us an email (mailto:fixit4me@microsoft.com?Subject=KB) message.
Posted in SBS2003. Comments Off »