Database migration problem

  • Database migration problem Renzo

    We have recently migrated our MOSS databases from MS SQL Express 2005 to MS SQL 2008 both intances running on the same Windows 2003 server.

    After "successful" migration we switched the 2005 server off and test that everything still working as expected which it did! (or at least we thought it did).

    All its apparently working fine exept that after few minutes we started receiving an error on the aevent viewer saying that couldn't find SERVER\SQL2005\MOSS_ConfigDatabase so we swtiched back on and start to research about what could the problem be?

    After few hours of research we found out that it seems that all the timer-jobs are executed from the old database on MS SQL 2005. So we went in to the config database and we realize that the table TimerRunningJobs on the 2008 config database was empty where the same table on config database on 2005 contains all the active timer-jobs with recent dates.

    Did any one seen this before? and if so how should it be fixed?. maybe is there a way that I could write some code to recreate the timer-jobs on the new database?

    Thanks in advance :)

  • How did you move the configuration database?

    You need to use psconfig.exe -cmd configdb -disconnect and psconfig.exe -cmd configdb -connect to move (and optionally rename) the config db.

  • The basic problem with our database was that for some reason psconfig didn't renamed the object for the old server instance in stead it created a new one and keeping the old too. We tried manually rename the object on the database but that didn't work because the key field is the SQL instance.

    SO after doing some research we solved our problem by creating an alias on the new SQL server with the name of the old SQL server.

    please see here fro more info about this.

    I hope it helps someone

2007 timer-jobs development sql-server administration
Related questions and answers
  • , we were lucky enough to still have the soon to be decommisioned server that previously ran Central Admin (Server1). So, I added the server to the farm. Removed the Central Admin from the new Server...We have a server farm that is having issues deploying WSPs. The odd thing is that the server goes through all the motions of deploying the WSPs with no errors. That is, the job is scheduled... that existed prior to the upgrade. This is also the case in a retract,delete,add,deploy scenario. Note: Our server topology has changed over time. Our Central Admin machine reached its End of Life, so we

  • attempting to start and run the UPS Sync) and eventually fails: Error ID: 22 - The Forefront Identity Manager Service cannot connect to the SQL Database Server. The SQL Server could not be contacted. The connection failure may be due to a network failure, firewall configuration error, or other connection issue. Additionally, the SQL Server connection information could be configured... 2010 SQL (Default Instance) SQL Server 2008 R2 64 Bit All the necessary steps in Spence's guide (domain accounts, permissions, rights, etc.) have been followed. The two FIM services on the APP

  • -SPConfigurationDatabase so I am able to use a non-domain username (SPF_CONFIG that I created in the previous step) But all I get is this: Unknown error The outcome after this error is: Database Sharepoint2010Config is created User SPF_CONFIG is added to SQL Server and attached to this newly created database as dbowner (check below image) alt text http...I'm having problems installing development machine for SharePoint (Foundation) 2010. This is what I did so far on the same machine: Installed a clean Windows 7 x64 with 4GB of RAM without being

  • into this and decided to completely re-install MOSS on that box. I have tried to re-run the config wizard to hook this server up to the existing config database and to re-create the central admin site. However I now... that I can join it at server XXXXXXXX\lob database XXX_SharePoint_Config in farm mode 05/05/2010 09:43:45 8 INF Now joining to farm at server XXXXXXXX\lob database XXX_SharePoint_Config... as the central admin db access account has access to the config database (I have admin access so can check this) but I cannot ascertain if it has access to the existing admin content database

  • hub. So I tried creating a new MMS with the old database, and entering the new URL to the content type hub, forcing the hub and subscriber jobs, all to no avail. Apart from trashing my source Content... machine from scratch and attached site collection databases and one MMS database to SQL. Then, for every content database restored I created a new web application, entering the name of that content database. No dramas there. I could browse the sites and all content looked to be intact. I then went into the connections property of the Manage Metadata services and changed the database name from

  • and SharePoint (as it is impossible to only uninstall the Reporting Services component with SQL Server 2005) used the same service account for all SQL services and the same for all SharePoint services given all service accounts domain administrator and local administrator permissions enabled Named Pipes and TCP/IP networking within SQL Server followed Troubleshooting Server and Database Connection Problems...On a single Windows 2008 Server I'm running SharePoint 2007 Enterprise (SP2, December 2009 CU) and SQL Server 2005 (SP3, CU 7). Authentication is NTLM. I've been trying to get SharePoint Reporting

  • without any particular rights: SPF_DATABASE for database credentials SPF_ADMIN for farm credentials Added domain administrator in SQL Server 2008 R2 with sysadmin rights started Sharepoint Powershell as domain administrator (so I have rights to access domain accounts) I didn't install SQL Server 2008 KB 970315 x64, because I'm running R2 version - as I understand this is SQL Server 2008 SP2... Then it runs for a few seconds and fails with this message: New-SPConfigurationDatabase : Cannot connect to database master at SQL server a t developer.mydomain.pri. The database might not exist

  • the Central Admin app pool account can write to the config database But then we lose the whole point - I want my site collection administrators to be able to manage the schedule! The only alternative solution...I have run into a problem several times now where I have developed a custom timer job, and I want my site collection administrators to manage the schedule of this job with a custom application page but I keep running into security related obstacles. Since timerjobs are child objects of SPWebApplication, they are stored in the config database. If you have set up your farm properly in such a way

  • could be possibly omitted if I will tweak the script, but I made this solution in one night learning from examples and building script) After that it loads all the information from spreadsheet... and this two sub sites have different set of user. So to summarize my question. I want to get as result of SQL query table with username (NT\login) with information about... this spreadsheet. I know that email address and NT\login is pretty the same information so email could be omitted to avoid redundancy of information. And rest of information like region, site name, sub-site

Data information