Error message referring to missing MSDHTML.OCX.
Your operating system is missing a required Microsoft file that can be obtained from the following patch:
Error message referring to missing MSDATGRD.OCX
Download the missing control from the following link:
Extract the zip to an empty folder, then copy the three extract files to your system32 folder. Next, register the MSDATGRD.OCX file via the following command, either via a command prompt your your Start menu Run command.
Adjust the path to the MSDATGRD.OCX file to suit your Windows installation.
After running the above command you should then receive an registration success message box.
Fact Sheet Fusion gives an error message that it can't save a record.
Ensure you have upgraded your FSF installation to the latest available.
- If you are running Windows Vista/7/8 check that you have saved or copied your .fusion database and associated folder to a location that is accessible to your account. E.g. My Documents. Tip: Don't save and work with your Fusion databases in the FSF installation folder.
- Try executing the FSF executable with higher privileges. That is right click on the FSF shortcut within your start menu and select the 'Run as Administrator' option from the pop-up context menu. You can make this option permanent by right clicking the shortcut and selecting 'Properties' option from the context menu.
- Check that you have enough drive space available.
- If running from a network drive, ensure the network speed is adequate, with no delays that could effect the write time to the database.
- Ensure no other user has the .Fusion database open at the same time you are attempting to use it.
Normally any errors generated during the export process relate to the selected template. If you are using a custom template ensure that the template is valid XML and loads without any errors. An easy way to check for errors within your template.xsl file is to load it via Internet Explorer. Any errors within the XML document will be reported by IE, along with an error description and line number where the problem occurred.
Another less common cause for export errors are corrupted images. If you receive an error message related to an image, check that it can be opened by your preferred graphics package. Also try re-exporting/saving the graphic again from your preferred graphics. Check the graphic is not in a 36bit format as this is not supported within FSF.
Missing images reported during the export process.
During the export process FSF can no longer find the attached image for the given entity. This is normally due to the file being renamed, moved or deleted in the Fusion database media folder outside the scope of FSF. To correct this. Either replace the image back to the correct entity folder using the same file name when attached in FSF. Or reattach the image via FSF. Note if you choose to reattach the image it will be treated as a new image and the caption may need to be re-entered.