Error ID 3023:
DPM is unable to configure the Windows account because the password
you entered does not meet the Group Policy requirements. (ID: 3023)
I received this message right after selecting the DPM installer to install SQL, on the next screen, it asks for a password for the service account to use. Note, that this creates a two local accounts, using the password provided in the installer. Time after time, I kept getting this error ID 3023. Strange thing, I was able to go to computer management, add a local account, using the exact same name and password that the DPM installer was trying to do, and it would work!?!? But when the installer did it, it would fail.
This error was a HUGE problem, and caused me a great deal of stress, so, I wanted to pass on the solution, so nobody else needs to have this heartache!
My first troubleshooting steps were to block all group policy to the OU the computer account was in, perform a gpupdate /force and restart the server. This didn't work. Same error message.
Next, I created a local admin account, logged in with it, and tried to install DPM with it - no go, as the installer needs to communicate with Active Directory.
Then, I tried installing SQL 2005, and SQL 2005 SP2 manually. The install when OK, albeit, the SQL install took an unusually long time to install. I remembered something from a long time ago, that I was installing SQL, and it would hang for hours during the install, while setting permissions, and the trick was to unplug (or disable) the NIC during the install, and it goes right through without issues! I did this, and the SQL install went through nice and quick!
So, Now I had SQL installed, back to the DPM installer. So I choose the option for an existing SQL instance, and don't you know, that only works if the SQL is NOT on the same box as you are installing DPM? ARGH!!!
Uninstalled SQL....
Well, I had an idea - I had to disable the NIC for the SQL trick, maybe I can do this with DPM? So, I disable the NIC, and start the installer. Failed the pre-requisite check, saying it couldn't communicate with Active Directory. So, enabled the NIC, started the installer, got past the pre-requisite check, then disabled the NIC, selected for DPM to install SQL, clicked next, said a little prayer, and entered the password.... clicked next..... AND IT WORKED! I was couldn't believe it worked! So, I enabled the NIC again, and let the installer go to work.
All was good, until the installer was done installing SQL, and SQL SP2, it started the DPM portion of the install, and it failed, with this error:
*** Error : Report configuration failed.
Verify that SQL Server Reporting Services is installed properly and that it is running.
ID: 812
Now oddly enough, this error references that SharePoint Services is installed on the same machine, and there are certain steps in order to make SQL for DPM and SharePoint Services to work correctly together. Well, that's great, except for the fact that I DIDN'T have SPS installed on the box!
Well, I ran through the installer again, disabling the NIC before the password, entered the password, enabled the NIC, and got to the DPM install portion again, and watched it fail on the section of setting security. BINGO! that's the same place that SQL was messing up before! So, start over, Disable the NIC for the password, enable it again, wait for the installer to get to setting security during the DPM install portion, and disabled it again....
Survey says!? Success!!!! After the security, the installer finished in a few minutes, and I enabled after the install was complete. I enabled the NIC, restarted the box, and I was finally in business!
I hope this helps somebody else out there, I know it was a bear for me! If you have any questions, please comment, and I'll be glad to answer them if I can! Good luck!
6 comments:
WRT the existing SQL install...
According to the docs it sure seems like you should be able to pre-install a default instance of SQL 2005 apply SP2 and then get on with it.
From http://technet.microsoft.com/en-us/library/bb808868.aspx
"If you do not want to use the dedicated instance for DPM, you can use another instance name or you can install SQL Server on a different computer."
But then further down in Step 11.:
"On the Instance Name page, select Named instance, type MS$DPM2007$, and then click Next."
Grrr so which one is it Microsoft, MS$DPM2007$ or "another instance name"?
BTW, I'm doing this on Server 2008 and my point of failure is at that same SQL selection screen and I get the error:
Setup has detected that the installation of Reporting Services is not correctly configured or no instance of Reporting Services is linked to MS$DPM2007$ of SQL Server.1)To use the local dedicated MS$DPM2007$ instance with DPM, uninstall SQL Server and run setup again.
2)To use the option of installing DPM with an existing instance of SQL Server, make sure that the Reporting Services instance is also installed and linked correctly. For details, refer to DPM Setup Help.
I'm keeping up the fight... ;)
I would stick with MS@DMP$2007 as the instance name - DPM is fragile enough as it is, so why mix things up? :) I did try installing SQL manually, as well as SP2 from the TechNet documentation, but when the DPM installer runs, it has to touch SQL, and that is when I had to unplug the NIC.
Hope this helps!
So I took your advice (uninstalling, then reinstalling SQL with the special named instance) and was midway through the SQL install when there was another Ah ha! moment... I had neglected to follow the directions to customize each individual SQL Service logon account to be—as applicable—Local System, Network Service, or Local Service. So we have MS recomending a non-Best Practices installation of SQL. Ahem! Everyone is running their SQL servers with a least privlige domain user account right? ;)
Hmmm, oh well...continuing on... X__X
So, SP2 and post SP2 security fixes went on fine and then DPM setup gets through all preReq checks. So then I specify existing SQL and enter in localhost\MS$DPM2007$ and administrator account info. Interesting msg pops up...I can't use the special DPM named instance on the local machine BUT go back and have it install dedicated instance and it will detect the already installed SQL and use that (and its Reporting Services).
Voila! I did so and it did indeed detect the already installed SQL Enterprise Ed.! It does change the service logon user account to Microsot$DPM$Acct for both SQL Server Agent and SQL Server Services. Strangely, there is now two instances of SQL Server Reporting Services, one linked to the named instance starting as Network Service and one to the (non-existant) default MSSQLSERVER. Hmm, hopefully I can get rid of that one w/o hosing the whole thing!
So Install looks good with the exception of some error messages needing to be policed in event viewer.
When i went to do the standard install of SQL Server 2005 (to name the default database what DPM wants it to be, I got a message part of the way thru that I had ASP.net 32-bit installed on Windows x64 and that this config would affect Reporting Services... I fixed ASP.net and continued the install; will update if anything else occurs.
Thanks for the tip. Disconnecting from the network during the SQL server install helped me out.
Hey All,
I get the
*** Error : Report configuration failed.
Verify that SQL Server Reporting Services is installed properly and that it is running.
ID: 812
during the installation process. I tried disabling the NIC and enabling again at all the places mentioned, but it STILL gives me the error when it starts with "deploying reports" steps after the security checking steps.
Post a Comment