Some other info:

I am running Server 2003, and SEPM 11.06 MP1.  This is what I was running before I ran into the issues and had to re-install so this is the backup I have.  

I first installed 11.06a and then I ran 11.06 MP1.  

When I start the server configuration wizard it just leaves the embedded database service state as "starting" and it never actually starts.  

I have tried running backup and restore and I also get an error.  I guess it's because it can't connect to the new empty database as it can't start it.

I have tried overwriting the new db folder with my backup db folder and this still doesn't work as I am still unable to start the service.

Any ideas?

Not sure if this helps either.   This is the content of the upgrade.log file in the tomcat folder: 

Check if u have any process using port 2968

While restoring the DB; the sepm version from which it was backed up should be  of same version.

Hi Rafeeq

After many re-installs, reboots and all sorts of other things I am now back online.  My problem now is that I am back to square one....

The whole reason I uninstalled and re-installed was because as soon as I start the SEPM service my page file slowly starts to increase and then after around 3 hours I get either virtual memory warnings or the server just crashes.  It is definitely something to do with SEPM.

Do you have any ideas?  Also, when I look in task manager I see LOTS of java.exe processes, some of which are using A LOT of memory.  Somehow these are created when starting the SEPM service and these cause the paging.  How can I stop this happening?

Can I run some tools or diags and get an idea of what is happening and prevent it? 

Thanks

James

Thanks Vikram

Is this a known issue?  Will this solve my problem?

What I am now thinking of doing is creating a Windows 2008 Server VM on VSphere ESXi and installing SEPM on this.  Do you know if this will work?  Do you know how I can migrate all of my policies across and get my clients talking to this new server? I want to ditch this server and its database as I believe the problem lies within a corrupt db.

I have backed up all of my policies and I have my private key too.

James

changing that value didn't work.

Thanks Vikram. Will this work fine on an VSphere ESXi 4.0 Windows Server 2008 R2?

Do I need to use my private key or shall I just ditch it?

I am getting a little bored of having to babysit this thing.  I used to love Symantec but their software appears to have become rather flaky and the support on the 0870 606 6000 is appalling!  It's like the advisors are learning themselves!

Try running upgrade.bat from  ..\SEPM\bin\upgrade.bat once the database is restored.

The reason why i am saying is because of the log snippet

"Result: Can't connect to database at this moment. You may need to upgrade manually.

Server is not configured correctly, please run Server Configuration Assistant!"