MSSQL 2000 SSL Snapshot problem

Currently I am running 2 MSSQL SQL 2000 Enterprise servers running on Win2k3
utilizing SSL via "force protocol encryption". The systems are running fine
with the exception of Snapshots and/or DTS packages that write to the local
disk. When trying to get a snapshot to run for the local machine I recieve
the following error:
General network error. Check your network documentation.
(Source: SERVER (Data source); Error number: 11)
If I turn off "force protocol encryption" the snapshot works just fine.
I suspect the replication binaries do not support SSL. You should contact MS
(PSS) for further clarification on how to configure this.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"PSchultz" <PSchultz@.discussions.microsoft.com> wrote in message
news:A6ECD0B1-87BD-4D41-9A80-48E26BAA155A@.microsoft.com...
> Currently I am running 2 MSSQL SQL 2000 Enterprise servers running on
> Win2k3
> utilizing SSL via "force protocol encryption". The systems are running
> fine
> with the exception of Snapshots and/or DTS packages that write to the
> local
> disk. When trying to get a snapshot to run for the local machine I
> recieve
> the following error:
> General network error. Check your network documentation.
> (Source: SERVER (Data source); Error number: 11)
> If I turn off "force protocol encryption" the snapshot works just fine.
>
|||Some tables will successfully produce a snapshot, however, it is quite hit or
miss so I believe that the binaries do support SSL. I've also looked into it
being a possible issue with a timeout, however, that isn't the root cause as
the error occurs within seconds of the snapshot starting
"Hilary Cotter" wrote:

> I suspect the replication binaries do not support SSL. You should contact MS
> (PSS) for further clarification on how to configure this.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "PSchultz" <PSchultz@.discussions.microsoft.com> wrote in message
> news:A6ECD0B1-87BD-4D41-9A80-48E26BAA155A@.microsoft.com...
>
>
sql

MSSQL 2000 SP4 Memory Leak

Greetings all!

On one of our intranet SQL servers running under Windows 2000 SP 3,
MSsql 2000 SP4 seems to gradually "eat" away all available memory (with no obvious reason for it) until a certain limit is reached, forcing the server to slow down substantially since the OS has to SWAP continuously.

I would appreciate any suggestions at this point on how to tackle this problem :)

Thank you!
VincentJSThat is the nature of SQL Server. By default, it will continue to claim available memory that is not being used by applications. It's not a memory leak. Most of this memory is used for data cache, which greatly improves performance. You want SQL Server to have plenty of memory. But you can limit this amout if you view the server properties in enterprise manager.

Bill|||if you can afford it, you should have your web and database servers on different machines. I believe you can limit the amount memory sql server consums with the max server memory option in sp_configure but I have never used it

mssql 2000 server migration

do anyone know how to migrate a mssql 2000 server (running windows 2003) to
another server which is running windows 2003 also, what are the procedures
to do so?
ok thanks
Generally you would install SQL in the same location on server 2 as you did in server 1. ShutDown SQL on both servers and copy of the data directory that contains your mdf and ldf files to the same location on Server2.
This is a very generic answer of course. If you need to change locations and such then it would be more complex.
Make sure that you have the service packs installed also.
Jeff
MCDBA, MCSE+I
sql

mssql 2000 server migration

do anyone know how to migrate a mssql 2000 server (running windows 2003) to
another server which is running windows 2003 also, what are the procedures
to do so?
ok thanksGenerally you would install SQL in the same location on server 2 as you did
in server 1. ShutDown SQL on both servers and copy of the data directory th
at contains your mdf and ldf files to the same location on Server2.
This is a very generic answer of course. If you need to change locations an
d such then it would be more complex.
Make sure that you have the service packs installed also.
Jeff
MCDBA, MCSE+I

MSSQL 2000 on top of MSDE 2000?

Hi,
How does one install MSSQL 2000 on a machine that's already running MSDE 2000? Do i need to unintstall MSDE, or both can be installed seperately??
Is there a way to simply upgrade MSDE into MSSQL 2000?
Thanks!Its easy to upgrade from MSDE to SQL Server, review information from books online from the topic 'How to perform an edition upgrade within SQL Server 2000'sql

