Errors 5981, Error 5460 are all caused when Word’s Protected View is triggered.
It is because Word does not trust the document being opened for one reason or another.
Protected View settings and Trusted Locations are something that would usually be configured by your IT department and if Protected View is triggered then Word will prevent the document from being edited by the Insolvency merge process and will result in this error from Insol.
Solution 1
You can simply disable Protected View in Word to get around the problem (this should resolve the problem in the short term whilst you implement solution 2 which is detailed below).
To disable protected view in Word you can follow these steps:-
- Close Insolvency
- Close all open word documents.
- Open task manager and kill all instances of WinWord.exe
- Disable Protected View
Open Word and go to File>Options>Trust Centre>Trust Centre Settings
Trust Centre
Make sure the "Disable all Trusted Locations" is not ticked:
Protected View
If the Trust Centre Settings will not allow you to open a document without the Protected View Disabled. Then you may need to disable the Protected view options.
Macro Settings
Set macro settings to the VBA object model: - Restart Word again and make sure the settings have saved (often they don’t)
- Open Insolvency and try the document again, it should now work without error
Solution 2
This is the recommended solution. If you need Protected View to be enabled then you need to figure out what causes it to be triggered. There are 3 main things that can cause it:-
- Is the Merge Template folder (and sub folders) location a Trusted Location
- Is the document management root folder (and sub folders) a Trusted Location
- Is the document template that you are merging blocked (locate the template in the network folder, right mouse click on the template and select properties)
Once you have confirmed these then try re-enabling Protected View and try the merge again.
All Protected View settings can be configured across the network via Group Policy.
Comments
0 comments
Please sign in to leave a comment.