The ahsay online backup failed with the message “Expect log sequence ‘xxx’ but found ‘SERVER\Microsoft Information Store\ First Storage Group\xxxxx.log”

The solution and description to this error is set out below;

The problem occurs because another backup has already initiated a change in the log sequence.

To fix the problem, disable all other backup systems (NT Backup, Backup Exec, etc) and restart the online backup.

For e-mail accounts based on Exchange (as opposed to web based e-mail), Out of Office notification can be configured from Outlook.

Click on ‘Tools’, then ‘Out of Office Assistant’

And fill out accordingly…

I discovered that my Small Business Server (2003) was extremely very slow to respond to basic tasks.  Printers were not working,  browsing files and folders was slow and users were complaining of  overall speed issues. On further inspection, I learned that C:\WINDOWS\system32\LogFiles\ folder had over 6gb of logfiles. The question was, could I delete these files and more importantly, can I prevent this from reocurring?

The solution and description to this error is set out below;

Unless you need to report who is connecting to your (1)  Web site,  (2) and/or SMTP server, you can delete the files in these folders . If you are not interested in this information, you can turn logging off on the SMTP Virtual Server in Exchange System Manager, and on the Default Web Site in IIS Manager.

 To do this;

1. Open IIS. Then right click on your default web site, and from the Web Site Tab, you can uncheck the “Enable Logging” section. Alternatively, you can slect properties and modify the path for these log files to an alternative location.

2. Open Exchange System Manager. Click on Administrative Groups, Servers, <Exchange-db- name>, Protocols, SMTP and right-click on ‘Default Virtual Server’ and select properties. You can also uncheck ‘Enable Logging’ here or again, modify the path in the properties section.

I Hope you too have Found A Fix !!

The Server disk capcity on partition C: was full due to a build up of  exchange log files.

The solution and description to this error is set out below;

In this situation, I had to move the log files from partition C: to partition D:

The following procedure can be used to move the exchange log files and/or the databases to another disk partition.

To move the log files

1. Start the Exchange System Manager.
2. Click ‘Administrative Groups’.Note: If your  ’Administrative Groups’  is not visible, it may not be turned on. To turn on ‘Administrative Groups’, right-click ‘Exchange Organization’ in the Exchange System Manager, and then click Properties. Click to select the Display Administrative Groups check box.
3. Locate the storage group where you want to change log file paths, right-click the storage group, and then click ‘Properties’.
4. Click the ‘General’ tab, and then click on the ‘Browse’ button next to the ‘Transaction log location’ box, and then specify the new drive or folder location for the log files.

 To move databases

1. Start the Exchange System Manager.
2. Open the administrative group that contains the database that you want to change.
3. Under ‘Storage Group’, right-click on the mailbox store or the public folder store that you want to change, and then click ‘Properties’.
4. Click the ‘Database’ tab.
5. Next to the database that you want to change, click ‘Browse’, and then specify a new drive or folder location for the files.

I would like to acknowledge and thank Microsoft for their solution.

I Hope you too have Found A Fix !!

The Microsoft Exchange POP3 service on Windows Server 2003 was stuck in an infinite state of  ”Starting” status after I had tried to manually restart it . After this, it would not respond to “net start” or “net stop” and I was also unable to control it from the services control panel.

The solution and description to this error is set out below; 

Not wanting to restart the server during business hours, I stumbled across this solution.

1. Open Task Manager. [Ctrl+Alt+Delete]

2. Find the process “inetinfo.exe” .

3. Click on ‘End Process’

The service should now start normally.. 

I Hope you too have Found a Fix!