Search Results

It looks like you have an access denied issue. Either your disconnected from the network or AD DS, or the account your using has expired credentials. Try to find the failing job in job history, and ch …

You may have deleted (but not removed) SPSites in your content DB, which shows in SSMS, but not in Central Administration. To check if you do, run: >Get-SPDeletedSite If there are deleted sites, yo …

There is a rough way to see which database is in use running the query sp_who which outputs (among other things) loginame, hostname and dbname. You will find the connections to all databases in this s …

It's very hard to know what actually happened during the process of renaming the SQL Server. Still, I will try to make a few suggestions of the steps that should have happened, but (from your post) di …

Yes, It's compatible. Just make sure you use MOSS SharePoint Service Pack 3, and you should be just fine. Also there's no difference to SharePoint concern whether you use SP2 or SP3 on the SQL Server …

I would install a new SQL Server to the level that you require, such as SQL Server 2008 R2. Tehn I would backup from source SQL and restore to destination SQL, with the same permissions and settings a …

TL;DR With an SQL Alias, you create a pointer to the new SQL Server. That's why your Central Admin Page still thinks it's using MyOldDBServer. The alias lives in the Operation System and is not part o …

From a SharePoint Server you can simply run $db = (Get-SPDatabase)[0] $db.Server From SQL Server it's a bit tricker, but you can get the applications using this SQL Server by running the followin …

There are a couple of things to check from your very informative images: Are you logged in as sp_admin while running the script? Can you open and view Central Administration? Do the sp_admin account …