MSSQL 2000 memory leaks

Hi,
I have one application in two different companies with MSSQL2000 running on Windows2000 Server and Windows2003 Server.
It seems that memory needed for MSSQL2000 as displayed in task manager is increased every day.
Does anybody knows anything regarding memory leaks in MSSQL2000?

How can I find what version of service pack have I installed in a MSSQL2000 server machine?

Regards,
ManolisSQL Server is designed to take up as much memory as it needs. See the article titled "Server Memory Options" in BOL.|||SQL 2000 is sensistive to "Memory Pressure" where other applications request memory from the host operating system. As other apps request more memory, SQL 2000 will free up some of the memory that it is using. In general though, SQL 2000 will tend to "camp" on memory until it percieves pressure from other applications, so it has a reputation as a "memory hog" that I don't feel is justified.

To find your present patch level, execute:SELECT ServerProperty('ProductLevel')-PatP|||Link http://www.sqljunkies.com/Article/7F8518F9-FDAA-4FF3-8FC5-25E8946C8D0C.scuk to investigate & resolve the performance issues.

MSSQL 2000 DB Migration to Microsoft SQL 2005

Hi,
We're building new machine Windows 2003 with MSSQL 2005 server.
We have current machine running Windows 2000 with MSSQL 2000.
How do we migrate the MSSQL2000 database to MSSQL 2005 server?
A) My way: inplace upgrade (i know this one will 99% work!)[vbcol=seagreen]
w/MSSQL2000[vbcol=seagreen]
B) Another way: backup the MSSQL DB from Windows2000 and restore to
Windows2005 with MSSQL2005? work?
C) Detach and attach the database from MSSQL2000 and attach to MSSQL2005 ?
work?
Any other way which will guarantee work best?
Thanks for any input!!
J.H
"J.H" <jpthsd@.hotmail.com> wrote in message
news:%239XXAO1aHHA.4616@.TK2MSFTNGP03.phx.gbl...
> Hi,
> We're building new machine Windows 2003 with MSSQL 2005 server.
> We have current machine running Windows 2000 with MSSQL 2000.
> How do we migrate the MSSQL2000 database to MSSQL 2005 server?
> A) My way: inplace upgrade (i know this one will 99% work!)
> w/MSSQL2000
> B) Another way: backup the MSSQL DB from Windows2000 and restore to
> Windows2005 with MSSQL2005? work?
This will work.
I would do this.
That way if something "goes wrong" you still have your original 2000 DB and
a backup.
However, no matter WHAT choice you make, make sure to to test your
application thoroughly.
There shouldn't be any gotchas, but you never know.

> C) Detach and attach the database from MSSQL2000 and attach to MSSQL2005 ?
> work?
>
> Any other way which will guarantee work best?
> Thanks for any input!!
> J.H
>
Greg Moore
SQL Server DBA Consulting
Email: sql (at) greenms.com http://www.greenms.com
|||I did attach/dettach for all my database. Now working wothout any problems.
Don't forget to change compatibility level to 9 after attaching database.
Ramunas
"J.H" <jpthsd@.hotmail.com> wrote in message
news:%239XXAO1aHHA.4616@.TK2MSFTNGP03.phx.gbl...
> Hi,
> We're building new machine Windows 2003 with MSSQL 2005 server.
> We have current machine running Windows 2000 with MSSQL 2000.
> How do we migrate the MSSQL2000 database to MSSQL 2005 server?
> A) My way: inplace upgrade (i know this one will 99% work!)
> w/MSSQL2000
> B) Another way: backup the MSSQL DB from Windows2000 and restore to
> Windows2005 with MSSQL2005? work?
> C) Detach and attach the database from MSSQL2000 and attach to MSSQL2005 ?
> work?
>
> Any other way which will guarantee work best?
> Thanks for any input!!
> J.H
>
sql

MSSQL 2000 DB Migration to Microsoft SQL 2005

