So I started getting strange backup reports on a server last week saying that it had failed with some VSS error. So I went investigating and found the following errors in the event viewer:

Backup_errors_small Backup_errors2_small

 

[spoiler title=”The actual error codes are”]

Event 518, Microsoft-Windows-Backup

Backup started at ’11/12/2013 12:00:22 PM’ failed as another backup or recovery is in progress. Please re-run backup.

 

Event 1, SQLVDI

SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=3352. Thread=7288. Client. Instance=MICROSOFT##SSEE. VD=Global\{8E68F739-4463-4710-A965-02CB141F7345}1_SQLVDIMemoryName_0.

 

Event 3041, MSSQL$MICROSOFT##SSEE

The description for Event ID 3041 from source MSSQL$MICROSOFT##SSEE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

BACKUP DATABASE model

The specified resource type cannot be found in the image file

 

Event 24583, SQLWRITER

The description for Event ID 24583 from source SQLWRITER cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

ICommandText::Execute
0x80040e14
SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: A nonrecoverable I/O error occurred on file “{8E68F739-4463-4710-A965-02CB141F7345}2:” 995(error not found).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Native Client
Error message: Processed 0 pages for database ‘msdb’, file ‘MSDBData’ on file 1.

the message resource is present but the message is not found in the string/message table

Event 3041, MSSQL$SBSMONITORING

BACKUP failed to complete the command BACKUP DATABASE model. Check the backup application log for detailed messages.

Event 18210, MSSQL$SBSMONITORING

BackupVirtualDeviceFile::SendFileInfoBegin:  failure on backup device ‘{7D8BEEF1-F3C5-48B9-804E-58B5DC189C4A}1’. Operating system error 995(error not found).

Event 3041, MSSQL$SBSMONITORING

BACKUP failed to complete the command BACKUP DATABASE msdb. Check the backup application log for detailed messages.

Event 2007, ESE

Information Store (900) Shadow copy instance 10 aborted.

Event 24583, SQLWRITER

The description for Event ID 24583 from source SQLWRITER cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

ICommandText::Execute
0x80040e14
SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: A nonrecoverable I/O error occurred on file “{7D8BEEF1-F3C5-48B9-804E-58B5DC189C4A}3:” 995(error not found).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Native Client
Error message: Processed 0 pages for database ‘SBSMonitoring’, file ‘SBSMonitoring’ on file 1.

Event 3355, Windows SharePoint Services 3

Cannot connect to SQL Server. np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query not found. Additional error information from SQL Server is included below.

Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

 

[/spoiler]

So I followed my nose and found this Microsoft technet article on Windows Server Backup May Fail Because of the SQL VSS Writer which basically says that this error may be caused by an error in a different database and gives an example of the SBSMonitoring database has errors in it.
In my event logs there were some errors with the SBSMonitoring database(event id 3041 and 18210).

So then I found an technet article on how to recreate the SBSMontitoring database so I followed the steps on there and ran the Powershell script that is attached to the article.

That nights backups still had the same problems and still through out a heap of errors in the event logs.

I thought it could be the SharePoint database which I was a bit worried about because I have spent hours fixing a SharePoint installation about a year ago. Refer to this post on SharePoint cannot connect to configuration database error for more information on that saga.

I then thought what would happen if I recreated the backup job. So I deleted the backup job that was running and made a new one.
That nights backup on the Small Business Server worked!!
I am not sure if the recreation of the SBSMonitoring database had anything to do with the problem but those were the steps I used to fix the backup problem. Hopefully this doesn’t reoccur but if it does I will update this post with more information.

 

If you have had the same problem please comment with how you fixed it and if you needed to recreate the SBSMonitoring database.

 

You may also like:

SBS2011 – Administrator “Administrator Name” Does not have Exchange administrator rights.

SharePoint cannot connect to configuration database error after installing KB2687442 update on SBS Server 2008

Read More →
Replies: 0 / Share:

This video will show you how to recover your email password from the following email applications:

  • Outlook Express
  • Microsoft Outlook 2000 (POP3 and SMTP Accounts only)
  • Microsoft Outlook 2002/2003/2007/2010/2013 (POP3, IMAP, HTTP and SMTP Accounts)
  • Windows Mail
  • Windows Live Mail
  • IncrediMail
  • Eudora
  • Netscape 6.x/7.x (If the password is not encrypted with master password)
  • Mozilla Thunderbird (If the password is not encrypted with master password)
  • Group Mail Free
  • Yahoo! Mail – If the password is saved in Yahoo! Messenger application.
  • Hotmail/MSN mail – If the password is saved in MSN/Windows/Live Messenger application.
  • Gmail – If the password is saved by Gmail Notifier application, Google Desktop, or by Google Talk.

This is using a small mail password recovery utility called Mail Pass View which is by a software developer called Nirsoft. Nirsoft make a lot of free password recovery utilities and all the ones I have tried work well.

All you need to do for this to recover your email password with this software is download it and then run it. It is that simple.

