Right firstly let me start off by saying I have really enjoyed reading posts put up by fellow edugeekers and it most definatley has helped me in a few very tight and near misses
Now I need you to put your magic on this - this has done both mine and my senior techies head in!!
From the start then:
We have a sharepoint setup with a seperate SQL 2005 DB for all the data etc. so far so good
We are running our of space on the C: drive on the SQL server so we bought a new server ready to take its place.
It is build, patched, SQL 2005 installed jobs a good-un.
A few options came to mind, reading MS way of doing this was one of them or using virtualistion.
Because it is a critical server we thought we would get an image of the old sql server anyway (being about 9 years old) so virtualisation using the free convertor was carried out. It did this whilst the server was still switched on - BONUS
This is where the fun begins, we bought a license for VMWare workstation installed and confiured the new virtual server, switched off the old sql server and sharepoint servers, used the image from the old sql database and started the virtual workstation
It booted up, wanted to install some drivers it found (USB drivers) and restarted the server. It worked as expected.
(on the VM) the C: Drive was expanded using the VMware command and then using EASUS partition software I expanded the drive.
After it rebooted, the VM C: Drive showed the new allocated disc space and all was well
The SQL services were restarted as normal procedure and all was well.
Started the Sharepoint Services Server first and waited for it to complete then started the MOSS Server and started its needed services.
Logged onto the MOSS Server to view the central admin page and it came up, showing the SQL server as the data store.
Logged onto the VLE and 'an unexpected error has occured' error message came up and nothing else worked
Looked around the net with no joy so had to pu everthing back to as it was.
Now we have a shrinking database and an urgent need to do something about it!
We wont be able to turn the sql db off anytime soon unless it is planned/weekend/after 6pm
Any help would greatly be appreciated - or if anyone knows of anyone who maybe upto the job as a consultant (eg do this for us and tell us how you did it!)
I cant think straight at the moment, so i will re-read this thread tomorrow morning when i am more awake lol.
but, have you re-created the web application on sharepoint and on the database pointed it to your sql server and the instance? and Content Database Name?
If you have re-created the web application, then the error is quite important as it could be trying to do anything depending if you had any webparts etc on the main page before hand.. that will no longer be their as you have re-created the web application.
Have you got the full detail of the error available? If everything else is working, it may be something in the VLE configuration.
Also it may be worth trying a backup of the SharePoint site through stsadm - then restoring this to a new web application within the same setup. If this works, try restoring it to your virtualized server rather than relying on the image.
When the error page appeared was it the SharePoint unexpected error page, with a link to Troubleshoot SharePoint errors? If it was then there may be a stack trace in the server's event viewer which'd help.
If not then you should take a look at your IIS event logs (System32\LogFiles\somethingincomprehensible I believe). You can find out the path by going into IIS Manager and looking at the web site properties. This might help you narrow it down a little more.