Analysis Services - Step by Step: Errors related to feature availability and configuration

On page 56 of SQL Server 2005 Analysis Services Step by Step, I tried to DEPLOY the project, and it failed with this msg:

Errors related to feature availability and configuration: The 'Measure expressions' feature is not included in the 'Standard Edition' SKU.

Is it because of my Standard Edition? If it is, could I change the 'Measure expressions' some how to get by this msg and go on with the book?

Yes, you are running into this situation because you working against Standard edition of SQL Server Analysis Services.

You can install free trial edition from http://www.microsoft.com/sql/downloads/trial-software.mspx. It has full set of features for you to comlete any tutorial.

As for the steps described in the book, or how to work around them. You should point your questions to the authors of the book.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Thanks Edward. I'll try with the trial edition.

I was also trying to post the question to the authors, but I could not find the link to it.

|||

Hi mate

I have the same problem. Could you tell me how to fix this issue please. I'm using SQL 2005 standand version. Does it cause the problem? Please tell me as soon as possible.

thank you in adv

Wen Ou

|||I have the same problem. I am also interested in a fix, not the trial version. Could someone please let me know how to change the configuration of the cube.sql

Analysis Services - Step by Step: Errors related to feature availability and configuration

On page 56 of SQL Server 2005 Analysis Services Step by Step, I tried to DEPLOY the project, and it failed with this msg:

Errors related to feature availability and configuration: The 'Measure expressions' feature is not included in the 'Standard Edition' SKU.

Is it because of my Standard Edition? If it is, could I change the 'Measure expressions' some how to get by this msg and go on with the book?

Yes, you are running into this situation because you working against Standard edition of SQL Server Analysis Services.

You can install free trial edition from http://www.microsoft.com/sql/downloads/trial-software.mspx. It has full set of features for you to comlete any tutorial.

As for the steps described in the book, or how to work around them. You should point your questions to the authors of the book.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Thanks Edward. I'll try with the trial edition.

I was also trying to post the question to the authors, but I could not find the link to it.

|||

Hi mate

I have the same problem. Could you tell me how to fix this issue please. I'm using SQL 2005 standand version. Does it cause the problem? Please tell me as soon as possible.

thank you in adv

Wen Ou

|||I have the same problem. I am also interested in a fix, not the trial version. Could someone please let me know how to change the configuration of the cube.

Analysis Service Deployment Error

Hi,

I created a SQL Server 2005 Analysis Service project. When I tried to deploy a standard Decision Tree model, it gave me errors (see below). Clearly, I can't use ntext data type with DISTINCT, but how can I change the SQL command since it was automatically created? What was the final impact of removing the DISTINCT word from the SQL command?

SQL queries 1
SELECT DISTINCT [dbo_Training_x0020_Data].[Hellos] AS [dbo_Training_x0020_DataHellos0_0]

FROM [dbo].[Training Data] AS [dbo_Training_x0020_Data]

Error Messages 1
OLE DB error: OLE DB or ODBC error: The ntext data type cannot be selected as DISTINCT because it is not comparable.; 42000.

Please assist!

MaryYou can change the data type in the DSV, or add a calculated DSV column that casts the ntext to text

Analysis Server Database has errors. Cant delete, can't view

I tried to import a abf file in my Analysis Services using the wizard. It didn't succeed completely as I ran out of disk space. However it left my AS database in inconsistent state. I can't view anything. Can't delete anything. The entire AS is unusable at the moment. I get the following error.

"Errors in metadata manager. The dimension with ID of v_Contract, Name of Contract referenced by 'GPC GL Cube' does not exist......"

Please let me know how to restore my AS so that I can retry importing the database.

Thanks,

Ashish

I was able to remove the database. I had to stop the AS and delete the physical folders. Then restarted the AS and I was able to delete the Databases.

Hope this helps someone else because I spent some time trying to figure this out.

Ashish

An established connection was aborted by the software in your host machine.

I am getting connection errors all over the place, in everything I'm doing related to native client and connection issues failing with my database. I have changed users, authentification from windows to sql, everything. The latest was when I tried to apply the properties of my existing OLE DB Connection editor, one that has been working fine up until today. Every time I try to reselect the database and table in the properties if this, it errors out with the below:

TITLE: Microsoft SQL Native Client

