Prev: WSS3.0 and IRM protectors
Next: Search Errors after new installation of WSS 3.0
From: "Greg Tompkins" send email to g r e g without spaces at g r e g t o m p k i n s D O T c o on 8 Oct 2007 12:50
Hi David,

Well I just thought I would give it a try since the other method had me
running in circles. At this point I'm going to uninstall 3.0 reinstall 2.0
and try the database migration again.


"David Lozzi" <dlozzi(remote-this)@delphi-ts.com> wrote in message
news:71ED127A-091A-4312-A481-10C1C5ABE27B(a)microsoft.com...
> Hi Greg,
>
> The first upgrade I did I also did an in-place and nothing good came from
> it. I since uninstalled WSS3 and WSS2 and reinstalled WSS2 and installed
> WSS3
> with do not upgrade option. Then use the prescan.exe tool on the WSS2
> site,
> which gets the SQL db ready, then copied the db to a new name and added
> the
> content db using the stsadm tool. This scenario works great every time.
>
> Let me know if you want more info.
> Thanks,
>
>
> "Greg Tompkins" wrote:
>
>> Hi David,
>>
>> Well I ran the inplace upgrade and it didn't report any errors. But now
>> when
>> I try to open up the site I get an error message that says: "
>>
>> An error occurred during the processing of
>> /sca/OJDTC_Meet/default.aspx. The server tag is not well formed.
>>
>> "
>>
>> I have no idea what this means or how to proceed.
>>
>> Thanks,
>>
>> --GREG--
>>
>>
>> "David Lozzi" <dlozzi(remote-this)@delphi-ts.com> wrote in message
>> news:114AE5E1-41AB-4898-AC65-C505B3B1A01D(a)microsoft.com...
>> > Hi Greg,
>> >
>> > I've had similar frustrations. I setup a test server with my WSS2 app,
>> > about
>> > 2.5GB in size, and dealt with the very annoying migration process.
>> > Ultimately, I got it down to a few easy steps, with the longest being
>> > the
>> > time it took for the database to attach. I have since upgraded 3 other
>> > sites
>> > for customers and have a few more in the line up.
>> >
>> > Keep me posted, I'll see if I can help.
>> > Thanks,
>> > David
>> >
>> > "Greg Tompkins" wrote:
>> >
>> >> I don't know. I am starting all over again from scratch. I'm
>> >> installing
>> >> the
>> >> Windows 2003 server, the SQL Server, restoring from backup to WSS 2.0,
>> >> then
>> >> try to attach to my 3.0 server again. I am starting to think
>> >> Sharepoint
>> >> is a
>> >> complete kludge.
>> >>
>> >>
>> >> "David Lozzi" <dlozzi(remote-this)@delphi-ts.com> wrote in message
>> >> news:99C7C03A-72FC-46B2-A0E7-A3E5F20F3E4D(a)microsoft.com...
>> >> > What were the errors?
>> >> >
>> >> > "Greg Tompkins" wrote:
>> >> >
>> >> >> Hi All,
>> >> >>
>> >> >> I think I am getting somewhere.....
>> >> >>
>> >> >> I ran this command to attach my 2.0 contentDB to WSS 3.0:
>> >> >>
>> >> >> STSADM -o addcontentdb -url http://MYSERVER -databaseserver
>> >> >> MYDATABASESERVER -databasename MYDATABASENAME
>> >> >>
>> >> >> It took almost 15 minutes but completed successfully. I checked the
>> >> >> upgrade.log file and it only registered three errors, which isn't
>> >> >> bad
>> >> >> considering the size of my database.
>> >> >>
>> >> >> HOWEVER.....
>> >> >>
>> >> >> When I go to Central Administration > Application Management >
>> >> >> Content
>> >> >> Databases I am not seeing my database attached. If I try to
>> >> >> attach
>> >> >> it
>> >> >> here, I get an error saying to use the STSADM command!
>> >> >>
>> >> >> So I am running in a circle.
>> >> >>
>> >> >> Any help would be greatly appreciated.
>> >> >>
>> >> >> Thanks,
>> >> >>
>> >> >> --GREG--
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>


First  |  Prev  | 
Pages: 1 2
Prev: WSS3.0 and IRM protectors
Next: Search Errors after new installation of WSS 3.0