Showing posts with label process. Show all posts
Showing posts with label process. Show all posts

Thursday, March 22, 2012

Error 80070006

Hello everyone,
I have a large table (around 15m rows) I'm trying to Full-Text index using
the Japanese wordbreaker.
When I do a full process, after processing 3-4 million rows, I see a couple
of "Error Fetching URL (80070006 - Invalid handle)" records in the Gather
Log, followed by many many c0000005 records in the log.
At that point, the MSSearch service is still running, but if I try to shut
it down using the sql server service manager or the windows tasks control
panel, it hangs while stopping. I have to kill it using the task manager
process panel.
I tried applying SP4 and recreating the catalog, but I have the same problem.
Any suggestions?
Regards,
Jonathan
does this apply -
http://support.microsoft.com/default...b;en-us;298794
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
"Jonathan Levine" <myfoo2@.nospam.nospam> wrote in message
news:23546C67-AAE7-43AB-B435-C255BB43CF0B@.microsoft.com...
> Hello everyone,
> I have a large table (around 15m rows) I'm trying to Full-Text index using
> the Japanese wordbreaker.
> When I do a full process, after processing 3-4 million rows, I see a
couple
> of "Error Fetching URL (80070006 - Invalid handle)" records in the Gather
> Log, followed by many many c0000005 records in the log.
> At that point, the MSSearch service is still running, but if I try to shut
> it down using the sql server service manager or the windows tasks control
> panel, it hangs while stopping. I have to kill it using the task manager
> process panel.
> I tried applying SP4 and recreating the catalog, but I have the same
problem.
> Any suggestions?
> Regards,
> Jonathan
|||Hilary,
Thanks very much for your reply.
"Hilary Cotter" wrote:
> does this apply -
> http://support.microsoft.com/default...b;en-us;298794
I don't think so. I have increased MaxPropStoreCacheSize gradually to 0x0460.
Regards,
Jonathan
|||This is possibly a buffer overrun. How are you storing your data? Is it in
char, varchar, text or image? If Image what is your document format?
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
"Jonathan Levine" <myfoo2@.nospam.nospam> wrote in message
news:23546C67-AAE7-43AB-B435-C255BB43CF0B@.microsoft.com...
> Hello everyone,
> I have a large table (around 15m rows) I'm trying to Full-Text index using
> the Japanese wordbreaker.
> When I do a full process, after processing 3-4 million rows, I see a
couple
> of "Error Fetching URL (80070006 - Invalid handle)" records in the Gather
> Log, followed by many many c0000005 records in the log.
> At that point, the MSSearch service is still running, but if I try to shut
> it down using the sql server service manager or the windows tasks control
> panel, it hangs while stopping. I have to kill it using the task manager
> process panel.
> I tried applying SP4 and recreating the catalog, but I have the same
problem.
> Any suggestions?
> Regards,
> Jonathan
|||Hi again Hilary,
"Hilary Cotter" wrote:
> This is possibly a buffer overrun. How are you storing your data? Is it in
> char, varchar, text or image? If Image what is your document format?
>
Buffer overrun sounds likely to me.
The data is in two columns: one big nvarchar, and an ntext.
It is Japanese text from web pages (the web pages have been stripped of HTML
tags).
Regards,
Jonathan
|||just out of curiosity, do you get the problem when you index the content
with the neutral word breaker?
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
"Jonathan Levine" <myfoo2@.nospam.nospam> wrote in message
news:21043DBE-5885-41FC-A68B-462A7A6DEA47@.microsoft.com...
> Hi again Hilary,
>
> "Hilary Cotter" wrote:
> Buffer overrun sounds likely to me.
> The data is in two columns: one big nvarchar, and an ntext.
> It is Japanese text from web pages (the web pages have been stripped of
> HTML
> tags).
> Regards,
> Jonathan
>
|||Hilary,
"Hilary Cotter" wrote:
> just out of curiosity, do you get the problem when you index the content
> with the neutral word breaker?
>
I haven't tried the neutral word breaker. The neutral word breaker doesn't
handle Japanese text very well: most Japanese is written without whitespace
between the words, so I don't think the neutral word breaker index would be
very useful even if it worked.
Jonathan
|||I realize you are loosing the language capabilities you need - however if it
works using the neutral word breaker the problem is with the Japanese word
breaker and you can raise this as a bug with MS. If it fails with the
neutral word breaker something is wrong with your environment which might be
solved with a reapplication of the service pack, or by removing and
reinstalling SQL FTS.
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
"Jonathan Levine" <myfoo2@.nospam.nospam> wrote in message
news:51A6B6D7-D439-4351-B619-D8645494DDF5@.microsoft.com...
> Hilary,
> "Hilary Cotter" wrote:
> I haven't tried the neutral word breaker. The neutral word breaker
doesn't
> handle Japanese text very well: most Japanese is written without
whitespace
> between the words, so I don't think the neutral word breaker index would
be
> very useful even if it worked.
> Jonathan
|||"Hilary Cotter" wrote:
> I realize you are loosing the language capabilities you need - however if it
> works using the neutral word breaker the problem is with the Japanese word
> breaker and you can raise this as a bug with MS. If it fails with the
> neutral word breaker something is wrong with your environment which might be
> solved with a reapplication of the service pack, or by removing and
> reinstalling SQL FTS.
Hilary,
Your instincts were right on. The problem was in the Windows 2003
wordbreaker -- upgrading to SP1 fixed the problem. (see KB article 885899)
Thanks for your help!
Jonathan
http://kerblog.com/earlyedition/arch...05/27/460.aspx

