Re: SBS 2003 and Great Plains problem

I've had similar issues with running SQL 5 Express. The VSS MSDE writer
fails.

See http://support.microsoft.com/Default.aspx?kbid=912414

For me the following process had the .\username format:

SQL Server VSS Writer

I changed that, restarted ALL sql related services and then ran a backup
from the Server Manager. It hung for a while at "preparing to backup from
shadow copy services" but then suddenly it started to copy data over.
--

Regards,
Mark Crall, MCP
Charlotte Tech Care Team
Charlotte SBS Group Lead (www.sbs-charlotte.com)
CITPG IT & Meetings Director (www.carolinait.org)

Direct: (704) 248-8328 x33

If you think installing patches and security updates is expensive, try not
installing them.

"Kerry Brown" <kerry@xxxxxxxxxxxxxxxxxxx*a*m> wrote in message
news:uMhXKNc2GHA.2196@xxxxxxxxxxxxxxxxxxxxxxx
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?

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




.

Relevant Pages

  • Re: 2 Applications With MSDE
    ... > Since MSDE SP2 it just doesn't work anymore. ... I do not know what kind of service pack level hase been applied to Veritas ... upgrade tha instance yourself downloading and installing the sp3 from ... it is not mandatory that all MSDE/SQL Server ...
    (microsoft.public.sqlserver.msde)
  • Re: MSDE installation fails
    ... Whether installing Veritas Backup Exec, Microsoft SUSW, or any other ... program that needs to add an instance of MSDE it bombs. ... SQL Server does not exist or access denied. ...
    (microsoft.public.windows.server.sbs)
  • Re: MSDE installation fails
    ... Whether installing Veritas Backup Exec, Microsoft SUSW, or any other ... program that needs to add an instance of MSDE it bombs. ... SQL Server does not exist or access denied. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Great Plains problem - NOT SOLVED :(
    ... It doesn't matter if the new instance of MSDE is ... but I now have a new instance of MSDE working and the SBS backup also ... 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)
  • 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)
Loading