Desperate - WSS2.0 upgrade to WSS 3.0 trashed DB no either won
in [Windows Services]
|
From: Garth Kirkwood on 24 Sep 2007 18:20 Daniel, Thanks for the reply, but unfortunately neither of these have worked. When using V2 with a new configDB when I try and attach my ContentDB I get the error message: "Cannot drop type 'dbo.tSystemID' because it is currently in use. (Error code: 3732)" and it doesn't attach. I have also tried to attach it to a new V3 install and it states that I need to upgrade the database, but as I have stated earlier, I can't upgrade using the stsadm -o upgrade command as my ContentDB is in SQL 2005 server and when you use the default install of V3 it uses MS##SSEE and I don't know how to copy the DB from SQL 2005 to MS##SSEE. Thanks. "Daniel Bugday" wrote: > Hi Garth, > first.. i have seen the same issue before and just to make you a little > happier.. there is a solution to your problem :) > > If i understand you correctly then you try to revert your upgrade and you > need to come back to original? > > If you need to stay in V2 then try this.. > > First of all.. backup all your databases :) > > Check to make sure nothing is sticked in the ConfigDB.. > (Sometimes i have noticed that the ConfigDB gets corrupted because of a > failed upgrade..) > > 1. Create a new web site in IIS > 2. Extend the new site to SharePoint > 3. Configure the new IIS site to map to the existing ContentDB > > (I have once been forced to create a new ConfigDB but it was a litte > complex.. get back if you need to know how i did it) > > If you want to use V3 and attach the DB then use the command: > Addcontentdb: Stsadm operation (Windows SharePoint Services) > http://technet2.microsoft.com/windowsserver/WSS/en/library/f9f9a3eb-ce46-4dbb-a15c-9fad9eb32ec71033.mspx?mfr=true > > /Daniel Bugday > > > "Garth Kirkwood" <GarthKirkwood(a)discussions.microsoft.com> wrote in message > news:4A62BF6B-1E27-40A4-B151-EA564BB69CAC(a)microsoft.com... > >I tried to do an inplace upgrade from 2.0 to 3.0 after compeleting a > > succesful prescan, but it didn't work. I tried in vain to get it to work, > > but > > could not get pasted step 2 of 10. I would though I could just unintall > > and > > go back to version 2, no luck. > > > > I can get each version working with new databases, but when I try and use > > my > > old config and content DBs they won't connect. > > In version 2 when I try and connect the Content DB I get this error > > message: > > Cannot drop type 'dbo.tSystemID' because it is currently in use. (Error > > code: 3732). > > > > When I try and connect it in Version 3, it says it needs to be upgraded. I > > can't run the upgrade on the DB as the it is in my SQL server and V3 is > > using > > MS##SSEE. > > > > I am able to go either way, version 2 or version 3, I just need it to > > work. > > I am running Windows Server 2003, with MS SQL 2005 (9.00.3045). > > > > Please my head is on the chopping block and this problem is making me > > physically sick with worry as I am concerned I won't be able to get it > > working again. Thanks to anyone that can help. >
From: Daniel Bugday on 26 Sep 2007 13:54 You could install SQL 2005 Studio Management Express and attach the database from your SQL environment. /Daniel Bugday "Garth Kirkwood" <GarthKirkwood(a)discussions.microsoft.com> wrote in message news:9C164320-1F4A-4ECD-9215-D7CE6403A1FE(a)microsoft.com... > Daniel, > > Thanks for the reply, but unfortunately neither of these have worked. > When > using V2 with a new configDB when I try and attach my ContentDB I get the > error message: "Cannot drop type 'dbo.tSystemID' because it is currently > in > use. (Error code: 3732)" and it doesn't attach. > > I have also tried to attach it to a new V3 install and it states that I > need > to upgrade the database, but as I have stated earlier, I can't upgrade > using > the stsadm -o upgrade command as my ContentDB is in SQL 2005 server and > when > you use the default install of V3 it uses MS##SSEE and I don't know how to > copy the DB from SQL 2005 to MS##SSEE. > > Thanks. > > "Daniel Bugday" wrote: > >> Hi Garth, >> first.. i have seen the same issue before and just to make you a little >> happier.. there is a solution to your problem :) >> >> If i understand you correctly then you try to revert your upgrade and you >> need to come back to original? >> >> If you need to stay in V2 then try this.. >> >> First of all.. backup all your databases :) >> >> Check to make sure nothing is sticked in the ConfigDB.. >> (Sometimes i have noticed that the ConfigDB gets corrupted because of a >> failed upgrade..) >> >> 1. Create a new web site in IIS >> 2. Extend the new site to SharePoint >> 3. Configure the new IIS site to map to the existing ContentDB >> >> (I have once been forced to create a new ConfigDB but it was a litte >> complex.. get back if you need to know how i did it) >> >> If you want to use V3 and attach the DB then use the command: >> Addcontentdb: Stsadm operation (Windows SharePoint Services) >> http://technet2.microsoft.com/windowsserver/WSS/en/library/f9f9a3eb-ce46-4dbb-a15c-9fad9eb32ec71033.mspx?mfr=true >> >> /Daniel Bugday >> >> >> "Garth Kirkwood" <GarthKirkwood(a)discussions.microsoft.com> wrote in >> message >> news:4A62BF6B-1E27-40A4-B151-EA564BB69CAC(a)microsoft.com... >> >I tried to do an inplace upgrade from 2.0 to 3.0 after compeleting a >> > succesful prescan, but it didn't work. I tried in vain to get it to >> > work, >> > but >> > could not get pasted step 2 of 10. I would though I could just unintall >> > and >> > go back to version 2, no luck. >> > >> > I can get each version working with new databases, but when I try and >> > use >> > my >> > old config and content DBs they won't connect. >> > In version 2 when I try and connect the Content DB I get this error >> > message: >> > Cannot drop type 'dbo.tSystemID' because it is currently in use. (Error >> > code: 3732). >> > >> > When I try and connect it in Version 3, it says it needs to be >> > upgraded. I >> > can't run the upgrade on the DB as the it is in my SQL server and V3 is >> > using >> > MS##SSEE. >> > >> > I am able to go either way, version 2 or version 3, I just need it to >> > work. >> > I am running Windows Server 2003, with MS SQL 2005 (9.00.3045). >> > >> > Please my head is on the chopping block and this problem is making me >> > physically sick with worry as I am concerned I won't be able to get it >> > working again. Thanks to anyone that can help. >>
From: Garth Kirkwood on 26 Sep 2007 19:32 Unfortunately I had to revert to emplying MS support services and whilst I had created the DB that was eventually able to connect to v2, there was a slight problem installing v3. Anyway in the end the site is now running in version 3, now if only I can remember how I fixed my DB I would be more happier. Thanks Daniel and everyone that read my post. Garth "Daniel Bugday" wrote: > You could install SQL 2005 Studio Management Express and attach the database > from your SQL environment. > > /Daniel Bugday > > "Garth Kirkwood" <GarthKirkwood(a)discussions.microsoft.com> wrote in message > news:9C164320-1F4A-4ECD-9215-D7CE6403A1FE(a)microsoft.com... > > Daniel, > > > > Thanks for the reply, but unfortunately neither of these have worked. > > When > > using V2 with a new configDB when I try and attach my ContentDB I get the > > error message: "Cannot drop type 'dbo.tSystemID' because it is currently > > in > > use. (Error code: 3732)" and it doesn't attach. > > > > I have also tried to attach it to a new V3 install and it states that I > > need > > to upgrade the database, but as I have stated earlier, I can't upgrade > > using > > the stsadm -o upgrade command as my ContentDB is in SQL 2005 server and > > when > > you use the default install of V3 it uses MS##SSEE and I don't know how to > > copy the DB from SQL 2005 to MS##SSEE. > > > > Thanks. > > > > "Daniel Bugday" wrote: > > > >> Hi Garth, > >> first.. i have seen the same issue before and just to make you a little > >> happier.. there is a solution to your problem :) > >> > >> If i understand you correctly then you try to revert your upgrade and you > >> need to come back to original? > >> > >> If you need to stay in V2 then try this.. > >> > >> First of all.. backup all your databases :) > >> > >> Check to make sure nothing is sticked in the ConfigDB.. > >> (Sometimes i have noticed that the ConfigDB gets corrupted because of a > >> failed upgrade..) > >> > >> 1. Create a new web site in IIS > >> 2. Extend the new site to SharePoint > >> 3. Configure the new IIS site to map to the existing ContentDB > >> > >> (I have once been forced to create a new ConfigDB but it was a litte > >> complex.. get back if you need to know how i did it) > >> > >> If you want to use V3 and attach the DB then use the command: > >> Addcontentdb: Stsadm operation (Windows SharePoint Services) > >> http://technet2.microsoft.com/windowsserver/WSS/en/library/f9f9a3eb-ce46-4dbb-a15c-9fad9eb32ec71033.mspx?mfr=true > >> > >> /Daniel Bugday > >> > >> > >> "Garth Kirkwood" <GarthKirkwood(a)discussions.microsoft.com> wrote in > >> message > >> news:4A62BF6B-1E27-40A4-B151-EA564BB69CAC(a)microsoft.com... > >> >I tried to do an inplace upgrade from 2.0 to 3.0 after compeleting a > >> > succesful prescan, but it didn't work. I tried in vain to get it to > >> > work, > >> > but > >> > could not get pasted step 2 of 10. I would though I could just unintall > >> > and > >> > go back to version 2, no luck. > >> > > >> > I can get each version working with new databases, but when I try and > >> > use > >> > my > >> > old config and content DBs they won't connect. > >> > In version 2 when I try and connect the Content DB I get this error > >> > message: > >> > Cannot drop type 'dbo.tSystemID' because it is currently in use. (Error > >> > code: 3732). > >> > > >> > When I try and connect it in Version 3, it says it needs to be > >> > upgraded. I > >> > can't run the upgrade on the DB as the it is in my SQL server and V3 is > >> > using > >> > MS##SSEE. > >> > > >> > I am able to go either way, version 2 or version 3, I just need it to > >> > work. > >> > I am running Windows Server 2003, with MS SQL 2005 (9.00.3045). > >> > > >> > Please my head is on the chopping block and this problem is making me > >> > physically sick with worry as I am concerned I won't be able to get it > >> > working again. Thanks to anyone that can help. > >> >
|
Pages: 1 Prev: Ever growing OWSTIMER.EXE Next: WSS3.0 and IRM protectors |