Hi,
We're building new machine Windows 2003 with MSSQL 2005 server.
We have current machine running Windows 2000 with MSSQL 2000.
How do we migrate the MSSQL2000 database to MSSQL 2005 server?
A) My way: inplace upgrade (i know this one will 99% work!)
>> installing new Windows 2003R2 with MSSQL2000 w/SP4
>> restore the MSSQL2000 database file to the new machine Windows2003R2
w/MSSQL2000
>> doing inplace upgrade on Windows2003R2 w/MSSQL2000 /wSP4 >> MSSQL2005
B) Another way: backup the MSSQL DB from Windows2000 and restore to
Windows2005 with MSSQL2005? work?
C) Detach and attach the database from MSSQL2000 and attach to MSSQL2005 ?
work?
Any other way which will guarantee work best?
Thanks for any input!!
J.H"J.H" <jpthsd@.hotmail.com> wrote in message
news:%239XXAO1aHHA.4616@.TK2MSFTNGP03.phx.gbl...
> Hi,
> We're building new machine Windows 2003 with MSSQL 2005 server.
> We have current machine running Windows 2000 with MSSQL 2000.
> How do we migrate the MSSQL2000 database to MSSQL 2005 server?
> A) My way: inplace upgrade (i know this one will 99% work!)
>> installing new Windows 2003R2 with MSSQL2000 w/SP4
>> restore the MSSQL2000 database file to the new machine Windows2003R2
> w/MSSQL2000
>> doing inplace upgrade on Windows2003R2 w/MSSQL2000 /wSP4 >> MSSQL2005
> B) Another way: backup the MSSQL DB from Windows2000 and restore to
> Windows2005 with MSSQL2005? work?
This will work.
I would do this.
That way if something "goes wrong" you still have your original 2000 DB and
a backup.
However, no matter WHAT choice you make, make sure to to test your
application thoroughly.
There shouldn't be any gotchas, but you never know.
> C) Detach and attach the database from MSSQL2000 and attach to MSSQL2005 ?
> work?
>
> Any other way which will guarantee work best?
> Thanks for any input!!
> J.H
>
Greg Moore
SQL Server DBA Consulting
Email: sql (at) greenms.com http://www.greenms.com|||I did attach/dettach for all my database. Now working wothout any problems.
Don't forget to change compatibility level to 9 after attaching database.
Ramunas
"J.H" <jpthsd@.hotmail.com> wrote in message
news:%239XXAO1aHHA.4616@.TK2MSFTNGP03.phx.gbl...
> Hi,
> We're building new machine Windows 2003 with MSSQL 2005 server.
> We have current machine running Windows 2000 with MSSQL 2000.
> How do we migrate the MSSQL2000 database to MSSQL 2005 server?
> A) My way: inplace upgrade (i know this one will 99% work!)
> >> installing new Windows 2003R2 with MSSQL2000 w/SP4
> >> restore the MSSQL2000 database file to the new machine Windows2003R2
> w/MSSQL2000
> >> doing inplace upgrade on Windows2003R2 w/MSSQL2000 /wSP4 >> MSSQL2005
> B) Another way: backup the MSSQL DB from Windows2000 and restore to
> Windows2005 with MSSQL2005? work?
> C) Detach and attach the database from MSSQL2000 and attach to MSSQL2005 ?
> work?
>
> Any other way which will guarantee work best?
> Thanks for any input!!
> J.H
>

MSSQL 2000 DB Migration to Microsoft SQL 2005

Hi,
We're building new machine Windows 2003 with MSSQL 2005 server.
We have current machine running Windows 2000 with MSSQL 2000.
How do we migrate the MSSQL2000 database to MSSQL 2005 server?
A) My way: inplace upgrade (i know this one will 99% work!)[vbcol=seagreen]
w/MSSQL2000[vbcol=seagreen]
B) Another way: backup the MSSQL DB from Windows2000 and restore to
Windows2005 with MSSQL2005? work?
C) Detach and attach the database from MSSQL2000 and attach to MSSQL2005 ?
work?
Any other way which will guarantee work best?
Thanks for any input!!
J.H"J.H" <jpthsd@.hotmail.com> wrote in message
news:%239XXAO1aHHA.4616@.TK2MSFTNGP03.phx.gbl...
> Hi,
> We're building new machine Windows 2003 with MSSQL 2005 server.
> We have current machine running Windows 2000 with MSSQL 2000.
> How do we migrate the MSSQL2000 database to MSSQL 2005 server?
> A) My way: inplace upgrade (i know this one will 99% work!)
> w/MSSQL2000
> B) Another way: backup the MSSQL DB from Windows2000 and restore to
> Windows2005 with MSSQL2005? work?
This will work.
I would do this.
That way if something "goes wrong" you still have your original 2000 DB and
a backup.
However, no matter WHAT choice you make, make sure to to test your
application thoroughly.
There shouldn't be any gotchas, but you never know.

