a 6ya Technician can help you resolve that issue over the phone in a minute or two.
Best thing about this new service is that you are never placed on hold and get to talk to real repair professionals here in the US. click here to Talk to a Technician (only for users in the US for now) and get all the help you need. Goodluck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Start the Volume Shadow Copy service by running "net start
vss", do a test backup and see how it goes.
II. If the issue persists,
Let's perform these troubleshooting steps:
1. Make sure you can use OSQL
to connect to every running instance of SQL/MSDE on the box, if you can not
disable all of the instances.
You can find all of the instances installed
on your server, by looking at this registry value:
The syntax would be "OSQL -E -S
For example OSQL -E -S
If you can't connect to the database, then it will
cause this type of failure.
Also make sure that each of the SQL/MSDE
instances is either running under the Local System account or a Domain Admin
2. The issue may occur if there is corrupted data on the drive
to be backed up. Please run CHKDSK on each drive with the /f switch to fix
the errors on the disk (if there are any).
3. Per my experience, this
issue can be due to VSS thinks the system is still in setup process. Please
perform the steps below to check the status.
WARNING: Using Registry
Editor incorrectly can cause serious problems that may require you to
reinstall Windows. Microsoft cannot guarantee that problems resulting from
the incorrect use of Registry Editor can be solved. Use Registry Editor at
your own risk.
Open the registry and locate the registry
Ensure both registry values are
set to 0:
- SystemSetupInProgress - UpgradeInProgress
4. If the
issue still happens, reinstall COM+ by following these steps:
and then delete HKLM\Software\Microsoft\COM3
B. Boot to Recovery console
and rename clbcatq.dll to ~clbcatq.dll. Be sure to use the tilde.
Boot to normal mode and in Control Panel, open the Add or Remove Programs
tool, and then open the Add/Remove Windows Components tool. Do not make any
changes, just click "Next". This reinstalls COM+.
NOTE: You must have
your Windows Server 2003 SP1 files available during this step.
above information helps! I am happy to be of assistance to you and look
forward to your reply!
I presume you did not do a full system backup of your Server 2000 system/boot drive before upgrading to Server 2003? If you did, just restore your Server 2000 backup. If not, then backup all your application data files and re-install Sever 2000 as if it was a new install. Then re-install your application and restore the data files.
Another possibility is to check with your application vendor and see if they have a version that works with Server 2003.
First things First!
1) you always going to have problems with exchange servers, or migrations. ** systems are not perfects**
2) You can migrate the emails to the new server, but, if only are in the correct version of Exchange 2003.
3) if backup is damage or fail, you lost everything.
4) try to reinstall the Server, and all utilites, is better, I know takes more time, but is better because you created yourself.
I suggest you to install from scratch!
Microsoft Windows Server 2003, Web Edition
Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
Microsoft Windows Server 2003, Enterprise x64 Edition
Microsoft Windows Small Business Server 2003 Premium Edition
This problem occurs when the following conditions are true:
You back up data from a volume that contains a Microsoft SQL Server database.
The recovery model of the SQL Server database is configured to use an option that is different from Simple.
Submit a request here to get a hotfix from Microsoft ( Its free and no product key will be asked )