Communication link failure
TCP Provider: An established connection was aborted by the software in your host machine.

BUTTONS:

&Retry
Cancel

Here are my logs:
http://www.photopizzaz.biz/junk/logs.txt
print screens of various errors I have received on my remote SQL Server 2005 (Enterprise version):
http://www.photopizzaz.biz/junk/sqlserver_2005_errors_and_resolutions.doc

Have you checked if remote connections are enabled for your server and what network protocols are available?

Please open SQL Server Surface Area Configuration tool and click 'Surface Area Configuraiton for Services and Connections' to set those settings.

An established connection was aborted by the software in your host machine.

I am getting connection errors all over the place, in everything I'm doing related to native client and connection issues failing with my database. I have changed users, authentification from windows to sql, everything. The latest was when I tried to apply the properties of my existing OLE DB Connection editor, one that has been working fine up until today. Every time I try to reselect the database and table in the properties if this, it errors out with the below:

TITLE: Microsoft SQL Native Client

Communication link failure
TCP Provider: An established connection was aborted by the software in your host machine.

BUTTONS:

&Retry
Cancel

Here are my logs:
http://www.photopizzaz.biz/junk/logs.txt
print screens of various errors I have received on my remote SQL Server 2005 (Enterprise version):
http://www.photopizzaz.biz/junk/sqlserver_2005_errors_and_resolutions.doc

Have you checked if remote connections are enabled for your server and what network protocols are available?

Please open SQL Server Surface Area Configuration tool and click 'Surface Area Configuraiton for Services and Connections' to set those settings.

An array of errors and the fix...

