Parag -
I too am experiencing the exact issue you reported. My workbook is compiled by a product called LockXLS, and becomes an executable that requires the installation of Excel to operate. My troubleshooting includes the vendor in the conversation, as I am unsure
of where the problem originates.
The error produces itself when the executable is on a file server and it is loaded from a workstation. The folder on the file server is wide open to our test user.
The program will run fine after the error is cleared. Funny thing is that we acknowledge the error 4 times. Don't know what that means.
Hope this provides some insight. Hopefully somebody will pick up on this thread and tell us what we are seeing!