Monday, March 19, 2012

Error 705 while restoring transaction logs

While in the process of restoring a large number of
transaction logs, I recieved the following error
"There not enough room for process 11 to store PROC_HDR
0x5975000 in Pss.
What doesn't it have room for? The system databases have
plenty of room.
The error occurred on the 14th of about 30 transaction
logs being loaded. I am using SQL 6.5, I am unsure of the
service pack level, it migt be 5a (the build number is
6.50.479).
Any help would be greatly appreciatedDaniel,
PSS here stands for "process status structure" and refers to something SQL
Server keeps in memory. In effect, the message is saying SQL Server ran out
of memory in some buffer area. Were you able to finish the restores?
Ron
--
Ron Talmage
SQL Server MVP
"Daniel Inman" <dwinman.ns@.iqe.com> wrote in message
news:00f401c356cb$73274890$a601280a@.phx.gbl...
> While in the process of restoring a large number of
> transaction logs, I recieved the following error
> "There not enough room for process 11 to store PROC_HDR
> 0x5975000 in Pss.
> What doesn't it have room for? The system databases have
> plenty of room.
> The error occurred on the 14th of about 30 transaction
> logs being loaded. I am using SQL 6.5, I am unsure of the
> service pack level, it migt be 5a (the build number is
> 6.50.479).
> Any help would be greatly appreciated
>|||Thank you for your response, but unfortunately, we
couldn't continue restoring logs. The database was
marked suspect as a result of the error, and in 6.5 it
seems that you can't restore a corrupt database without
dropping it first. My client was getting nervous over
the downtime so we gave upon restoring the transaction
logs and went back to the last full backup. I don't know
what would have happened if I had tried the entire
restore process again - just restoring the full backup
took over five hours - the DB is over 5gb.
I am just concerned that I may encounter the same error
the next time I have to restore transaction logs for this
client. For future reference, do you think this was
related to some attribute of the transaction log it faile
on, such as size or contents? Does it matter that I ran
the load database in the same batch as the load
transaction?
Daniel Inman
>--Original Message--
>Daniel,
>PSS here stands for "process status structure" and
refers to something SQL
>Server keeps in memory. In effect, the message is saying
SQL Server ran out
>of memory in some buffer area. Were you able to finish
the restores?
>Ron
>--
>Ron Talmage
>SQL Server MVP
>
>"Daniel Inman" <dwinman.ns@.iqe.com> wrote in message
>news:00f401c356cb$73274890$a601280a@.phx.gbl...
>> While in the process of restoring a large number of
>> transaction logs, I recieved the following error
>> "There not enough room for process 11 to store PROC_HDR
>> 0x5975000 in Pss.
>> What doesn't it have room for? The system databases
have
>> plenty of room.
>> The error occurred on the 14th of about 30 transaction
>> logs being loaded. I am using SQL 6.5, I am unsure of
the
>> service pack level, it migt be 5a (the build number is
>> 6.50.479).
>> Any help would be greatly appreciated
>
>.
>

Friday, March 9, 2012

Error 5123 Cannot Attach DB