I am posting this in the hope that Google will spider the post and others
may not have to walk the same path that I have over the last week.
I have a new server with SATA HighPoint RAID 5, 2GB of RAM, 3.2GHz Intel P4,
915GAG motherboard. After a successful installation of Win Server 2003 and
SQL Server 2000 (and service packs) I started to bring over the SQL Server
databases off my old server. I was running some queries to check out the
speed and strange things started to happen. Query connections were being
dropped, tables were becoming corrupted and DBCC was causing SQL Server to
GPF. Some of the errors are seen below. I studied each error as it turned up
but most of the time the problem was left unresolved. I thought it was the
RAID array. I removed it but it still happened. I installed WinXP but it
still happened. I thought it was the network cables but it still happened.
This excellent article
http://support.microsoft.com/default...b;en-us;826433 pointed me to
SQLIOStress (this is a top piece of software - I did not know it even
existed - check it out) Sure enough it indicated that there was a problem
with stale reads and dirty writes; something to do with caching. My hard
drives do have 8 meg of cache. However this was ultimately a red herring.
Eventually I discovered using the help of MemTest86+
(http://www.memtest.org) that I had about 12 bits of corrupted RAM towards
the top of the 2GB memory space. I ripped out the dodgy memory and the
problem disappeared. So if you see any of the following error messages try
doing a Memtest first and save yourself a weeks worth of mucking around.
As an aside, I have now Memtested my other computers to find that one of
them has 2 bits of dodgy RAM. If this posting ever helps you then be sure
to drop me an email.
Regards
Dave A (dave @. sigmasolutions.com.au)
These are the errors that were appearing in the event log:
17310 :SqlDumpExceptionHandler: Process 3796 generated fatal exception
c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Error: 947, Severity: 16, State: 1 Error while closing database 'myDB'
cleanly
Error: 3414, Severity: 21, State: 1 Database 'myDB' (database ID 7) could
not recover. Contact Technical Support.
Error: 3314, Severity: 21, State: 3 Error while undoing logged operation in
database 'myDB'. Error at log record ID (29979:11238:226).
Error: 644, Severity: 21, State: 1 Could not find the index entry for RID
'36ad1720c37a7a19b9500300101802000' in index page (1:168081), index ID 0,
database 'myDB'.
18052 : Error: 3624, Severity: 20, State: 1.
17066 : SQL Server Assertion: File: <recbase.cpp>, line=1378 Failed
Assertion = 'm_offBeginVar < m_SizeRec'.
17066 : SQL Server Assertion: File:
<p:\sql\ntdbms\storeng\drs\include\record.inl>, line=1447 Failed Assertion
= 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
17066 : SQL Server Assertion: File: <lckmgr.cpp>, line=5201 Failed Assertion
= 'NULL == m_lockList.Head ()'.
Thanks for the info Dave. Can you tell us the brands of the server and the
memory as well?
Jacco Schalkwijk
SQL Server MVP
"Dave A" <dave@.sigmasolutionsdonotspamme.com.au> wrote in message
news:uT5O2YrCFHA.3376@.TK2MSFTNGP12.phx.gbl...
>I am posting this in the hope that Google will spider the post and others
> may not have to walk the same path that I have over the last week.
> I have a new server with SATA HighPoint RAID 5, 2GB of RAM, 3.2GHz Intel
> P4,
> 915GAG motherboard. After a successful installation of Win Server 2003 and
> SQL Server 2000 (and service packs) I started to bring over the SQL Server
> databases off my old server. I was running some queries to check out the
> speed and strange things started to happen. Query connections were being
> dropped, tables were becoming corrupted and DBCC was causing SQL Server to
> GPF. Some of the errors are seen below. I studied each error as it turned
> up
> but most of the time the problem was left unresolved. I thought it was
> the
> RAID array. I removed it but it still happened. I installed WinXP but it
> still happened. I thought it was the network cables but it still happened.
> This excellent article
> http://support.microsoft.com/default...b;en-us;826433 pointed me
> to
> SQLIOStress (this is a top piece of software - I did not know it even
> existed - check it out) Sure enough it indicated that there was a problem
> with stale reads and dirty writes; something to do with caching. My hard
> drives do have 8 meg of cache. However this was ultimately a red herring.
> Eventually I discovered using the help of MemTest86+
> (http://www.memtest.org) that I had about 12 bits of corrupted RAM towards
> the top of the 2GB memory space. I ripped out the dodgy memory and the
> problem disappeared. So if you see any of the following error messages try
> doing a Memtest first and save yourself a weeks worth of mucking around.
> As an aside, I have now Memtested my other computers to find that one of
> them has 2 bits of dodgy RAM. If this posting ever helps you then be
> sure
> to drop me an email.
> Regards
> Dave A (dave @. sigmasolutions.com.au)
> These are the errors that were appearing in the event log:
> 17310 :SqlDumpExceptionHandler: Process 3796 generated fatal exception
> c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this
> process.
> Error: 947, Severity: 16, State: 1 Error while closing database 'myDB'
> cleanly
> Error: 3414, Severity: 21, State: 1 Database 'myDB' (database ID 7) could
> not recover. Contact Technical Support.
> Error: 3314, Severity: 21, State: 3 Error while undoing logged operation
> in
> database 'myDB'. Error at log record ID (29979:11238:226).
> Error: 644, Severity: 21, State: 1 Could not find the index entry for RID
> '36ad1720c37a7a19b9500300101802000' in index page (1:168081), index ID 0,
> database 'myDB'.
> 18052 : Error: 3624, Severity: 20, State: 1.
> 17066 : SQL Server Assertion: File: <recbase.cpp>, line=1378 Failed
> Assertion = 'm_offBeginVar < m_SizeRec'.
> 17066 : SQL Server Assertion: File:
> <p:\sql\ntdbms\storeng\drs\include\record.inl>, line=1447 Failed
> Assertion
> = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
> 17066 : SQL Server Assertion: File: <lckmgr.cpp>, line=5201 Failed
> Assertion
> = 'NULL == m_lockList.Head ()'.
>
>
|||It was VData RAM but the rest was just bought in a shopping list format from
the local computer shop. I have now replaced the RAM and it is working fine.
Just a bad batch.
"Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid > wrote
in message news:u7wdU9rCFHA.3100@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Thanks for the info Dave. Can you tell us the brands of the server and the
> memory as well?
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Dave A" <dave@.sigmasolutionsdonotspamme.com.au> wrote in message
> news:uT5O2YrCFHA.3376@.TK2MSFTNGP12.phx.gbl...
and[vbcol=seagreen]
Server[vbcol=seagreen]
to[vbcol=seagreen]
turned[vbcol=seagreen]
happened.[vbcol=seagreen]
me[vbcol=seagreen]
problem[vbcol=seagreen]
herring.[vbcol=seagreen]
towards[vbcol=seagreen]
try[vbcol=seagreen]
could[vbcol=seagreen]
RID[vbcol=seagreen]
0,
>

An array of errors and the fix...

I am posting this in the hope that Google will spider the post and others
may not have to walk the same path that I have over the last week.
I have a new server with SATA HighPoint RAID 5, 2GB of RAM, 3.2GHz Intel P4,
915GAG motherboard. After a successful installation of Win Server 2003 and
SQL Server 2000 (and service packs) I started to bring over the SQL Server
databases off my old server. I was running some queries to check out the
speed and strange things started to happen. Query connections were being
dropped, tables were becoming corrupted and DBCC was causing SQL Server to
GPF. Some of the errors are seen below. I studied each error as it turned up
but most of the time the problem was left unresolved. I thought it was the
RAID array. I removed it but it still happened. I installed WinXP but it
still happened. I thought it was the network cables but it still happened.
This excellent article
http://support.microsoft.com/defaul...kb;en-us;826433 pointed me to
SQLIOStress (this is a top piece of software - I did not know it even
existed - check it out) Sure enough it indicated that there was a problem
with stale reads and dirty writes; something to do with caching. My hard
drives do have 8 meg of cache. However this was ultimately a red herring.
Eventually I discovered using the help of MemTest86+
(http://www.memtest.org) that I had about 12 bits of corrupted RAM towards
the top of the 2GB memory space. I ripped out the dodgy memory and the
problem disappeared. So if you see any of the following error messages try
doing a Memtest first and save yourself a weeks worth of mucking around.
As an aside, I have now Memtested my other computers to find that one of
them has 2 bits of dodgy RAM. If this posting ever helps you then be sure
to drop me an email.
Regards
Dave A (dave @. sigmasolutions.com.au)
These are the errors that were appearing in the event log:
17310 :SqlDumpExceptionHandler: Process 3796 generated fatal exception
c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Error: 947, Severity: 16, State: 1 Error while closing database 'myDB'
cleanly
Error: 3414, Severity: 21, State: 1 Database 'myDB' (database ID 7) could
not recover. Contact Technical Support.
Error: 3314, Severity: 21, State: 3 Error while undoing logged operation in
database 'myDB'. Error at log record ID (29979:11238:226).
Error: 644, Severity: 21, State: 1 Could not find the index entry for RID
'36ad1720c37a7a19b9500300101802000' in index page (1:168081), index ID 0,
database 'myDB'.
18052 : Error: 3624, Severity: 20, State: 1.
17066 : SQL Server Assertion: File: <recbase.cpp>, line=1378 Failed
Assertion = 'm_offBeginVar < m_SizeRec'.
17066 : SQL Server Assertion: File:
< p:\sql\ntdbms\storeng\drs\include\record
.inl>, line=1447 Failed Assertion
= 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
17066 : SQL Server Assertion: File: <lckmgr.cpp>, line=5201 Failed Assertion
= 'NULL == m_lockList.Head ()'.Thanks for the info Dave. Can you tell us the brands of the server and the
memory as well?
Jacco Schalkwijk
SQL Server MVP
"Dave A" <dave@.sigmasolutionsdonotspamme.com.au> wrote in message
news:uT5O2YrCFHA.3376@.TK2MSFTNGP12.phx.gbl...
>I am posting this in the hope that Google will spider the post and others
> may not have to walk the same path that I have over the last week.
> I have a new server with SATA HighPoint RAID 5, 2GB of RAM, 3.2GHz Intel
> P4,
> 915GAG motherboard. After a successful installation of Win Server 2003 and
> SQL Server 2000 (and service packs) I started to bring over the SQL Server
> databases off my old server. I was running some queries to check out the
> speed and strange things started to happen. Query connections were being
> dropped, tables were becoming corrupted and DBCC was causing SQL Server to
> GPF. Some of the errors are seen below. I studied each error as it turned
> up
> but most of the time the problem was left unresolved. I thought it was
> the
> RAID array. I removed it but it still happened. I installed WinXP but it
> still happened. I thought it was the network cables but it still happened.
> This excellent article
> http://support.microsoft.com/defaul...kb;en-us;826433 pointed me
> to
> SQLIOStress (this is a top piece of software - I did not know it even
> existed - check it out) Sure enough it indicated that there was a problem
> with stale reads and dirty writes; something to do with caching. My hard
> drives do have 8 meg of cache. However this was ultimately a red herring.
> Eventually I discovered using the help of MemTest86+
> (http://www.memtest.org) that I had about 12 bits of corrupted RAM towards
> the top of the 2GB memory space. I ripped out the dodgy memory and the
> problem disappeared. So if you see any of the following error messages try
> doing a Memtest first and save yourself a weeks worth of mucking around.
> As an aside, I have now Memtested my other computers to find that one of
> them has 2 bits of dodgy RAM. If this posting ever helps you then be
> sure
> to drop me an email.
> Regards
> Dave A (dave @. sigmasolutions.com.au)
> These are the errors that were appearing in the event log:
> 17310 :SqlDumpExceptionHandler: Process 3796 generated fatal exception
> c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this
> process.
> Error: 947, Severity: 16, State: 1 Error while closing database 'myDB'
> cleanly
> Error: 3414, Severity: 21, State: 1 Database 'myDB' (database ID 7) could
> not recover. Contact Technical Support.
> Error: 3314, Severity: 21, State: 3 Error while undoing logged operation
> in
> database 'myDB'. Error at log record ID (29979:11238:226).
> Error: 644, Severity: 21, State: 1 Could not find the index entry for RID
> '36ad1720c37a7a19b9500300101802000' in index page (1:168081), index ID 0,
> database 'myDB'.
> 18052 : Error: 3624, Severity: 20, State: 1.
> 17066 : SQL Server Assertion: File: <recbase.cpp>, line=1378 Failed
> Assertion = 'm_offBeginVar < m_SizeRec'.
> 17066 : SQL Server Assertion: File:
> < p:\sql\ntdbms\storeng\drs\include\record
.inl>, line=1447 Failed
> Assertion
> = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
> 17066 : SQL Server Assertion: File: <lckmgr.cpp>, line=5201 Failed
> Assertion
> = 'NULL == m_lockList.Head ()'.
>
>|||It was VData RAM but the rest was just bought in a shopping list format from
the local computer shop. I have now replaced the RAM and it is working fine.
Just a bad batch.
"Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid> wrote
in message news:u7wdU9rCFHA.3100@.TK2MSFTNGP09.phx.gbl...
> Thanks for the info Dave. Can you tell us the brands of the server and the
> memory as well?
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Dave A" <dave@.sigmasolutionsdonotspamme.com.au> wrote in message
> news:uT5O2YrCFHA.3376@.TK2MSFTNGP12.phx.gbl...
and[vbcol=seagreen]
Server[vbcol=seagreen]
to[vbcol=seagreen]
turned[vbcol=seagreen]
happened.[vbcol=seagreen]
me[vbcol=seagreen]
problem[vbcol=seagreen]
herring.[vbcol=seagreen]
towards[vbcol=seagreen]
try[vbcol=seagreen]
could[vbcol=seagreen]
RID[vbcol=seagreen]
0,[vbcol=seagreen]
>

An array of errors and the fix...

I am posting this in the hope that Google will spider the post and others
may not have to walk the same path that I have over the last week.
I have a new server with SATA HighPoint RAID 5, 2GB of RAM, 3.2GHz Intel P4,
915GAG motherboard. After a successful installation of Win Server 2003 and
SQL Server 2000 (and service packs) I started to bring over the SQL Server
databases off my old server. I was running some queries to check out the
speed and strange things started to happen. Query connections were being
dropped, tables were becoming corrupted and DBCC was causing SQL Server to
GPF. Some of the errors are seen below. I studied each error as it turned up
but most of the time the problem was left unresolved. I thought it was the
RAID array. I removed it but it still happened. I installed WinXP but it
still happened. I thought it was the network cables but it still happened.
This excellent article
http://support.microsoft.com/default.aspx?scid=kb;en-us;826433 pointed me to
SQLIOStress (this is a top piece of software - I did not know it even
existed - check it out) Sure enough it indicated that there was a problem
with stale reads and dirty writes; something to do with caching. My hard
drives do have 8 meg of cache. However this was ultimately a red herring.
Eventually I discovered using the help of MemTest86+
(http://www.memtest.org) that I had about 12 bits of corrupted RAM towards
the top of the 2GB memory space. I ripped out the dodgy memory and the
problem disappeared. So if you see any of the following error messages try
doing a Memtest first and save yourself a weeks worth of mucking around.
As an aside, I have now Memtested my other computers to find that one of
them has 2 bits of dodgy RAM. If this posting ever helps you then be sure
to drop me an email.
Regards
Dave A (dave @. sigmasolutions.com.au)
These are the errors that were appearing in the event log:
17310 :SqlDumpExceptionHandler: Process 3796 generated fatal exception
c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Error: 947, Severity: 16, State: 1 Error while closing database 'myDB'
cleanly
Error: 3414, Severity: 21, State: 1 Database 'myDB' (database ID 7) could
not recover. Contact Technical Support.
Error: 3314, Severity: 21, State: 3 Error while undoing logged operation in
database 'myDB'. Error at log record ID (29979:11238:226).
Error: 644, Severity: 21, State: 1 Could not find the index entry for RID
'36ad1720c37a7a19b9500300101802000' in index page (1:168081), index ID 0,
database 'myDB'.
18052 : Error: 3624, Severity: 20, State: 1.
17066 : SQL Server Assertion: File: <recbase.cpp>, line=1378 Failed
Assertion = 'm_offBeginVar < m_SizeRec'.
17066 : SQL Server Assertion: File:
<p:\sql\ntdbms\storeng\drs\include\record.inl>, line=1447 Failed Assertion
= 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
17066 : SQL Server Assertion: File: <lckmgr.cpp>, line=5201 Failed Assertion
= 'NULL == m_lockList.Head ()'.Thanks for the info Dave. Can you tell us the brands of the server and the
memory as well?
--
Jacco Schalkwijk
SQL Server MVP
"Dave A" <dave@.sigmasolutionsdonotspamme.com.au> wrote in message
news:uT5O2YrCFHA.3376@.TK2MSFTNGP12.phx.gbl...
>I am posting this in the hope that Google will spider the post and others
> may not have to walk the same path that I have over the last week.
> I have a new server with SATA HighPoint RAID 5, 2GB of RAM, 3.2GHz Intel
> P4,
> 915GAG motherboard. After a successful installation of Win Server 2003 and
> SQL Server 2000 (and service packs) I started to bring over the SQL Server
> databases off my old server. I was running some queries to check out the
> speed and strange things started to happen. Query connections were being
> dropped, tables were becoming corrupted and DBCC was causing SQL Server to
> GPF. Some of the errors are seen below. I studied each error as it turned
> up
> but most of the time the problem was left unresolved. I thought it was
> the
> RAID array. I removed it but it still happened. I installed WinXP but it
> still happened. I thought it was the network cables but it still happened.
> This excellent article
> http://support.microsoft.com/default.aspx?scid=kb;en-us;826433 pointed me
> to
> SQLIOStress (this is a top piece of software - I did not know it even
> existed - check it out) Sure enough it indicated that there was a problem
> with stale reads and dirty writes; something to do with caching. My hard
> drives do have 8 meg of cache. However this was ultimately a red herring.
> Eventually I discovered using the help of MemTest86+
> (http://www.memtest.org) that I had about 12 bits of corrupted RAM towards
> the top of the 2GB memory space. I ripped out the dodgy memory and the
> problem disappeared. So if you see any of the following error messages try
> doing a Memtest first and save yourself a weeks worth of mucking around.
> As an aside, I have now Memtested my other computers to find that one of
> them has 2 bits of dodgy RAM. If this posting ever helps you then be
> sure
> to drop me an email.
> Regards
> Dave A (dave @. sigmasolutions.com.au)
> These are the errors that were appearing in the event log:
> 17310 :SqlDumpExceptionHandler: Process 3796 generated fatal exception
> c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this
> process.
> Error: 947, Severity: 16, State: 1 Error while closing database 'myDB'
> cleanly
> Error: 3414, Severity: 21, State: 1 Database 'myDB' (database ID 7) could
> not recover. Contact Technical Support.
> Error: 3314, Severity: 21, State: 3 Error while undoing logged operation
> in
> database 'myDB'. Error at log record ID (29979:11238:226).
> Error: 644, Severity: 21, State: 1 Could not find the index entry for RID
> '36ad1720c37a7a19b9500300101802000' in index page (1:168081), index ID 0,
> database 'myDB'.
> 18052 : Error: 3624, Severity: 20, State: 1.
> 17066 : SQL Server Assertion: File: <recbase.cpp>, line=1378 Failed
> Assertion = 'm_offBeginVar < m_SizeRec'.
> 17066 : SQL Server Assertion: File:
> <p:\sql\ntdbms\storeng\drs\include\record.inl>, line=1447 Failed
> Assertion
> = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
> 17066 : SQL Server Assertion: File: <lckmgr.cpp>, line=5201 Failed
> Assertion
> = 'NULL == m_lockList.Head ()'.
>
>|||It was VData RAM but the rest was just bought in a shopping list format from
the local computer shop. I have now replaced the RAM and it is working fine.
Just a bad batch.
"Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid> wrote
in message news:u7wdU9rCFHA.3100@.TK2MSFTNGP09.phx.gbl...
> Thanks for the info Dave. Can you tell us the brands of the server and the
> memory as well?
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Dave A" <dave@.sigmasolutionsdonotspamme.com.au> wrote in message
> news:uT5O2YrCFHA.3376@.TK2MSFTNGP12.phx.gbl...
> >I am posting this in the hope that Google will spider the post and others
> > may not have to walk the same path that I have over the last week.
> >
> > I have a new server with SATA HighPoint RAID 5, 2GB of RAM, 3.2GHz Intel
> > P4,
> > 915GAG motherboard. After a successful installation of Win Server 2003
and
> > SQL Server 2000 (and service packs) I started to bring over the SQL
Server
> > databases off my old server. I was running some queries to check out the
> > speed and strange things started to happen. Query connections were being
> > dropped, tables were becoming corrupted and DBCC was causing SQL Server
to
> > GPF. Some of the errors are seen below. I studied each error as it
turned
> > up
> > but most of the time the problem was left unresolved. I thought it was
> > the
> > RAID array. I removed it but it still happened. I installed WinXP but it
> > still happened. I thought it was the network cables but it still
happened.
> > This excellent article
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;826433 pointed
me
> > to
> > SQLIOStress (this is a top piece of software - I did not know it even
> > existed - check it out) Sure enough it indicated that there was a
problem
> > with stale reads and dirty writes; something to do with caching. My hard
> > drives do have 8 meg of cache. However this was ultimately a red
herring.
> >
> > Eventually I discovered using the help of MemTest86+
> > (http://www.memtest.org) that I had about 12 bits of corrupted RAM
towards
> > the top of the 2GB memory space. I ripped out the dodgy memory and the
> > problem disappeared. So if you see any of the following error messages
try
> > doing a Memtest first and save yourself a weeks worth of mucking around.
> >
> > As an aside, I have now Memtested my other computers to find that one of
> > them has 2 bits of dodgy RAM. If this posting ever helps you then be
> > sure
> > to drop me an email.
> >
> > Regards
> > Dave A (dave @. sigmasolutions.com.au)
> >
> > These are the errors that were appearing in the event log:
> >
> > 17310 :SqlDumpExceptionHandler: Process 3796 generated fatal exception
> > c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this
> > process.
> >
> > Error: 947, Severity: 16, State: 1 Error while closing database 'myDB'
> > cleanly
> >
> > Error: 3414, Severity: 21, State: 1 Database 'myDB' (database ID 7)
could
> > not recover. Contact Technical Support.
> >
> > Error: 3314, Severity: 21, State: 3 Error while undoing logged operation
> > in
> > database 'myDB'. Error at log record ID (29979:11238:226).
> >
> > Error: 644, Severity: 21, State: 1 Could not find the index entry for
RID
> > '36ad1720c37a7a19b9500300101802000' in index page (1:168081), index ID
0,
> > database 'myDB'.
> >
> > 18052 : Error: 3624, Severity: 20, State: 1.
> >
> > 17066 : SQL Server Assertion: File: <recbase.cpp>, line=1378 Failed
> > Assertion = 'm_offBeginVar < m_SizeRec'.
> >
> > 17066 : SQL Server Assertion: File:
> > <p:\sql\ntdbms\storeng\drs\include\record.inl>, line=1447 Failed
> > Assertion
> > = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
> >
> > 17066 : SQL Server Assertion: File: <lckmgr.cpp>, line=5201 Failed
> > Assertion
> > = 'NULL == m_lockList.Head ()'.
> >
> >
> >
> >
>