Hello

I was asked to upgrade an MCMS 2001 database to MCMS 2002 SP2.

Having restored the database and assigned the right credentials in SQL
Server 2005, I ran the DCA to configure and upgrade the database in the MCMS
environment. Having run approx. 15% during the migration, the DCA throws an
error:

"Error 3903 - The rollback transaction request has no corresponding begin
transaction".

I've upgraded a fairly large number of MCMS2001 databases and made sure the
following checklist had been met (according to the FAQs posted on the
MCMSFAQ site):

1. the CMSSystem user is not present the database
2. the database was trimmed and the logfile allowed to expand (and increased
to a default of 10 GB)
3. the correct compatibility mode set on the database

The setup is running on a single Windows 2003 server with SQL Server 2005
SP1 and MCMS 2002 SP2 (4GB ram etc.).

Reading the few posts on the internet (using google), it seems that several
other developers have faced the same issues I'm describing (although some
report that fixing the transaction logs made everything work). Could this be
caused by database inconsistencies? If so, how do I correct them?

I've tried a lot of different approaches - please share any ideas.

Thanks in advance!

--
With regards
Anders Borum / SphereWorks
Microsoft Certified Professional (.NET MCP)

[ Post a follow-up to this message ]

Hi Anders,

you might want to open a support case for this.

Cheers,
Stefan


"Anders Borum" <anders@sphereworks.dk> wrote in message
news:%23gI6ygHVHHA.4756@TK2MSFTNGP06.phx.gbl...
> Hello
>
> I was asked to upgrade an MCMS 2001 database to MCMS 2002 SP2.
>
> Having restored the database and assigned the right credentials in SQL
> Server 2005, I ran the DCA to configure and upgrade the database in the
> MCMS environment. Having run approx. 15% during the migration, the DCA
> throws an error:
>
> "Error 3903 - The rollback transaction request has no corresponding begin
> transaction".
>
> I've upgraded a fairly large number of MCMS2001 databases and made sure
> the following checklist had been met (according to the FAQs posted on the
> MCMSFAQ site):
>
> 1. the CMSSystem user is not present the database
> 2. the database was trimmed and the logfile allowed to expand (and
> increased to a default of 10 GB)
> 3. the correct compatibility mode set on the database
>
> The setup is running on a single Windows 2003 server with SQL Server 2005
> SP1 and MCMS 2002 SP2 (4GB ram etc.).
>
> Reading the few posts on the internet (using google), it seems that
> several other developers have faced the same issues I'm describing
> (although some report that fixing the transaction logs made everything
> work). Could this be caused by database inconsistencies? If so, how do I
> correct them?
>
> I've tried a lot of different approaches - please share any ideas.
>
> Thanks in advance!
>
> --
> With regards
> Anders Borum / SphereWorks
> Microsoft Certified Professional (.NET MCP)
>

[ Post a follow-up to this message ]

Hi Stefan

> you might want to open a support case for this.

There's really no way I could fix this problem without opening a supportcase
(which is very expensive)?

--
With regards
Anders Borum / SphereWorks
Microsoft Certified Professional (.NET MCP)

[ Post a follow-up to this message ]

Hi again
 
> There's really no way I could fix this problem without opening a
> supportcase (which is very expensive)?

Just wanted to inform you, that a friend of mine tried to run over the same
procedures on a SQL Server 2000 setup and encountered the same issues.

--
With regards
Anders Borum / SphereWorks
Microsoft Certified Professional (.NET MCP)

[ Post a follow-up to this message ]

Hi Anders,

I checked our knowledge base and old service requests: such an error message
has never been reported before.
So I cannot provide you with answer.
This requires a more detailed analysis.

Cheers,
Stefan


"Anders Borum" <anders@sphereworks.dk> wrote in message
news:OmP7bHNVHHA.3568@TK2MSFTNGP06.phx.gbl...
> Hi again
> 
>
> Just wanted to inform you, that a friend of mine tried to run over the
> same procedures on a SQL Server 2000 setup and encountered the same
> issues.
>
> --
> With regards
> Anders Borum / SphereWorks
> Microsoft Certified Professional (.NET MCP)
>

[ Post a follow-up to this message ]

On 20 Feb, 10:23, "Stefan Go=DFner [MSFT]"
<stef...@online.microsoft.com> wrote:
> Hi Anders,
>
> I checked our knowledge base and old service requests: such an error mess=
age
> has never been reported before.
> So I cannot provide you with answer.
> This requires a more detailed analysis.
>
> Cheers,
> Stefan
>
> "Anders Borum" <and...@sphereworks.dk> wrote in message
>
> news:OmP7bHNVHHA.3568@TK2MSFTNGP06.phx.gbl...
>
>
> 
> 
> 
> 
>
> - Show quoted text -

Hi - I don't know if it's related, but I once had this error, on a non
CMS SQL Server Database and looking on the SQL server in the SQL
Server Enterprise Manager under the "Space Allocated" tab I had no
free "data space" remaining.  Which was the cause of my problem at the
time...... something to check perhaps.

Kevin

[ Post a follow-up to this message ]