> C) Detach and attach the database from MSSQL2000 and attach to MSSQL2005 ?
> work?
>
> Any other way which will guarantee work best?
> Thanks for any input!!
> J.H
>
Greg Moore
SQL Server DBA Consulting
Email: sql (at) greenms.com http://www.greenms.com|||I did attach/dettach for all my database. Now working wothout any problems.
Don't forget to change compatibility level to 9 after attaching database.
Ramunas
"J.H" <jpthsd@.hotmail.com> wrote in message
news:%239XXAO1aHHA.4616@.TK2MSFTNGP03.phx.gbl...
> Hi,
> We're building new machine Windows 2003 with MSSQL 2005 server.
> We have current machine running Windows 2000 with MSSQL 2000.
> How do we migrate the MSSQL2000 database to MSSQL 2005 server?
> A) My way: inplace upgrade (i know this one will 99% work!)
> w/MSSQL2000
> B) Another way: backup the MSSQL DB from Windows2000 and restore to
> Windows2005 with MSSQL2005? work?
> C) Detach and attach the database from MSSQL2000 and attach to MSSQL2005 ?
> work?
>
> Any other way which will guarantee work best?
> Thanks for any input!!
> J.H
>

MSSQL & MySQL on the same server?

Hi all,
I was wondering what the PROS & CONS are of running both MSSQL 2000 &
MySQL on the same box? I would think resource contention, such as memory,
would be something to be careful of. But, I'd like to get a broader input
from others out there. Plus I know nothing about MySQL.
Thanks So Much,
Joe DYes they will co-exist peacefully. A more interesting question is why do you
want both.
"Joe D" <jkdriscoll@.qg.com> wrote in message
news:e4vaj6$1adv$1@.sxnews1.qg.com...
> Hi all,
> I was wondering what the PROS & CONS are of running both MSSQL 2000 &
> mysql on the same box? I would think resource contention, such as memory,
> would be something to be careful of. But, I'd like to get a broader input
> from others out there. Plus I know nothing about MySQL.
> Thanks So Much,
> Joe D
>|||Good Question - Same question that I asked. Things like this can happen when
one group in the company does what it wants (in this case go and buys some
3rd party software package) but wants another group (i.e. the IT group) to
make it work on existing servers. If you've been around the business
awhile, you know what I'm talking about.
Thanks for your feedback.
"Steve Dassin" <steve@.nospamrac4sql.net> wrote in message
news:Ohmb2hrfGHA.4464@.TK2MSFTNGP04.phx.gbl...
> Yes they will co-exist peacefully. A more interesting question is why do
> you
> want both.
> "Joe D" <jkdriscoll@.qg.com> wrote in message
> news:e4vaj6$1adv$1@.sxnews1.qg.com...
>

MSSQL & MySQL on the same server?

Hi all,
I was wondering what the PROS & CONS are of running both MSSQL 2000 &
MySQL on the same box? I would think resource contention, such as memory,
would be something to be careful of. But, I'd like to get a broader input
from others out there. Plus I know nothing about MySQL.
Thanks So Much,
Joe DYes they will co-exist peacefully. A more interesting question is why do you
want both.
"Joe D" <jkdriscoll@.qg.com> wrote in message
news:e4vaj6$1adv$1@.sxnews1.qg.com...
> Hi all,
> I was wondering what the PROS & CONS are of running both MSSQL 2000 &
> MySQL on the same box? I would think resource contention, such as memory,
> would be something to be careful of. But, I'd like to get a broader input
> from others out there. Plus I know nothing about MySQL.
> Thanks So Much,
> Joe D
>|||Good Question - Same question that I asked. Things like this can happen when
one group in the company does what it wants (in this case go and buys some
3rd party software package) but wants another group (i.e. the IT group) to
make it work on existing servers. If you've been around the business
awhile, you know what I'm talking about.
Thanks for your feedback.
"Steve Dassin" <steve@.nospamrac4sql.net> wrote in message
news:Ohmb2hrfGHA.4464@.TK2MSFTNGP04.phx.gbl...
> Yes they will co-exist peacefully. A more interesting question is why do
> you
> want both.
> "Joe D" <jkdriscoll@.qg.com> wrote in message
> news:e4vaj6$1adv$1@.sxnews1.qg.com...
>> Hi all,
>> I was wondering what the PROS & CONS are of running both MSSQL 2000 &
>> MySQL on the same box? I would think resource contention, such as memory,
>> would be something to be careful of. But, I'd like to get a broader input
>> from others out there. Plus I know nothing about MySQL.
>> Thanks So Much,
>> Joe D
>

