Excel exe модуль unknown

Спасибо за ссылку, обязательно изучу материал. Я пока только осваиваю VBA и сам понимаю что получилось громоздко. Но давайте по существу.

Сделал костыли…

Дело в том, что MultiPage’и не могут обработать параметры выдаваемые им во время загрузки формы (могут только после загрузки формы), добавил промежуточную форму, вынес обработку MultiPage’ев в отдельную процедуру, вроде как пашет… но это вот как раз не оптимизация кода, а совсем наоборот. Что скажете?

Добавлено через 3 минуты
… а нет, не пашет

Теперь вот:

Сигнатура проблемы:
Имя события проблемы: BEX
Имя приложения: EXCEL.EXE
Версия приложения: 14.0.4756.1000
Отметка времени приложения: 4b9c08e8
Имя модуля с ошибкой: unknown
Версия модуля с ошибкой: 0.0.0.0
Отметка времени модуля с ошибкой: 00000000
Смещение исключения: 00000000
Код исключения: c0000005
Данные исключения: 00000008
Версия ОС: 6.1.7601.2.1.0.256.1
Код языка: 1049

Дополнительные сведения об этой проблеме:
LCID: 1049
skulcid: 1049

Добавлено через 16 минут

Вы попробуйте закрыть Excel и выполнить Start из другой книги по кнопке с панели инструментов. Погоняйте стартовую форму, поюзайте контролы, может выдаст ошибку. У меня периодически отрабатывает без ошибок. Да и фиг бы с ней, но на работе постоянно открыто 10-15 книг и один такой крит уведёт все книги с собой не сохранив.

Добавлено через 9 минут
Вот кусок дампа или как его там, я тут вообще не шарю…

sharedOfficeSoftwareProtectionPlatformOSPPCEXT.D LL». Невозможно найти или открыть PDB-файл.
«EXCEL.EXE» (Win32). Загружено «C:WindowsSysWOW64crypt32.dll». Символы загружены.
«EXCEL.EXE» (Win32). Загружено «C:WindowsSysWOW64msasn1.dll». Символы загружены.
«EXCEL.EXE» (Win32). Загружено «C:WindowsSysWOW64WinSCard.dll». Символы загружены.
«EXCEL.EXE» (Win32). Загружено «C:WindowsSysWOW64winhttp.dll». Символы загружены.
«EXCEL.EXE» (Win32). Загружено «C:WindowsSysWOW64webio.dll». Символы загружены.
«EXCEL.EXE» (Win32). Загружено «C:WindowsSysWOW64winmm.dll». Символы загружены.
«EXCEL.EXE» (Win32). Загружено «C:WindowsSysWOW64FM20ENU.DLL». Невозможно найти или открыть PDB-файл.
Поток 0x174c завершился с кодом 0 (0x0).
Необработанное исключение по адресу 0x74A3CB49 в EXCEL.EXE: 0xC0000005: нарушение прав доступа при исполнении по адресу 0x00000000.

When talking about MS Office error messages, it’s always a long story. Users would report hundreds of different error messages they received when they open Word, Excel, or PowerPoint. For some common errors like Runtime Error 1004 or add-in template is not valid, we have already introduced how can you fix them. This time, we will talk about another error message — Compile error in hidden module.

Users often received this error message when they start Excel. In rare times, when users start MS Word, this error would also pop up. Usually, users would see one of the following error messages:

• Compile error in hidden module: AutoExec
• Compile error in hidden module: AutoExecNew
• Compile error in hidden module: DistMon

The different suffixes indicate that you have different culprits to blame, and that’s why there is more than one solution for you to solve the problem. Before checking the solutions, you should know the reasons why you see these error messages.

Why Do I See the Error Message of Compile Error in Hidden Module?

Now Office 2016 is upgraded from a 32-bit version to a 64-bit version. The Compile error in hidden module error message usually appears when there are dome 32-bit add-ins versions of the office in your computer, and they are incompatible with the 64-bit version.

Two common conditions that would cause this error are as follow:

1. When MS Excel startup folder contains both the following two template files on Adobe Acrobat PDF Maker add-in:

• Pdfmaker.dot
• Pdfmaker.xla

2. Your computer has installed the Norton Anti-virus software.

After knowing what causes this error message, now it’s time to apply the solutions. Here we have listed four solutions, you can try them one by one until you solve the problem.

Method 1. Re-register OCX Files with CMD

The first solution you can try is to re-register some basic Excel function files. In this method, we need to apply Windows Command Prompt.

Step 1. Press Windows + R keys at the same time. Type cmd in the run box.

Step 2. Type the following command and press Enter.

For 32-bit:

regsvr32 -u c:windowssystem32mscomctl.ocx

regsvr32 c:windowssystem32mscomctl.ocx

For 64-bit:

regsvr32 -u c:windowssystem64mscomctl.ocx

regsvr32 c:windowssystem64mscomctl.ocx

Step 3. Now run MS Excel again to check if the error message still exists.

Method 2. Delete .exd Files

The exd file is a control information cache file of Microsoft Office. These files are created when a user inserts an ActiveX control into a document using the Control Toolbox in an MS Office program. You can delete this cache file to see if it can fix the Compile error in the hidden module error.

Step 1. Press Windows + R keys at the same time. Type %appdata% in the run box.

Step 2. It will open your AppData folder. Go to Roaming > Microsoft > Forms.

Step 3. Find the .exd files, select comctllib.exd and mscomctllib.exd, and delete these two files.

Step 4. Restart your Excel and check if the problem is solved.

Method 3. Move PDF Maker Files

As we have mentioned above, one of the reasons you will see this error message is because there are two template files on Adobe Acrobat PDF Maker add-in. So in this method, you can move the PDF Maker files to another place to fix your problem. Here are the detailed steps.

Step 1. Open Windows File Explorer, search pdfmaker.* on your computer.

Step 2. Choose the pdfmaker.dot and pdfmaker.xla files, right-click on both files, and select cut.

Step 3. Paste these two files to your Desktop.

Now you can restart the MS Excel to see if the problem is solved.

Method 4. Update to the Latest Adobe Acrobat

If the above methods can’t help you solve the Compile error in hidden module problem, the last resort is to update the Adobe Acrobat to the latest version. It’s because this problem is associated with the Adobe Acrobat that is installed on your computer.

Go to the Adobe official website, find the latest version of Acrobat, download and install it on your computer.

Bonus Solution: Repair Damaged or Corrupted MS Excel Efficiently

With the above methods, you might have solved the Excel Compile error in the hidden module issue. Then we’d like to share a good bonus tool — EaseUS Data Recovery Wizard with you. 

This is an advanced 4-in-1 specialized fix tool that enables you to repair corrupted  PDF documents and Office files in multiple formats. If your documents got damaged, Stellar file repair software will scan and repair them efficiently. 

If you want to try on this file repair software, you can download it and follow the guide to see how to use this tool. In the following guide, we have introduced how to repair Excel documents.

Step 1. Launch EaseUS Data Recovery Wizard. Select a disk location where the corrupted files are saved. Click «Scan» to start finding the broken files. EaseUS file repair tool allows you to fix damaged documents, videos, and pictures in differnet formats. 

Step 2. After scanning, you can quickly find corrupt data by file type. If you want to repair damaged Word, Excel, or PDF, select Documents and filter a specific category. For pictures and videos repair, all the common types are suppored, including JPEG, PNG, BMP, MOV, MP4, GIF, and more.

Step 3. EaseUS file repair software will automatically fix broken files. You can preview the repaired files before recovery. Last, click «Recover» and save the recovered files to a different location to avoid data overwriting.

The Bottom Line

That’s all about Compile error in hidden module error message. Hope you can fix your problem after reading this article. Once again, we’d like to introduce EaseUS file repair tool. No matter whether you need to repair Word, Excel, PPT, or PDF documents, applying this tool is a wise choice.

This is a well-described issue, and it exactly matches what I have just experienced (even including the fact that I haven’t been versioning recently).

My file has an xlsb suffix. Resaving with a different suffix did not work for me on the same PC, but I emailed the file to another PC, opened it, saved as xlsm, sent it back to the original machine and it now works fine again. I can even re-save with my preferred xlsb suffix and it still works.

I’ve also run this script to make a backup of my modules:

Sub ExportVbaModules()
     
'Acknowledgements to Andy Pope [ozgrid thread 60787]
     
    Dim objMyProj As VBProject 'if error, go to VBA editor - tools - References - Microsoft Visual Basic-Extensibility5.3
    Dim objVBComp As VBComponent
     
    Set objMyProj = Application.ActiveWorkbook.VBProject
     
    For Each objVBComp In objMyProj.VBComponents
        If objVBComp.Type = vbext_ct_StdModule And objVBComp.Name <> "" Then
            objVBComp.Export "C:UsersMyNameVbaBackups" & objVBComp.Name & ".txt"
        End If
    Next

End Sub

The And objVBComp.Name <> "" stops it from erroring when it encounters a corrupted module but turned out not to be necessary as the ‘fixed’ file contained no corrupted modules.

Since that export routine is so fast (40 modules / 100kb saved in <1s) I will be assigning it to a button on the ribbon with a better naming convention for the files it creates.