FSD has not intialized
In one client i am getting following for VB graphic display
Error Creating ActivxX.HRESULT = 0x8abb0048
E_AFW_FSD_NOT _INITED(0x8abb0048) FSD has not been initialized.
why this issue happend? how to resolve this issue?
Voted best answer
Removing and adding nodes may mess up node settings like affinity, Clock Sync, etc. Doing this to an IM could cause you a lot of extra work since IM stores settings below its node object in the Node Administration Structure.
In most cases; let node remain in Node Administration Structure (=avoid "Remove Client/Server" exercises in the Config Wizard) disconnect it locally from the client, then reconnect using "Connect Node".
To clear the FSD cache, just erase its folder from OperateITTemp and stop/kill the AfwFSDNode.exe process - it will restart at next VB callup and then rebuild the cache.
However the reason to the not inited can be many.
- Check that OperateITTemp is writable and contains a FsdCache folder with lots of subfolders & files. Sometimes a "reused" client may have OperateITTemp folder from past system/domain/workgroup which is inaccessible. If so, take ownership and erase it, then "Connect Node" from Node Admin aspect or client's System Configuration wizard.
- A bad affinity may block this client from connecting the FSD Service
- Service Account incorrect?
- Related events in [Workplace Structure]Web System Workplace:System Event List?