Re: SBS 2003 and Great Plains problem - SOLVED



I got it working. I don't know what the cause was or what fixed it but I now
have a new instance of MSDE working and the SBS backup also works. I deleted
all the leftover files from the other tries at installing a new instance. I
then stopped the SBSMONITORING and SHAREPOINT instances as well as SQLAgent.
The first time I tried to install a new instance the install quit with an
error. A quick Google search didn't turn up anything that looked likely. I
deleted the leftover files from this install and tried again with the exact
same setup command. This time it installed with no errors. I set the new
instance service to automatic and rebooted. I started SQLAgent for the new
instance and set it to automatic. Both of these I had done on previous
tries. I then tried NTBackup of the System State. It paused for a long time
at the start where it says "Preparing to backup using shadowcopy". It
stalled there for about fifteen minutes but this time the disk was being
accessed continuously. Previously when it stalled here there was no disk
activity. Then it started copying files and finished with no errors. I don't
know if stopping the other MSDE instances was the fix but it was the only
thing I did different from the previous tries.

--
Kerry
MS-MVP Windows - Shell/User
http://www.vistahelp.ca


Kerry Brown wrote:
I have a customer who wants to run Great Plains 9.0 on their SBS 2003
SP1 server. The MS partner that sold them Great Plains doesn't seem
to know much about setting it up on SBS so I am testing it on a test
server for the customer before they install it on their server. They
will be using MSDE with Great Plains as they have SBS 2003 Standard.
According to the GP documentation this is a supported configuration.
When I installed the MSDN version of Great Plains 9.0 on my test
server everything installed, I created a new MSDE instance, Great
Plains found it and was happy. The problem occurred when I tried to
backup the server. I couldn't use the SBS Backup or do manual backups
with NTBackup. It failed when trying to create a shadow copy. The
error was:
Error returned while creating the volume shadow copy:0xffffffff.

Searching the Internet and the MS KB gave me quite a few things to
try to fix it but none of them worked. Uninstalling GP 9.0 and the
MSDE instance then rebooting the server fixed it. I'm thinking it is
the MSDE instance causing the problem. This is the command line I
used to install MSDE
setup SAPWD=password SECURITYMODE=SQL INSTANCENAME=GreatPlains

This created a new instance called GreatPlains with the correct
password. GP 9.0 could connect to it OK.

Have I setup MSDE wrong? Is there something I have to do other than
this to get the backup working with the new instance of MSDE?


.



Relevant Pages

  • Re: SBS 2003 and Great Plains problem - NOT SOLVED :(
    ... It doesn't matter if the new instance of MSDE is ... It did before the reboot. ... install a new instance the install quit with an error. ... server for the customer before they install it on their server. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Great Plains problem
    ... SQL Server VSS Writer ... restarted ALL sql related services and then ran a backup ... If you think installing patches and security updates is expensive, ... They will be using MSDE ...
    (microsoft.public.windows.server.sbs)
  • Re: Wrong MSDE installed
    ... That is the command line to install a new default instance. ... This will upgrade the existing instance but do nothing to get SBS Monitoring and Sharepoint installed. ... They use WMSDE not MSDE. ... those folders are as you say on my SBS 2003 server that has been upgraded to SP1. ...
    (microsoft.public.windows.server.sbs)
  • Completely remove MSDE
    ... On a server that I'm working on, there was previous versions of MSDE ... I am trying to install ... Veritas Backup Exec version 10 on this server now. ...
    (microsoft.public.sqlserver.msde)
  • Re: Issue with VSS on W2K3
    ... As a troubleshooting step I stopped the SQL instances one at a time and tried a backup. ... On the real server I was running a script to stop the offending MSDE instance before doing the backup then starting it afterwards. ... Once we stop the hung VSS service we do that and it will allow us to do ...
    (microsoft.public.windows.server.general)