mssearch.exe easting up memory

Hi ,
Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it up
for three days, the mssearch.exe job just continues to eat up more memory
until the machine runs out of it needing for the mssearch.exe job to be
ended. Then the mssearch.exe runs again and the cycle continues.
I observered that everytime our .net app touches the sql server database,
that is when this mssearch.exe job stays and start to eat up memory. A
google search reveals that open cursors to the database or a web user
creates a link and does nothing causes this mssearch.exe to go up and grow
and grow.
Is there a fix for this or a workaround?
Thanks,
RdR
You should contact Microsoft Product Support and have them take a look at
MSSearch.
Adrian
"RdR" <rrosario@.datamirror.com> wrote in message
news:GWRde.4408$5u4.15748@.nnrp1.uunet.ca...
> Hi ,
> Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it
> up for three days, the mssearch.exe job just continues to eat up more
> memory until the machine runs out of it needing for the mssearch.exe job
> to be ended. Then the mssearch.exe runs again and the cycle continues.
> I observered that everytime our .net app touches the sql server database,
> that is when this mssearch.exe job stays and start to eat up memory. A
> google search reveals that open cursors to the database or a web user
> creates a link and does nothing causes this mssearch.exe to go up and grow
> and grow.
> Is there a fix for this or a workaround?
> Thanks,
> RdR
>

mssearch.exe easting up memory

Hi ,
Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it up
for three days, the mssearch.exe job just continues to eat up more memory
until the machine runs out of it needing for the mssearch.exe job to be
ended. Then the mssearch.exe runs again and the cycle continues.
I observered that everytime our .net app touches the sql server database,
that is when this mssearch.exe job stays and start to eat up memory. A
google search reveals that open cursors to the database or a web user
creates a link and does nothing causes this mssearch.exe to go up and grow
and grow.
Is there a fix for this or a workaround?
Thanks,
RdRYou should contact Microsoft Product Support and have them take a look at
MSSearch.
Adrian
"RdR" <rrosario@.datamirror.com> wrote in message
news:GWRde.4408$5u4.15748@.nnrp1.uunet.ca...
> Hi ,
> Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it
> up for three days, the mssearch.exe job just continues to eat up more
> memory until the machine runs out of it needing for the mssearch.exe job
> to be ended. Then the mssearch.exe runs again and the cycle continues.
> I observered that everytime our .net app touches the sql server database,
> that is when this mssearch.exe job stays and start to eat up memory. A
> google search reveals that open cursors to the database or a web user
> creates a link and does nothing causes this mssearch.exe to go up and grow
> and grow.
> Is there a fix for this or a workaround?
> Thanks,
> RdR
>

mssearch.exe easting up memory

