joseph bittman mcad

July 23, 2005

I ran into a similar problem. I assume you installed DPM with the Eval
editions of SQL Server? I believe this happens (actually I had this happen
EVERY time) when you create a password for the SQL SA account. When I
stopped creating a password for this account, then everything went fine.
When I installed SQL myself and didn't use the evals, I also found that
specifying a password while upgrading the instance to SP3a before installing
DPM, also broke DPM once it was installed. Did you do either of these
things? Thanks and have a great day!

--
Joseph Bittman
Microsoft Certified Application Developer

Web Site: http://71.39.42.23
Static IP

prashant kumar [msft]

Hi Joseph

Specifying the sa password should not affect the DPM installation. The only
related thing you need to take care is to choose "Windows authentication"
mode when manually installing SQL Server for DPM.

We have not observed this to be broken in our testing. Can you elaborate the
steps that lead to the observed behavior? Did DPM setup succeed and then
later you ran into error 941? Please run the DPM bug tracing tool and submit
a bug with the tracing information if this error can be reproduced.

Thanks,
Prashant

--
Prashant Kumar [MSFT]
**This posting is provided "AS IS" with no warranties, and confers no
rights.

joseph bittman mcsd

August 5, 2005

Can I email you something under NDA, so I don't have to file a bug for a
sentence or so? pkumar@online.microsoft.com?

--
Joseph Bittman
Microsoft Certified Solution Developer

Web Site: http://71.39.42.23
Static IP

prashant kumar [msft]

Joseph,
It would be best if you filed the bug at betaplace. That helps to keep track
of all issues at one place.

--
Prashant Kumar [MSFT]
**This posting is provided "AS IS" with no warranties, and confers no
rights.