I’ve upgraded from BigFix 10.0.4.32 to 10.0.6. Now in my console, computers load, sites load, etc but Fixlets and tasks just says “Loading…” and it has been 10minutes+. I cleared the console cache, closed and repoened and same. I see this from the console on 2 difference devices.
Anyone seeing this with 10.0.6 ?
Looking some more, all the content is there but none of it is relevant (none of all 110,468). This is the problem but I have no idea why.
For some reason the index on table FIXLETRESULTS was not created, maybe from a bug in 10.0.5 (https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0098680)
Sat, 11 Jun 2022 00:26:58 +0000 - /data/differenced-fixlet-results (1952) - {call fetch_fixletResults( ?, ?, ? )}
Sat, 11 Jun 2022 00:26:58 +0000 - /data/differenced-fixlet-results (1952) - [Microsoft][SQL Server Native Client 11.0][SQL Server]Index ‘IX_CID’ on table ‘FIXLETRESULTS’ (specified in the FROM clause) does not exist. (37000: 308)
It seems to be connected or may happen if WebUI is not stopped when upgrade is in progress.
https://help.hcltechsw.com/bigfix/10.0/platform/Platform/Installation/c_important.html#:~:text=Ensure%20that%20the%20BigFix%20WebUI%20service%20is%20stopped%20before%20starting%20to%20upgrade%20the%20BigFix%20components%2C%20and%20do%20not%20start%20it%20again%20until%20the%20overall%20upgrade%20procedure%20completes%20successfully
Please follow the steps below:
- stop all Bigfix services on the Root Server
- stop WebReports and WebUI services as well, if it is on another system
- close the Console
- run the following query to create the missing index:
use BFEnterprise
CREATE INDEX IX_CID ON dbo.FIXLETRESULTS( ComputerID ) INCLUDE ( IsRelevant );
exec sp_indexoption ‘FIXLETRESULTS.IX_CID’, ‘AllowPageLocks’, FALSE;
- after completing the query, verify the index exists in the table. You have to refresh the database view, to have the updated indexes’ list.
- finally, start all the BigFix services
2 Likes
First post: “Sounds like a database problems that will show up in BESRelay.log”
Second post: “Hmm I didn’t expect a missing index to be the database problem”.
Aside from the index referenced in the log message, did Support step through checking all the other indexes are set up as expected? I could export a list of indexes on my server if it helps?