I'm seeing some new behaviour on my site that I can't account for.
Each morning I collect a list of new products to add to our cs2k2 fp1
site and load it using :
CatalogManager.Im****tXML (im****tFilename, UpdateOnly, RunSynchronously,
GenerateFullTextIndexes)
which worked flawlessly until recently. Now it seems like every couple
of times I call GenerateFullTextIndexes it hangs the SQL Server.
I get a number of error messages like:
Microsoft.CommerceServer.Runtime.CommerceException: Timeout expired
---> System.Runtime.InteropServices.COMException (0x80040E31): Timeout
expired
from different operations on the website.
I've deleted and rebuilt the catalogs - didn't fix it. If it's left
long enough it kills any operation which access the database.
If I kill mssearch.exe (and restart the service) I'm up and running.
This has worked for years w/o problems but lately it's killing me.
(since migrating to fp1?) I've read about the
updatefulltextcatalogs.vbs but I'm not sure - should i be running it
instead of passing GenerateFullTextIndexes=true ?
Should I migrate my code to the FP1 im****txml? Should I just pass false
for GenerateFullTextIndexes ?
