I need to find a better way to handle DTS Job Failure issue. Currently, we have about 50 jobs which executed through DTS packages. Everytime when sources were not there or came in late, the DTS sent out an email to my page which I carried every day. Some those came in during the holidays even though I know the source party wont generate the source files at that day.
Trying to avoid to get beep everytime when job was failed. Someone suggested that it is possible to add kind of executable file within the Custom task and let it trigger the DTS packages. If, for example, a holiday then dont run the package so I wont get the page.
Any hints suggestions would be greatly appreciated
J827I get unhappy when I see 0 replies, but I have not done this before but this is how I would handle it.
I would write a dll in VB. It would check todays date against a list of holidays I might keep in a database table. If it did'nt return a result I would would use the VB syntax for firing off stored procedures (still in my dll).
Of course before you do this you need to already have your 50 DTS packages in place.
I would then build a new DTS package whose only step was to fire off this custom DLL. Register your cutom task and assign it icon and then build your DTS package using the DTS Designer (not the wizard).
Good luck.|||create a table or array with the dates of all non action days (holidays weekends down days).
create a master package that runs all of your sub packages(use the execute package task).
create a Execute SQL (or activex)Task to evaluate the NonActiveDays table against the execution of the package if getdate() = @.nonactiveday, return 0
else 1
then pass that value as a global variable to the task
when the 1 hits, run the package
this is a fairly simple solution.
and just for giggles if your code returns a 0, you can have the task email you a reminder that the task didnt run becuase of a holiday.
this opens you up to many possibllilties, for instance you could have this code run in a job the day before to remind you that the next day is a holiday and dts wont run...|||thanks thanks!|||Are you executing this from the web like in ASP.Net or something?
If you are, the problem is that the DTS package needs to run in the same security context that you created it in. The IUSR_etc... account in IIS does not have the ability to execute the package. The workarounds are sloppy and I have discussed them on this forum before. Do a search for ASP and DTS.|||I created a C# Console Application to trigger the DTS package directly and it worked (see code below). But it was an EXE (not DLL) file type.
I would like to plug this app as part of control in an existing DTS package by adding it into a Custom Task. I just noticed the DTS Custom Task only allows adding DLL format file to be registered. Then I recreated the app with Class library Type and tried to register / run Regsvr32 appName. I got Could not find entry point for DLLRegisterServer in the DLL / appName.DLL was load but the DLLRegisterServer entry point was not found, the file cant be registered.
Any helps would be highly appreciated!
---------------------
try
{
DTS.Package2Class package = new DTS.Package2Class();
object pVarPersistStgOfHost = null;
string ServerName = "DEV";
string ServerUserName = null;
string ServerPassword = null;
string PackagePassword = null;
string PackageGUID = null;
string PackageVersionGUID = null;
string PackagName = "DTSTestPackage";
package.LoadFromSQLServer(
ServerName,
ServerUserName,
ServerPassword,
DTS.DTSSQLServerStorageFlags.DTSSQLStgFlag_UseTrus tedConnection,
PackagePassword,
PackageGUID,
PackageVersionGUID,
PackagName,
ref pVarPersistStgOfHost);
package.Execute();
package.UnInitialize();
// force Release() on COM object
System.Runtime.InteropServices.Marshal.ReleaseComO bject(package);
package = null;
}
catch(System.Runtime.InteropServices.COMException e)
{
Console.WriteLine("COMException {0}", e.ErrorCode.ToString() );
Console.WriteLine("{0}", e.Message);
Console.WriteLine("{0}", e.Source);
Console.WriteLine("Stack dump\n{0}\n", e.StackTrace);
}
catch(System.Exception e)
{
Console.WriteLine("Exception");
Console.WriteLine("{0}", e.Message);
Console.WriteLine("{0}", e.Source);
Console.WriteLine("Stack dump\n{0}\n", e.StackTrace);
}
Showing posts with label failure. Show all posts
Showing posts with label failure. Show all posts
Monday, February 27, 2012
Friday, February 24, 2012
Help - An unknown full-text failure (80004005) while trying to create a new full-text cata
Hi,
We just started getting this error when trying to create new catalogs
on databases that do not already have a Full-Text catalog. I can
create a new catalog on a database that has an existing catalog, but
cannot on one that does not.
I get the following error: "An unknown full-text failure (80004005)
occurred in function EnumCatalogs on full-text catalog" when I try to
create a new catalog through Enterprise Manager and this error when I
execute sp_FullText_Database:
"Server: Msg 7608, Level 17, State 1, Procedure sp_fulltext_database,
Line 46
An unknown full-text failure (80004005) occurred in function
EnumCatalogs on full-text catalog ''."
Line 46 in sp_fulltext_database looks to be:
DBCC CALLFULLTEXT ( 7, @.dbid )-- FTDropAllCatalogs ( "@.dbid" )
I've seen plenty of postings of this error, but they are all for SQL
Server 7.0.
We're running SQL Server 2000:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003
16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
Any ideas?
Thanks in advance.
Andy
Andrew,
You are correct *most* of the causes for the "unknown full-text failure
(80004005) while trying to create a new full-text catalog" in SQL Server
2000 were either eliminated or more specific error text messages were
defined. Still, you should check the obvious causes, for example, have you
recently changed the DCOM settings on this server? Have you or anyone else
changed the MSSQLServer startup account via Win2K's Component services? Does
the SQL logon account BUILTIN\Administrator exist with the default settings
of master database and have sysadmin privileges? Is this SQL Server
installed on a Domain Controller (DC) or backup DC (BDC)? Except for the
DCOM setting & installed on a DC/BDC, you should of gotten different error
text messages if any other changes were made. You should review the
following KB articles:
277549 (Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K Component
Services]
http://support.microsoft.com/default...B;EN-US;277549
317746 (Q317746) PRB: SQL Server Full-Text Search Does Not Populate Catalogs
http://support.microsoft.com/default...b;en-us;317746
263712 (Q263712) INF: How to Impede Windows NT Administrators from
Administering a Clustered SQL Server
http://support.microsoft.com/default...B;EN-US;263712
Depending upon your answers, it may be necessary to re-install the SQL FTS
components via the procedures doc'ed in the following KB article: 827449 How
to manually reinstall the Microsoft Search service for an instance of SQL
2000
http://support.microsoft.com/default...b;EN-US;827449
Regards,
John
"Andrew Zoltay" <andy_trek@.hotmail.com> wrote in message
news:69abe98.0406281407.6885baa7@.posting.google.co m...
> Hi,
> We just started getting this error when trying to create new catalogs
> on databases that do not already have a Full-Text catalog. I can
> create a new catalog on a database that has an existing catalog, but
> cannot on one that does not.
> I get the following error: "An unknown full-text failure (80004005)
> occurred in function EnumCatalogs on full-text catalog" when I try to
> create a new catalog through Enterprise Manager and this error when I
> execute sp_FullText_Database:
> "Server: Msg 7608, Level 17, State 1, Procedure sp_fulltext_database,
> Line 46
> An unknown full-text failure (80004005) occurred in function
> EnumCatalogs on full-text catalog ''."
> Line 46 in sp_fulltext_database looks to be:
> DBCC CALLFULLTEXT ( 7, @.dbid ) -- FTDropAllCatalogs ( "@.dbid" )
> I've seen plenty of postings of this error, but they are all for SQL
> Server 7.0.
> We're running SQL Server 2000:
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003
> 16:08:15
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> Any ideas?
> Thanks in advance.
> Andy
|||Andrew,
You are correct *most* of the causes for the "unknown full-text failure
(80004005) while trying to create a new full-text catalog" in SQL Server
2000 were either eliminated or more specific error text messages were
defined. Still, you should check the obvious causes, for example, have you
recently changed the DCOM settings on this server? Have you or anyone else
changed the MSSQLServer startup account via Win2K's Component services? Does
the SQL logon account BUILTIN\Administrator exist with the default settings
of master database and have sysadmin privileges? Is this SQL Server
installed on a Domain Controller (DC) or backup DC (BDC)? Except for the
DCOM setting & installed on a DC/BDC, you should of gotten different error
text messages if any other changes were made. You should review the
following KB articles:
277549 (Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K Component
Services]
http://support.microsoft.com/default...B;EN-US;277549
317746 (Q317746) PRB: SQL Server Full-Text Search Does Not Populate Catalogs
http://support.microsoft.com/default...b;en-us;317746
263712 (Q263712) INF: How to Impede Windows NT Administrators from
Administering a Clustered SQL Server
http://support.microsoft.com/default...B;EN-US;263712
Depending upon your answers, it may be necessary to re-install the SQL FTS
components via the procedures doc'ed in the following KB article: 827449 How
to manually reinstall the Microsoft Search service for an instance of SQL
2000
http://support.microsoft.com/default...b;EN-US;827449
Regards,
John
"Andrew Zoltay" <andy_trek@.hotmail.com> wrote in message
news:69abe98.0406281407.6885baa7@.posting.google.co m...
> Hi,
> We just started getting this error when trying to create new catalogs
> on databases that do not already have a Full-Text catalog. I can
> create a new catalog on a database that has an existing catalog, but
> cannot on one that does not.
> I get the following error: "An unknown full-text failure (80004005)
> occurred in function EnumCatalogs on full-text catalog" when I try to
> create a new catalog through Enterprise Manager and this error when I
> execute sp_FullText_Database:
> "Server: Msg 7608, Level 17, State 1, Procedure sp_fulltext_database,
> Line 46
> An unknown full-text failure (80004005) occurred in function
> EnumCatalogs on full-text catalog ''."
> Line 46 in sp_fulltext_database looks to be:
> DBCC CALLFULLTEXT ( 7, @.dbid ) -- FTDropAllCatalogs ( "@.dbid" )
> I've seen plenty of postings of this error, but they are all for SQL
> Server 7.0.
> We're running SQL Server 2000:
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003
> 16:08:15
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> Any ideas?
> Thanks in advance.
> Andy
|||Andrew,
A follow-up to my reply below... There is now an updated KB article
"295772 (Q295772) How to debug full-text search when a 7608
(0x80004005) error message occurs in SQL Server" at
http://support.microsoft.com/?kbid=295772 that discuss in more detail
how to debug the unknown full-text failure (80004005) error you have
encountered. Let us know if you have resolved this error!
Thanks,
John
"John Kane" <jt-kane@.comcast.net> wrote in message news:<#Ju5y0ZXEHA.3892@.TK2MSFTNGP09.phx.gbl>...[vbcol=seagreen]
> Andrew,
> You are correct *most* of the causes for the "unknown full-text failure
> (80004005) while trying to create a new full-text catalog" in SQL Server
> 2000 were either eliminated or more specific error text messages were
> defined. Still, you should check the obvious causes, for example, have you
> recently changed the DCOM settings on this server? Have you or anyone else
> changed the MSSQLServer startup account via Win2K's Component services? Does
> the SQL logon account BUILTIN\Administrator exist with the default settings
> of master database and have sysadmin privileges? Is this SQL Server
> installed on a Domain Controller (DC) or backup DC (BDC)? Except for the
> DCOM setting & installed on a DC/BDC, you should of gotten different error
> text messages if any other changes were made. You should review the
> following KB articles:
> 277549 (Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
> MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K Component
> Services]
> http://support.microsoft.com/default...B;EN-US;277549
> 317746 (Q317746) PRB: SQL Server Full-Text Search Does Not Populate Catalogs
> http://support.microsoft.com/default...b;en-us;317746
> 263712 (Q263712) INF: How to Impede Windows NT Administrators from
> Administering a Clustered SQL Server
> http://support.microsoft.com/default...B;EN-US;263712
> Depending upon your answers, it may be necessary to re-install the SQL FTS
> components via the procedures doc'ed in the following KB article: 827449 How
> to manually reinstall the Microsoft Search service for an instance of SQL
> 2000
> http://support.microsoft.com/default...b;EN-US;827449
> Regards,
> John
>
>
>
> "Andrew Zoltay" <andy_trek@.hotmail.com> wrote in message
> news:69abe98.0406281407.6885baa7@.posting.google.co m...
|||Hi John,
Thanks for your quick response. Unfortunately, it was nothing out of
the "obvious" catagory. I checked into the suggested articles with no
luck either.
Found a workaround since we do have another server where there is no
problem creating catalogs. We'll probably end up doing the manual
reinstall you recommended, but currently don't have the time to try
it. It's not mission critical since it's just a dev server.
Thanks again!
Andy
"John Kane" <jt-kane@.comcast.net> wrote in message news:<#Ju5y0ZXEHA.3892@.TK2MSFTNGP09.phx.gbl>...[vbcol=seagreen]
> Andrew,
> You are correct *most* of the causes for the "unknown full-text failure
> (80004005) while trying to create a new full-text catalog" in SQL Server
> 2000 were either eliminated or more specific error text messages were
> defined. Still, you should check the obvious causes, for example, have you
> recently changed the DCOM settings on this server? Have you or anyone else
> changed the MSSQLServer startup account via Win2K's Component services? Does
> the SQL logon account BUILTIN\Administrator exist with the default settings
> of master database and have sysadmin privileges? Is this SQL Server
> installed on a Domain Controller (DC) or backup DC (BDC)? Except for the
> DCOM setting & installed on a DC/BDC, you should of gotten different error
> text messages if any other changes were made. You should review the
> following KB articles:
> 277549 (Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
> MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K Component
> Services]
> http://support.microsoft.com/default...B;EN-US;277549
> 317746 (Q317746) PRB: SQL Server Full-Text Search Does Not Populate Catalogs
> http://support.microsoft.com/default...b;en-us;317746
> 263712 (Q263712) INF: How to Impede Windows NT Administrators from
> Administering a Clustered SQL Server
> http://support.microsoft.com/default...B;EN-US;263712
> Depending upon your answers, it may be necessary to re-install the SQL FTS
> components via the procedures doc'ed in the following KB article: 827449 How
> to manually reinstall the Microsoft Search service for an instance of SQL
> 2000
> http://support.microsoft.com/default...b;EN-US;827449
> Regards,
> John
>
>
>
> "Andrew Zoltay" <andy_trek@.hotmail.com> wrote in message
> news:69abe98.0406281407.6885baa7@.posting.google.co m...
We just started getting this error when trying to create new catalogs
on databases that do not already have a Full-Text catalog. I can
create a new catalog on a database that has an existing catalog, but
cannot on one that does not.
I get the following error: "An unknown full-text failure (80004005)
occurred in function EnumCatalogs on full-text catalog" when I try to
create a new catalog through Enterprise Manager and this error when I
execute sp_FullText_Database:
"Server: Msg 7608, Level 17, State 1, Procedure sp_fulltext_database,
Line 46
An unknown full-text failure (80004005) occurred in function
EnumCatalogs on full-text catalog ''."
Line 46 in sp_fulltext_database looks to be:
DBCC CALLFULLTEXT ( 7, @.dbid )-- FTDropAllCatalogs ( "@.dbid" )
I've seen plenty of postings of this error, but they are all for SQL
Server 7.0.
We're running SQL Server 2000:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003
16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
Any ideas?
Thanks in advance.
Andy
Andrew,
You are correct *most* of the causes for the "unknown full-text failure
(80004005) while trying to create a new full-text catalog" in SQL Server
2000 were either eliminated or more specific error text messages were
defined. Still, you should check the obvious causes, for example, have you
recently changed the DCOM settings on this server? Have you or anyone else
changed the MSSQLServer startup account via Win2K's Component services? Does
the SQL logon account BUILTIN\Administrator exist with the default settings
of master database and have sysadmin privileges? Is this SQL Server
installed on a Domain Controller (DC) or backup DC (BDC)? Except for the
DCOM setting & installed on a DC/BDC, you should of gotten different error
text messages if any other changes were made. You should review the
following KB articles:
277549 (Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K Component
Services]
http://support.microsoft.com/default...B;EN-US;277549
317746 (Q317746) PRB: SQL Server Full-Text Search Does Not Populate Catalogs
http://support.microsoft.com/default...b;en-us;317746
263712 (Q263712) INF: How to Impede Windows NT Administrators from
Administering a Clustered SQL Server
http://support.microsoft.com/default...B;EN-US;263712
Depending upon your answers, it may be necessary to re-install the SQL FTS
components via the procedures doc'ed in the following KB article: 827449 How
to manually reinstall the Microsoft Search service for an instance of SQL
2000
http://support.microsoft.com/default...b;EN-US;827449
Regards,
John
"Andrew Zoltay" <andy_trek@.hotmail.com> wrote in message
news:69abe98.0406281407.6885baa7@.posting.google.co m...
> Hi,
> We just started getting this error when trying to create new catalogs
> on databases that do not already have a Full-Text catalog. I can
> create a new catalog on a database that has an existing catalog, but
> cannot on one that does not.
> I get the following error: "An unknown full-text failure (80004005)
> occurred in function EnumCatalogs on full-text catalog" when I try to
> create a new catalog through Enterprise Manager and this error when I
> execute sp_FullText_Database:
> "Server: Msg 7608, Level 17, State 1, Procedure sp_fulltext_database,
> Line 46
> An unknown full-text failure (80004005) occurred in function
> EnumCatalogs on full-text catalog ''."
> Line 46 in sp_fulltext_database looks to be:
> DBCC CALLFULLTEXT ( 7, @.dbid ) -- FTDropAllCatalogs ( "@.dbid" )
> I've seen plenty of postings of this error, but they are all for SQL
> Server 7.0.
> We're running SQL Server 2000:
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003
> 16:08:15
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> Any ideas?
> Thanks in advance.
> Andy
|||Andrew,
You are correct *most* of the causes for the "unknown full-text failure
(80004005) while trying to create a new full-text catalog" in SQL Server
2000 were either eliminated or more specific error text messages were
defined. Still, you should check the obvious causes, for example, have you
recently changed the DCOM settings on this server? Have you or anyone else
changed the MSSQLServer startup account via Win2K's Component services? Does
the SQL logon account BUILTIN\Administrator exist with the default settings
of master database and have sysadmin privileges? Is this SQL Server
installed on a Domain Controller (DC) or backup DC (BDC)? Except for the
DCOM setting & installed on a DC/BDC, you should of gotten different error
text messages if any other changes were made. You should review the
following KB articles:
277549 (Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K Component
Services]
http://support.microsoft.com/default...B;EN-US;277549
317746 (Q317746) PRB: SQL Server Full-Text Search Does Not Populate Catalogs
http://support.microsoft.com/default...b;en-us;317746
263712 (Q263712) INF: How to Impede Windows NT Administrators from
Administering a Clustered SQL Server
http://support.microsoft.com/default...B;EN-US;263712
Depending upon your answers, it may be necessary to re-install the SQL FTS
components via the procedures doc'ed in the following KB article: 827449 How
to manually reinstall the Microsoft Search service for an instance of SQL
2000
http://support.microsoft.com/default...b;EN-US;827449
Regards,
John
"Andrew Zoltay" <andy_trek@.hotmail.com> wrote in message
news:69abe98.0406281407.6885baa7@.posting.google.co m...
> Hi,
> We just started getting this error when trying to create new catalogs
> on databases that do not already have a Full-Text catalog. I can
> create a new catalog on a database that has an existing catalog, but
> cannot on one that does not.
> I get the following error: "An unknown full-text failure (80004005)
> occurred in function EnumCatalogs on full-text catalog" when I try to
> create a new catalog through Enterprise Manager and this error when I
> execute sp_FullText_Database:
> "Server: Msg 7608, Level 17, State 1, Procedure sp_fulltext_database,
> Line 46
> An unknown full-text failure (80004005) occurred in function
> EnumCatalogs on full-text catalog ''."
> Line 46 in sp_fulltext_database looks to be:
> DBCC CALLFULLTEXT ( 7, @.dbid ) -- FTDropAllCatalogs ( "@.dbid" )
> I've seen plenty of postings of this error, but they are all for SQL
> Server 7.0.
> We're running SQL Server 2000:
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003
> 16:08:15
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> Any ideas?
> Thanks in advance.
> Andy
|||Andrew,
A follow-up to my reply below... There is now an updated KB article
"295772 (Q295772) How to debug full-text search when a 7608
(0x80004005) error message occurs in SQL Server" at
http://support.microsoft.com/?kbid=295772 that discuss in more detail
how to debug the unknown full-text failure (80004005) error you have
encountered. Let us know if you have resolved this error!
Thanks,
John
"John Kane" <jt-kane@.comcast.net> wrote in message news:<#Ju5y0ZXEHA.3892@.TK2MSFTNGP09.phx.gbl>...[vbcol=seagreen]
> Andrew,
> You are correct *most* of the causes for the "unknown full-text failure
> (80004005) while trying to create a new full-text catalog" in SQL Server
> 2000 were either eliminated or more specific error text messages were
> defined. Still, you should check the obvious causes, for example, have you
> recently changed the DCOM settings on this server? Have you or anyone else
> changed the MSSQLServer startup account via Win2K's Component services? Does
> the SQL logon account BUILTIN\Administrator exist with the default settings
> of master database and have sysadmin privileges? Is this SQL Server
> installed on a Domain Controller (DC) or backup DC (BDC)? Except for the
> DCOM setting & installed on a DC/BDC, you should of gotten different error
> text messages if any other changes were made. You should review the
> following KB articles:
> 277549 (Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
> MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K Component
> Services]
> http://support.microsoft.com/default...B;EN-US;277549
> 317746 (Q317746) PRB: SQL Server Full-Text Search Does Not Populate Catalogs
> http://support.microsoft.com/default...b;en-us;317746
> 263712 (Q263712) INF: How to Impede Windows NT Administrators from
> Administering a Clustered SQL Server
> http://support.microsoft.com/default...B;EN-US;263712
> Depending upon your answers, it may be necessary to re-install the SQL FTS
> components via the procedures doc'ed in the following KB article: 827449 How
> to manually reinstall the Microsoft Search service for an instance of SQL
> 2000
> http://support.microsoft.com/default...b;EN-US;827449
> Regards,
> John
>
>
>
> "Andrew Zoltay" <andy_trek@.hotmail.com> wrote in message
> news:69abe98.0406281407.6885baa7@.posting.google.co m...
|||Hi John,
Thanks for your quick response. Unfortunately, it was nothing out of
the "obvious" catagory. I checked into the suggested articles with no
luck either.
Found a workaround since we do have another server where there is no
problem creating catalogs. We'll probably end up doing the manual
reinstall you recommended, but currently don't have the time to try
it. It's not mission critical since it's just a dev server.
Thanks again!
Andy
"John Kane" <jt-kane@.comcast.net> wrote in message news:<#Ju5y0ZXEHA.3892@.TK2MSFTNGP09.phx.gbl>...[vbcol=seagreen]
> Andrew,
> You are correct *most* of the causes for the "unknown full-text failure
> (80004005) while trying to create a new full-text catalog" in SQL Server
> 2000 were either eliminated or more specific error text messages were
> defined. Still, you should check the obvious causes, for example, have you
> recently changed the DCOM settings on this server? Have you or anyone else
> changed the MSSQLServer startup account via Win2K's Component services? Does
> the SQL logon account BUILTIN\Administrator exist with the default settings
> of master database and have sysadmin privileges? Is this SQL Server
> installed on a Domain Controller (DC) or backup DC (BDC)? Except for the
> DCOM setting & installed on a DC/BDC, you should of gotten different error
> text messages if any other changes were made. You should review the
> following KB articles:
> 277549 (Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
> MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K Component
> Services]
> http://support.microsoft.com/default...B;EN-US;277549
> 317746 (Q317746) PRB: SQL Server Full-Text Search Does Not Populate Catalogs
> http://support.microsoft.com/default...b;en-us;317746
> 263712 (Q263712) INF: How to Impede Windows NT Administrators from
> Administering a Clustered SQL Server
> http://support.microsoft.com/default...B;EN-US;263712
> Depending upon your answers, it may be necessary to re-install the SQL FTS
> components via the procedures doc'ed in the following KB article: 827449 How
> to manually reinstall the Microsoft Search service for an instance of SQL
> 2000
> http://support.microsoft.com/default...b;EN-US;827449
> Regards,
> John
>
>
>
> "Andrew Zoltay" <andy_trek@.hotmail.com> wrote in message
> news:69abe98.0406281407.6885baa7@.posting.google.co m...
Subscribe to:
Posts (Atom)