I'm getting Error 5123 "Cannot Open file because file is being used by
another process" when I try re-attaching a DB (.mdf) I had just detached.
I'm afraid I issued a DBCC command (which may be locking the file) right
before I detached the Database: DBCC OPENTRAN (oldoaiapp)
Does anyone know how I can identify and kill whatever process is attached to
my .mdf database? I obviously cannot use Query Analyzer as I cannot see the
database anymore.
Hi,
Probably your MDF or LDF file will be used by either Backup process or Anti
virus software. Verify both first and attach again.
If you still have issues then try to copy the files to a new folder and use
SP_ATTACH_DB to attach the database.
Incase if you still have issues then restart sql server service.
Thanks
Hari
SQL Server MVP
"Leslie" <Leslie@.discussions.microsoft.com> wrote in message
news:B94C2796-66C4-4641-B3C5-5B7F597CC7B2@.microsoft.com...
> I'm getting Error 5123 "Cannot Open file because file is being used by
> another process" when I try re-attaching a DB (.mdf) I had just detached.
> I'm afraid I issued a DBCC command (which may be locking the file) right
> before I detached the Database: DBCC OPENTRAN (oldoaiapp)
> Does anyone know how I can identify and kill whatever process is attached
> to
> my .mdf database? I obviously cannot use Query Analyzer as I cannot see
> the
> database anymore.
>
|||Hari,
I cannot copy the files as I get the same lock error. I have determined it
is indeed SQL Server which is locking the files. I have rebooted the SQL
Server as well, and that does not clear the file locks. I'm afraid the DBCC
OpenTran (oldoaiapp) is what caused the lock.
I tried the Query Analyzer command below and am getting the error below (the
filename path IS correct):
EXEC sp_attach_db @.dbname = 'OldOAIApp',
@.filename1 = N'C:\SQLData\MSSQL\Data\POAIAPP.mdf',
@.filename2 = N'C:\SQLData\MSSQL\Data\POAIAPP_log.ldf'
Error:
Server: Msg 5105, Level 16, State 4, Line 1
Device activation error. The physical file name
'C:\SQLData\MSSQL\Data\POAIAPP.mdf' may be incorrect.
"Hari Prasad" wrote:

> Hi,
> Probably your MDF or LDF file will be used by either Backup process or Anti
> virus software. Verify both first and attach again.
> If you still have issues then try to copy the files to a new folder and use
> SP_ATTACH_DB to attach the database.
> Incase if you still have issues then restart sql server service.
> Thanks
> Hari
> SQL Server MVP
|||Hi,
Can you stop MSSQL Server service and copy both files into a new folder.
Then rename the copied files to a different name
and try to attach the database.
Also verify the file names and directory you mention is correct.
Thanks
Hari
SQL Server MVP
"Leslie" <Leslie@.discussions.microsoft.com> wrote in message
news:A9250A47-F159-4DD0-B7B3-B3AE24638468@.microsoft.com...
> Hari,
> I cannot copy the files as I get the same lock error. I have determined
> it
> is indeed SQL Server which is locking the files. I have rebooted the SQL
> Server as well, and that does not clear the file locks. I'm afraid the
> DBCC
> OpenTran (oldoaiapp) is what caused the lock.
> I tried the Query Analyzer command below and am getting the error below
> (the
> filename path IS correct):
> EXEC sp_attach_db @.dbname = 'OldOAIApp',
> @.filename1 = N'C:\SQLData\MSSQL\Data\POAIAPP.mdf',
> @.filename2 = N'C:\SQLData\MSSQL\Data\POAIAPP_log.ldf'
> Error:
> Server: Msg 5105, Level 16, State 4, Line 1
> Device activation error. The physical file name
> 'C:\SQLData\MSSQL\Data\POAIAPP.mdf' may be incorrect.
> "Hari Prasad" wrote:
>
|||Thanks Hari,
I will try the stopping of SQL Server and do the file move/renames after
hours. I think this will work and hopefully SQL Server won't choke on
restart!
Cheers,
Leslie
"Hari Prasad" wrote:

> Hi,
> Can you stop MSSQL Server service and copy both files into a new folder.
> Then rename the copied files to a different name
> and try to attach the database.
> Also verify the file names and directory you mention is correct.
> Thanks
> Hari
> SQL Server MVP
> "Leslie" <Leslie@.discussions.microsoft.com> wrote in message
> news:A9250A47-F159-4DD0-B7B3-B3AE24638468@.microsoft.com...
>
>

Error 5123 Cannot Attach DB

I'm getting Error 5123 "Cannot Open file because file is being used by
another process" when I try re-attaching a DB (.mdf) I had just detached.
I'm afraid I issued a DBCC command (which may be locking the file) right
before I detached the Database: DBCC OPENTRAN (oldoaiapp)
Does anyone know how I can identify and kill whatever process is attached to
my .mdf database? I obviously cannot use Query Analyzer as I cannot see the
database anymore.Hi,
Probably your MDF or LDF file will be used by either Backup process or Anti
virus software. Verify both first and attach again.
If you still have issues then try to copy the files to a new folder and use
SP_ATTACH_DB to attach the database.
Incase if you still have issues then restart sql server service.
Thanks
Hari
SQL Server MVP
"Leslie" <Leslie@.discussions.microsoft.com> wrote in message
news:B94C2796-66C4-4641-B3C5-5B7F597CC7B2@.microsoft.com...
> I'm getting Error 5123 "Cannot Open file because file is being used by
> another process" when I try re-attaching a DB (.mdf) I had just detached.
> I'm afraid I issued a DBCC command (which may be locking the file) right
> before I detached the Database: DBCC OPENTRAN (oldoaiapp)
> Does anyone know how I can identify and kill whatever process is attached
> to
> my .mdf database? I obviously cannot use Query Analyzer as I cannot see
> the
> database anymore.
>|||Hari,
I cannot copy the files as I get the same lock error. I have determined it
is indeed SQL Server which is locking the files. I have rebooted the SQL
Server as well, and that does not clear the file locks. I'm afraid the DBCC
OpenTran (oldoaiapp) is what caused the lock.
I tried the Query Analyzer command below and am getting the error below (the
filename path IS correct):
EXEC sp_attach_db @.dbname = 'OldOAIApp',
@.filename1 = N'C:\SQLData\MSSQL\Data\POAIAPP.mdf',
@.filename2 = N'C:\SQLData\MSSQL\Data\POAIAPP_log.ldf'
Error:
Server: Msg 5105, Level 16, State 4, Line 1
Device activation error. The physical file name
'C:\SQLData\MSSQL\Data\POAIAPP.mdf' may be incorrect.
"Hari Prasad" wrote:

> Hi,
> Probably your MDF or LDF file will be used by either Backup process or Ant
i
> virus software. Verify both first and attach again.
> If you still have issues then try to copy the files to a new folder and u
se
> SP_ATTACH_DB to attach the database.
> Incase if you still have issues then restart sql server service.
> Thanks
> Hari
> SQL Server MVP|||Hi,
Can you stop MSSQL Server service and copy both files into a new folder.
Then rename the copied files to a different name
and try to attach the database.
Also verify the file names and directory you mention is correct.
Thanks
Hari
SQL Server MVP
"Leslie" <Leslie@.discussions.microsoft.com> wrote in message
news:A9250A47-F159-4DD0-B7B3-B3AE24638468@.microsoft.com...
> Hari,
> I cannot copy the files as I get the same lock error. I have determined
> it
> is indeed SQL Server which is locking the files. I have rebooted the SQL
> Server as well, and that does not clear the file locks. I'm afraid the
> DBCC
> OpenTran (oldoaiapp) is what caused the lock.
> I tried the Query Analyzer command below and am getting the error below
> (the
> filename path IS correct):
> EXEC sp_attach_db @.dbname = 'OldOAIApp',
> @.filename1 = N'C:\SQLData\MSSQL\Data\POAIAPP.mdf',
> @.filename2 = N'C:\SQLData\MSSQL\Data\POAIAPP_log.ldf'
> Error:
> Server: Msg 5105, Level 16, State 4, Line 1
> Device activation error. The physical file name
> 'C:\SQLData\MSSQL\Data\POAIAPP.mdf' may be incorrect.
> "Hari Prasad" wrote:
>
>|||Thanks Hari,
I will try the stopping of SQL Server and do the file move/renames after
hours. I think this will work and hopefully SQL Server won't choke on
restart!
Cheers,
Leslie
"Hari Prasad" wrote:

> Hi,
> Can you stop MSSQL Server service and copy both files into a new folder.
> Then rename the copied files to a different name
> and try to attach the database.
> Also verify the file names and directory you mention is correct.
> Thanks
> Hari
> SQL Server MVP
> "Leslie" <Leslie@.discussions.microsoft.com> wrote in message
> news:A9250A47-F159-4DD0-B7B3-B3AE24638468@.microsoft.com...
>
>