Faulting module excel exe

And they were able to access the same excel file in this user machine. But if this user open that excel file it crashes. Products 72 Special Topics 41 Video Hub Most Active Hubs Microsoft Teams. Security, Compliance and Identity. Microsoft Edge Insider.

Azure Databases. Autonomous Systems. Education Sector. Microsoft Localization. Microsoft PnP. Healthcare and Life Sciences. According to what I read on forums, it seems there is a permission issue. Windows will notify you if a solution is available. DLL State[0]. DoneStage1 State[0]. Attachments: Up to 10 attachments including images can be used with a maximum of 3. After exploring both process monitor log file, there seem to have behavior differences between both scenarios but I can't explain why.

In addition, if this problem is more urgent for you I still recommend that you open a case to Microsoft for further professional help. You should contact the vendor of this application and see if they can help you sort out the problem. AroldFrey Hi, The nacl Thread starter caroleary Start date Jun 14, Joined Jun 11, Messages 3. Users have many spreadsheets saved on a shared drive on a server. Any one of three users can access and work on them. Occasionally one will open one of the docs, which also work with Hyperion Retrieve, and Excel will crash with the "serious error" message and this event will be in the log.

Hyperion logs are clean as a whistle. Seems to happen at a specific time of day, but there is no scanning or backup running at the time. One of the two times it happened, Symantec was updating definitions. Also, seems to happen when they click on "print". But it is not the security patch problem because they all have the "patch for the patch" KB Any ideas? Excel Facts. Workdays for a market open Mon, Wed, Friday? Click here to reveal answer.

The 7 digits start on Monday. Trybly New Member. Joined Apr 15, Messages 4. It is allocated on a server. A file size 7,3 MB. Office file format. Basically one user for the last week one user who with this file works used uses. Next day the user opens a file, the window with the message emerges: In the book "filename" contents which did not manage to be read are revealed. Additionally, in the Application Event log, you may find a crash signature similar to the following in event ID Follow the steps in this section carefully.

Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur. Start Registry Editor. To do this, use one of the following procedures, as appropriate for your version of Windows.