This is really useful when you need to migrate a user to a new PC because it seems a lot of users (especially business users) do not know their email password. Then when you are running up the new computer you can run the Mail Pass View utility and recover the email password then apply it to the new system you are migrating to.

Read More →
Replies: 1 / Share:

The start screen is an addition to Microsoft Office that I personally do not like.

Thankfully there is a registry hack that can disable the Microsoft Office start screen that will make you open your programs (word, excel, publisher, etc.) alot quicker and also stop you from getting annoyed every time you start the program because it comes up with a stupid menu.

To do this you need to:

  • Open the registry editor (start menu and type in “regedit” without the quotes
  • Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\General
  • Then you will need to add a registry key by right clicking and selecting new dword 32bit value
  • Then call the new key “DisableBootToOfficeStart” (without the speaking marks)
  • Then open this key and 1

Now when you open your Microsoft Office programs you won’t need to be greeted with that pesky office start screen!
You can

through that link!

Read More →
Replies: 0 / Share:

Internet Explorer Enhanced Security Configuration settings define how users browse the internet and reduce the exposure of your server to potential security risks. This can minimalise the risk for users of the server to be able to load active content and keep you Windows Server safer.
This can get quite annoying when you need to download something onto your server, so today I will show you how to disable Internet Explorer’s Enhanced Security.
Once you have finished what you are doing I recommend activating the Enhanced Security again so that it minimalises the risk for other users when browsing the internet on you server

Read More →
Replies: 0 / Share:

So I was installing SharePoint Server 2012 on my VMWare Virtual machine for some videos I am making yesterday and it through up this really strange error “Error 1335”, the strange part was that it was in what I believe to be Spanish.

Error 1335 SQL 2013 Install

Error 1335. El archivo.CAV “Proof.CAB” que se necesita para esta
instalacon esta danado o no se puede usar. Esto puede indicar un error de 
red, un error al leer desde el CD-ROM, o un problema con esta paquete.:
Error 1335. El archivo.CAV “Proof.CAB” que se necesita para esta
instalacon esta danado o no se puede usar. Esto puede indicar un error de 
red, un error al leer desde el CD-ROM, o un problema con esta paquete”

Honestly this had me baffled, I cannot read Spanish so I had no idea what it meant.

Then I started researching. It turns out that this error simply means that the SharePoint installation cannot find the install files, which in my case was a mounted ISO file.

So I unmounted the ISO file and remounted the file and then pressed retry. Presto!! The installation went on.

I’m not sure why the error comes up in Spanish but at least it is easy to fix.

Read More →
Replies: 0 / Share:

The remote session was disconnected because there are no Terminal Server client access licenses available for this computer

 

If the error “The remote session was disconnected because there are no Terminal Server client access licenses available for this computer” shows up when you are trying to connect to your terminal server it is caused by one of  two problems.

The first is that you have run out of licenses on your Terminal Server user CALS. These CALS specify how many users can be logged into the terminal server at one time. So if you have 5 Terminal Server user CALS then there can only be 5 sessions logged into the terminal server at one time.

If you are receiving the error because of exceeding user count the only way to fix the issue is to buy more Terminal Server user CALS.

 

The second problem exists on the computer that is trying to log into the problem. This error is resolved by deleting some registry keys on the host machine.

Step 1: Open the registry editor (Start menu – Run – Then type in “regedit” with out the quotes)

Step 2: Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSLICENSING

Delete these keys
Delete these keys

Step 3: Delete all the keys in MSLICENSING

Step 4: Test the remote connection

Once the keys are deleted the remote desktop connection should work again. It will automatically remake the keys upon starting remote desktop.

Read More →
Replies: 1 / Share:

Outlook 2013 and Exchange 2003

Warning; Buying Office 2013

So you may have upgraded to Microsoft office 2013 and gone to connect your email to an exchange account and then you will see two error boxes come up, the first one says:

The resource that you are trying to use is located on an unsupported version of Microsoft Exchange. Contact your e-mail administrator for assistance.

The second window says:

Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The file (then the file path) is not an Outlook data file (.ost).

It seems that Microsoft Exchange 2003 is not supported by Outlook 2013. At the moment I do not know of any work around, if you do please leave a comment in the section below.

Snippet from the Office 2013 known issues page:

Error when connecting to Exchange 2003

When you configure Outlook 2013 for an Exchange 2003 account, you can get the following error message:

The resource that you are trying to use is located on an unsupported version of Microsoft Exchange. Contact your e-mail administrator for assistance.

Workaround    Outlook 2013 isn’t supported on Exchange 2003 and connectivity is blocked. Please connect Outlook 2013 to Exchange 2007, 2010, or 2013.

This is one of the things you need to be aware of if you are still running exchange 2003.
You can

through that link.

Read More →
Replies: 0 / Share:

IIS is the Web Server component of Windows. It is included in your normal Windows installation but it is a stripped down version. We will be using the Windows Server version of this software which is much more rich in features.

 

Read More →
Replies: 0 / Share: