You are browsing the archive for 2010 September.

DPM SQL Management Studio: Evaluation has expired

6:22 am in Uncategorized by mikeresseler

On the forums, we got a notification from a user that he got the following error when trying to open the SQL Management Studio from DPM.


I had asked him to check if it was a licensed version and so it was.  This intrigued me and I decided to check a few things.  On my test environment, I received the exact same notification although DPM and SQL were still running.  Because my test environment was an upgrade from beta to RC to eval, I figured that it had to do something with the upgrade, and the fact that the first instances of SQL were installed with evaluation versions.

So I decided to ask for the help of the MVP’s and very soon (actually from minute one :-)) I received answer from Kenneth Van Surksum, Artem Pronichkin and Denny Cherry with possible solutions.

Apparently, there are two versions of this problem.

1. Only the SQL Management Studio has expired.  This is the problem when you did the upgrade path from the Beta 1 because that was still with SQL 2008 evaluation without SP1, and this was fixed in SP1.  To fix it now, you can follow KB 971268 (


2. The second issue is that SQL itself has also expired, which strangely leads that DPM continue to work, until the first time that you need to restart the SQL server or restart the server itself (everybody needs to patch right :-)) This is discussed in KB 2020443 (

So in the end, if you are facing or the Management Studio expiration, or after a restart the the SQL instance doesn’t start, then work with the solutions and it will be fixed

Thanks for the assistance guys



From the forums: DPM is unable to enumerate Virtual SSP Writer on computer [computer name]. (ID: 3005)

4:38 pm in Uncategorized by mikeresseler

This is an interesting one that I found on the forums.  Normally, when you get this error message, this is the advice that I give:

1. Is the SPWriter service running on the WFE servers?

2. If they are running, use the following to register the writer: (

Or in short: stsadm -o registerwsswriter if you don’t want to go trough the article

3. Do a vssadmin list writers to see if there are errors with the vss writers

4. Run the configuresharepoint again with a farm administrator account

5. Try again


But in this case, and in a few other cases, it didn’t seemed to resolve the issue.  So the problem had to be somewhere else.  Since the issue couldn’t be helped with the assistance of the forum guys, a call was opened with Microsoft.

Unfortunately, the DPM guys couldn’t solve it either.  Therefore, the sharepoint guys had to assist, and in this joint venture, they found the solution:

Here is the quote of the administrator with the problem

Basically, the error was related to the inability to enumerate all resources defined in the farm’s configuration.  What the actual issue was turned out to be a missing database for one of the search services that was configured.

A similar internal MS bug was found that referenced issues with the Search services.  This led us to look at restarting our Search services on all of the servers in the farm.  Even though all of the search services were "running", one of them would not restart and asked to reprovide the credentials and database names, etc.  Before I submitted the restart, I verified on the SQL Server that the database that was referenced, did not exist !  You may ask, "How was SharePoint stating that the service was running if indeed it was not?"  I’m not sure, but after restarting the particular search service, the database was recreated and the VSS enumeration by DPM worked!

So a possible solution (one that worked for me) is to restart all of your search services and ensure that all ‘referenced’ databases actually exist.

So in the end, it was not a problem with DPM but with the Sharepoint config.  Since I found this interesting (a sharepoint farm that worked, but had issues after all :-)) I decided to search a bit more for this issue.  It seems that it happens quite a lot after an inplace upgrade of sharepoint.

So if you ever get this error, the first 5 steps don’t work for you, then make sure that you check out if the databases exist

Forum Source:



DPM 2010 Storage Calculator links

1:38 pm in Uncategorized by mikeresseler

Almost missed this one, but the new storage calculator sheets for DPM 2010 are available for download:







I see many requests for a SQL storage sheet, but you can actually use the sharepoint sheet to calculate SQL storage.  Just not fill in the other data 😉