I have a database that has not been purged in a while. Now, I can get the
error below when I attempted to purge the revisions. Please help.

Error:                            4005

Description:                   The XML parser could not parse the tag it was
given.

Severity:                                    5

Source:
 P:\NR\Shared\GrammarParserC\AEGrammarPar
ser.cpp 313

Debug info:                    Extended error: [What='Offending SQL: 

23;? =
call PurgeRevisionsByDate(?)};

{call UpdateChangeTable };Timeout expired. '] [LCID='1024'] [So
urceFile='']
[SourceFileLine='-1'] [DebugInfo='

Extra info:

Client Source:
 AETree::evhAETree_OnEvent:Menu\ToolsPurg
eRevisions

Recommended Action:   The ODBC data source may be incorrectly configured,
the database may not be running, or there may be incorrect data in the datab

[ Post a follow-up to this message ]

Hi,

there is a hotfix available to improve the performance of the revision
history deletion.
You should open a support call and request this fix:
http://support.microsoft.com/default.aspx?id=834324

Cheers,
Stefan

"mkaki" <mkaki@discussions.microsoft.com> wrote in message
news:C0ABF6E6-4A8D-4F2B-8BC9-526DE4FAFE10@microsoft.com...
>I have a database that has not been purged in a while. Now, I can get the
> error below when I attempted to purge the revisions. Please help.
>
> Error:                            4005
>
> Description:                   The XML parser could not parse the tag it
> was
> given.
>
> Severity:                                    5
>
> Source:
>  P:\NR\Shared\GrammarParserC\AEGrammarPar
ser.cpp 313
>
> Debug info:                    Extended error: [What='Offending SQL: &
#123;? =
> call PurgeRevisionsByDate(?)};
>
> {call UpdateChangeTable };Timeout expired. '] [LCID='1024']
> [SourceFile='']
> [SourceFileLine='-1'] [DebugInfo='
>
> Extra info:
>
> Client Source:
>  AETree::evhAETree_OnEvent:Menu\ToolsPurg
eRevisions
>
> Recommended Action:   The ODBC data source may be incorrectly configured,
> the database may not be running, or there may be incorrect data in the
> datab
>

[ Post a follow-up to this message ]

Thanks!

"Stefan Goßner [MSFT]" wrote:

> Hi,
>
> there is a hotfix available to improve the performance of the revision
> history deletion.
> You should open a support call and request this fix:
> http://support.microsoft.com/default.aspx?id=834324
>
> Cheers,
> Stefan
>
> "mkaki" <mkaki@discussions.microsoft.com> wrote in message
> news:C0ABF6E6-4A8D-4F2B-8BC9-526DE4FAFE10@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

I did apply the hotfix. But same problem same error. MS told me that CMS 200
1
is no longer supported, can't help me any further.

"Stefan Goßner [MSFT]" wrote:

> Hi,
>
> there is a hotfix available to improve the performance of the revision
> history deletion.
> You should open a support call and request this fix:
> http://support.microsoft.com/default.aspx?id=834324
>
> Cheers,
> Stefan
>
> "mkaki" <mkaki@discussions.microsoft.com> wrote in message
> news:C0ABF6E6-4A8D-4F2B-8BC9-526DE4FAFE10@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Hi,

the information you received is not correct.

CMS 2001 will be supported till 10.01.2012.
But CMS 2001 is in the extended support cycle which means that only Premier
customers can request new hotfixes.

Cheers,
Stefan


"mkaki" <mkaki@discussions.microsoft.com> wrote in message
news:9559B313-A097-4D9C-8E9A-20AE10C4D14E@microsoft.com...[vbcol=seagreen]
>I did apply the hotfix. But same problem same error. MS told me that CMS
>2001
> is no longer supported, can't help me any further.
>
> "Stefan Goßner [MSFT]" wrote:
> 

[ Post a follow-up to this message ]