Hi ,
Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it up
for three days, the mssearch.exe job just continues to eat up more memory
until the machine runs out of it needing for the mssearch.exe job to be
ended. Then the mssearch.exe runs again and the cycle continues.
I observered that everytime our .net app touches the sql server database,
that is when this mssearch.exe job stays and start to eat up memory. A
google search reveals that open cursors to the database or a web user
creates a link and does nothing causes this mssearch.exe to go up and grow
and grow.
Is there a fix for this or a workaround?
Thanks,
RdRYou should contact Microsoft Product Support and have them take a look at
MSSearch.
Adrian
"RdR" <rrosario@.datamirror.com> wrote in message
news:GWRde.4408$5u4.15748@.nnrp1.uunet.ca...
> Hi ,
> Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it
> up for three days, the mssearch.exe job just continues to eat up more
> memory until the machine runs out of it needing for the mssearch.exe job
> to be ended. Then the mssearch.exe runs again and the cycle continues.
> I observered that everytime our .net app touches the sql server database,
> that is when this mssearch.exe job stays and start to eat up memory. A
> google search reveals that open cursors to the database or a web user
> creates a link and does nothing causes this mssearch.exe to go up and grow
> and grow.
> Is there a fix for this or a workaround?
> Thanks,
> RdR
>sql

Mssearch.exe consuming High CPU over extended time period

Hello,
We are running SQL 2000 sp4 with full text search, recently we are
getting 100% CPU over extended period of time and the only way to
resolve this is by killing the Mssearch.exe process. (we tried to
restart the service but it hang) the Microsoft search service is
running under local system account.
our system topology is active/passive cluster with NAS disks, 4GB RAM
and 4 CPU for each server.
May be some one can help me?
The issue happen randomly with no specific job running at that time or
any thing, and when it happen the SQL queries are running very very
slow.
Thank you

No solution to your particular problem, except looking at a prioir post:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=93706&SiteID=1

In your particular case, when did the problem start? After upgrade, some configuration change, resource change, database size change?

This may help understand the problem.

Thanks,
Boris.|||I asked our dev team and there are no known problems of this kind. I would recommend contacting product support services and have them look at your particular configuration. Most likely the problem you are seeing is caused by the content being indexed.|||Hi,
We appear to be experiencing the same thing. There is no disk activity - just mssearch running at 100% utilization.
Have you found an answer yet?|||We used Microsoft support and nothing found we tried rebuild all catalogs , Fix some snapshot problem on the NAS and still we got the same problem finally we changed the affinity mask of the Mssearch and the SQL (SQL use CPU 1 and 2 and Mssearch the rest) we are still waiting to see if it help to solve the problem for now (4 days) it look fine even though the Mssearch took 100% the SQL continue to give services and the CPU drop back to normal with out human interference. So I will have more clear answer with in a week.

Mssearch.exe consuming High CPU over extended time period

Hello,
We are running SQL 2000 sp4 with full text search, recently we are
getting 100% CPU over extended period of time and the only way to
resolve this is by killing the Mssearch.exe process. (we tried to
restart the service but it hang) the Microsoft search service is
running under local system account.
our system topology is active/passive cluster with NAS disks, 4GB RAM
and 4 CPU for each server.
May be some one can help me?
The issue happen randomly with no specific job running at that time or
any thing, and when it happen the SQL queries are running very very
slow.
Thank you

No solution to your particular problem, except looking at a prioir post:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=93706&SiteID=1

In your particular case, when did the problem start? After upgrade, some configuration change, resource change, database size change?

This may help understand the problem.

Thanks,
Boris.|||I asked our dev team and there are no known problems of this kind. I would recommend contacting product support services and have them look at your particular configuration. Most likely the problem you are seeing is caused by the content being indexed.|||Hi,
We appear to be experiencing the same thing. There is no disk activity - just mssearch running at 100% utilization.
Have you found an answer yet?
|||We used Microsoft support and nothing found we tried rebuild all catalogs , Fix some snapshot problem on the NAS and still we got the same problem finally we changed the affinity mask of the Mssearch and the SQL (SQL use CPU 1 and 2 and Mssearch the rest) we are still waiting to see if it help to solve the problem for now (4 days) it look fine even though the Mssearch took 100% the SQL continue to give services and the CPU drop back to normal with out human interference. So I will have more clear answer with in a week.

MSSearch Gatherer Error: c0000005 on SQL2K SP3

Please, help me to troubleshoot MSSearch Gatherer error.
I am running SQL2k SP3 on Windows 2k DC and trying to setup full-text index using Enterprise Manager Console, everything goes fine until I am trying to start full population.

In the eventlog I got the following errors:

Event Source: Microsoft Search
Event Category: Gatherer
Event ID: 3035
Description:
One or more warnings or errors for Gatherer project <SQLServer SQL0000900005> were logged to file <d:\sqldata\FTData\SQLServer\GatherLogs\SQL00009000 05.1.gthr>. If you are interested in these messages, please, look at the file using the gatherer log query object (gthrlog.vbs, log viewer web page).

Event Source: Microsoft Search
Event Category: Gatherer
Event ID: 3036
Description:
The crawl seed <MSSQL75://SQLServer/78bedcc2> in project <SQLServer SQL0000900005> cannot be accessed. Error: c0000005 - A description for this error could not be found.

After that process I got ItemCount -2
using SELECT fulltextcatalogproperty('TestCatalog', 'ItemCount')

Services (SQL and MSSearch) running under LocalSystem Account and have correct BUILTIN\Administrators with all privileges.

Any idea?did u recently change the account on which mssqlserver runs?
check the following thread:

http://support.microsoft.com/default.aspx?scid=KB;EN-US;277549
http://www.dbforums.com/archives/t141995.html|||I tried to change and re-change SQL Server account using EM Console, also I reinstall sp3, but i got the same error message. Nothing helped. I checked
Gatherer Log and got the same errors.

10.03.2004 14:52:06 Add The gatherer has started
10.03.2004 14:52:06 Add The initialization has completed
10.03.2004 14:52:16 Add Started Full crawl
10.03.2004 14:52:16 Add Started Full crawl
10.03.2004 14:52:20 MSSQL75://SQLServer/267aba7a Add Error fetching URL, (c0000005 - A description for this error could not be found)
10.03.2004 14:52:20 MSSQL75://SQLServer/25869641 Add Error fetching URL, (c0000005 - A description for this error could not be found)
10.03.2004 14:52:20 Add Completed Full crawl
10.03.2004 14:52:20 Add Completed Full crawl

c0000005 - seem to be access_violation ?sql

MSOLAP Error. Please help!

I have an Openrowset query, which connects to a cube and obtains the data in a table. This is run every day. This process has been running for over a year but now all of a sudden doesn't work and gives the erros mentioned below. When I reduce the records to be returned to about 1/4, then it runs fine else not. We are using Enterprise Version. Any help will be really appreciated.

Error when tried once -

OLE DB provider 'MSOLAP' reported an error. The provider ran out of memory.
[OLE/DB provider returned message: An error occurred during attempt to get a cell value.]
[OLE/DB provider returned message: The operation has failed because of an error in the COM component - unknown error ]
OLE DB error trace [OLE/DB Provider 'MSOLAP' IRowset::GetNextRows returned 0x8007000e: The provider ran out of memory.].

The second time I received -

ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 77 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
[OLE/DB provider returned message: An unexpected internal error has occurred.] [Microsoft][ODBC SQL Server Driver]Function sequence error

Thanks,
SauravRevisiting archived thread here: http://www.dbforums.com/archive/index.php/t-534601.html

msmdpump.dll IIS hard crash

We have OLAP set up with a HTTP pump and throughout the day IIS has a hard crash 10-15 times. We can't get much out of the error log and running iisstate reveals:

(1414.127c): Unknown exception - code 800706ba (first chance)

We're running it as a priviledged user on the domain, and are impersonating a locale and set of roles on the connection string.

Not sure if this crash related to msmdpump.dll or to IIS.

You should contact Customer support for this problem and see if there is similar issue has been reported already.

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

|||We are also facing similar problem. What fix was applied?|||

Please make sure you install SP1 of SQL Server and copy SP1 version of msmdpump.dll into your vitual folder.

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

sql

msmdpump.dll IIS hard crash

We have OLAP set up with a HTTP pump and throughout the day IIS has a hard crash 10-15 times. We can't get much out of the error log and running iisstate reveals:

(1414.127c): Unknown exception - code 800706ba (first chance)

We're running it as a priviledged user on the domain, and are impersonating a locale and set of roles on the connection string.

Not sure if this crash related to msmdpump.dll or to IIS.

You should contact Customer support for this problem and see if there is similar issue has been reported already.

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

|||We are also facing similar problem. What fix was applied?|||

Please make sure you install SP1 of SQL Server and copy SP1 version of msmdpump.dll into your vitual folder.

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