Can t find dll entry point getuserdefaultlcid in kernel32

ngphongPosts: 7Joined: Thu Jun 22, 2017 5:17 pmOLAP Product: TM1Version: 10.2.2Excel Version: 365

Can't Find DLL entry point LoadLibraryA in Kernel32.dll

Hi:
I am installing TM1 Perspectives. When I do the Excel Add-in, after I map the IBM Cognos TM1 Perspectives (in the Excel Add-ins window) to tm1p.xla file, I got the message "can't find DLL entry point LoadLibraryA in Kernel32.dll". The TM1 Add-in does not show in Excel. I tried deleting and re-installed both Excel 365 (32-bit) and TM1 (10.2.2) a couple times, but the problem still there. This is the first time I see such issue. Has anyone run into this issue before?

Re: Can't Find DLL entry point LoadLibraryA in Kernel32.dll

Post by paulsimon » Tue Nov 28, 2017 9:34 pm

Hi

Did you by any chance select the option to copy the AddIn to the AddIns folder? This might be causing the error since all DLLs related to the TM1P.XLA need to be in the same folder.

Regards

Paul Simon

ngphongPosts: 7Joined: Thu Jun 22, 2017 5:17 pmOLAP Product: TM1Version: 10.2.2Excel Version: 365

Re: Can't Find DLL entry point LoadLibraryA in Kernel32.dll

Post by ngphong » Tue Nov 28, 2017 11:02 pm

Thanks. I see some add-ins subfolder under the Addins folder that you referenced, i.e. Power Map Excel Add-in, Power View Excel Add-in, PowerPivot Excel Add-in. Under each of those folders, there are verious .DLL files. I am not good enough to understand what are those .DLL files are for, and how are they related to the TM1P.XLA file.

Do you think I should try to re-install Excel and watch out for the option to copy the addins to the Addin folder?

Thanks,
Phong Nguyen

MichaelGlinskiPosts: 4Joined: Fri Jun 08, 2012 7:27 pmOLAP Product: TM1Version: 10.2.2+Excel Version: 2010-2016

Re: Can't Find DLL entry point LoadLibraryA in Kernel32.dll

Post by MichaelGlinski » Wed Aug 15, 2018 7:23 pm

FYI, in case anyone else runs into this error message in the future...

The exact error message discussed in this thread was being returned when a user tried running Perspectives on their machine. We tried reinstalling Perspectives, reinstalling Excel, re-registering DLLs, copying DLLs to Excel's ADDINS folder... all with no success.

It turns out the problem was that the user was on a network with a company-wide security policy to blacklist macros unless a specific .xla or .xlam file was whitelisted. These blacklists/whitelists even overrode any security settings we made in Excel, so while we thought we were allowing or telling Excel to notify us of macros via settings in Excel, we really weren't. The company-wide security policy overrode any configurations we made in Excel and prevented tm1p.xla from calling macros in a manner that resulted in the "Can't find DLL entry point LoadLibraryA in Kernel32.dll" message, which isn't typically what you see when macros are disabled.

After having a domain administrator whitelist "(user machine's name)\Program Files (x86)\ibm\cognos\tm1\bin\tm1p.xla", everything worked flawlessly.

I figured it would be worth posting some closure in this thread, since this error message isn't typically what you see when macros are being blocked and the previously described solution didn't work for me.

Kernel32.dll is considered a type of Dynamic Link Library (DLL) file. Dynamic Link Library files, like kernel32.dll, are essentially a "guide book" that stores information and instructions for executable (EXE) files - like HelpPane.exe - to follow. These files were created so that multiple programs (eg. Microsoft Office Access 2010) could share the same kernel32.dll file, saving valuable memory allocation, therefore making your computer run more efficiently.

Unfortunately, what makes DLL files so convenient and efficient, also makes them extremely vulnerable to problems. If something happens to a shared DLL file, either it goes missing or gets corrupted in some way, it can generate a "runtime" error message. Runtime is pretty self-explanatory; it means that these errors are triggered when kernel32.dll is attempted to be loaded either when Microsoft Office Access 2010 is starting up, or in some cases already running. Some of the most common kernel32.dll errors include:

• Access Violation at address - kernel32.dll.
• Kernel32.dll could not be found.
• Cannot find C:\Windows\SysWOW64\kernel32.dll.
• Cannot register kernel32.dll.
• Cannot start Microsoft Office Access 2010. A required component is missing: kernel32.dll. Please install Microsoft Office Access 2010 again.
• Failed to load kernel32.dll.
• The application has failed to start because kernel32.dll was not found.
• The file kernel32.dll is missing or corrupt.
• This application failed to start because kernel32.dll was not found. Re-installing the application may fix this problem.

Your kernel32.dll file could be missing due to accidental deletion, uninstalled as a shared file of another program (shared with Microsoft Office Access 2010), or deleted by a malware infection. Furthermore, kernel32.dll file corruption could be caused from a power outage when loading Microsoft Office Access 2010, system crash while loading kernel32.dll, bad sectors on your storage media (usually your primary hard drive), or quite commonly, a malware infection. Thus, it's critical to make sure your anti-virus is kept up-to-date and scanning regularly.