Issue exchanging excel file from Excel 64 bits to Excel 32 bits

Hi,

In a xlsm file, I've created a Userform with a WindowsMediaPlayer object.

If I send this file, which has been created on a Excel 32 bits, to a colleague with a Excel 64 bits : no problem, he can open and read the file.

If my colleague "saves as" this file on his PC and send it back to me, I get the following error message just after the warning dialog window about ActiveX :

&H80004005 (-2147467259)

If I remove the WMP object in the Userform and perform the same process, no problem I can read the file when it has been sent back to me.

Any explanation ?

I tried already all the solutions about removing Complements / Add ins etc.

Thank you for your help.

August 12th, 2015 11:18am

Hi SsvoKp,

Based on your error message >>&H80004005 (-2147467259)<<, this may be followed by these error messages:
Out of memory
Run-time error 7. Could not find the specified object.

You can refer to this KB article about this error message:
https://support.microsoft.com/en-us/kb/230888

You also said this issue appeared when exchanging excel file from 64bit to 32bit.

If your file is large or contains a large amount of features, it is possible you are running low on available memory resources. If you work with extremely large data sets, the 64-bit version of Office may perform better for you. 32-bit office you run are limited to making use of only 2GB of RAM.

I suppose this might be the reason of your issue, about the difference between 64bit and 32bit please refer to this article:
https://support.office.com/en-sg/article/Choose-the-32-bit-or-64-bit-version-of-Office-2dee7807-8f95-4d0c-b5fe-6c6f49b8d261?ui=en-US&rs=en-SG&ad=SG

Hope it's helpful.

Regards,

Emi Zhang
TechNet Community Su

Free Windows Admin Tool Kit Click here and download it now
August 13th, 2015 1:32am

Dear Emi,

Thank you for your quick and detailed answer.

In my case the error message is followed by "Out of memory".
I confirm that the symptoms of my bug are described in your article : kb/230888. Maybe you could extend the range of concerned products to OFFICE 2003, 2007? 2010 and 2013 because in the article they say that is for OFFICE 2000.

Regarding the cause, I know that the purpose of 64 bits is to allow the user to manipulate bigger files in RAM than with 32 bits, but that does not explain why the same file saved with Excel 64 bits (without any modification except "save as") can run later "out of memory" with the Excel 32 bits. Would it be possible to send you the initial file (32bits) (830 Ko) and the corrupted file (64bits) (844 Ko) ?

Best regards,

Sbastien Savarino




  • Edited by SsvoKp 1 hour 5 minutes ago
August 13th, 2015 2:24am

Hi SsovKp,

Yes, you can send initial files to our email address:
ibsofc@microsoft.com
Please Note: Please add the URL of the case in the email subject or body.

The KB 230888, maybe I didn't explain clearly. My purpose is to let you know, based on the first error message it maybe followed other error messages. :D

Based on the error message, I found 2 KB articles about it. One is KB 230888, and another one is KB 223152.
https://support.microsoft.com/en-us/kb/223152

On the other hand, your issue also is a startup problem, I provide a link about how to fix start problem as a reference:
http://www.jkp-ads.com/Articles/StartupProblems.asp

Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

Please try these methods and check if they work for you.

When you send files to our email address, I will also help you to check them.

Any updates please let me know, I'm glad to help and follow up your reply.

Regards,

Emi Zhang
TechNet Community Su

Free Windows Admin Tool Kit Click here and download it now
August 13th, 2015 4:52am

Dear Emi,

Thank you for your quick and detailed answer.

In my case the error message is followed by "Out of memory".
I confirm that the symptoms of my bug are described in your article : kb/230888. Maybe you could extend the range of concerned products to OFFICE 2003, 2007? 2010 and 2013 because in the article they say that is for OFFICE 2000.

Regarding the cause, I know that the purpose of 64 bits is to allow the user to manipulate bigger files in RAM than with 32 bits, but that does not explain why the same file saved with Excel 64 bits (without any modification except "save as") can run later "out of memory" with the Excel 32 bits. Would it be possible to send you the initial file (32bits) (830 Ko) and the corrupted file (64bits) (844 Ko) ?

Best regards,

Sbastien Savarino




  • Edited by SsvoKp Thursday, August 13, 2015 6:25 AM
August 13th, 2015 6:22am

Dear Emi,

Thank you for your quick and detailed answer.

In my case the error message is followed by "Out of memory".
I confirm that the symptoms of my bug are described in your article : kb/230888. Maybe you could extend the range of concerned products to OFFICE 2003, 2007? 2010 and 2013 because in the article they say that is for OFFICE 2000.

Regarding the cause, I know that the purpose of 64 bits is to allow the user to manipulate bigger files in RAM than with 32 bits, but that does not explain why the same file saved with Excel 64 bits (without any modification except "save as") can run later "out of memory" with the Excel 32 bits. Would it be possible to send you the initial file (32bits) (830 Ko) and the corrupted file (64bits) (844 Ko) ?

Best regards,

Sbastien Savarino




  • Edited by SsvoKp Thursday, August 13, 2015 6:25 AM
Free Windows Admin Tool Kit Click here and download it now
August 13th, 2015 6:22am

Hi Emi,

I didn't get any news from the file I sent to you few weeks ago. So I cannot yet accept your suggestion as answer to my issue.

Thanks again for your support.

Regards,

Sbastien

September 8th, 2015 3:38am

i find that when I link objects from a 64-bit subsystem (office 64-bit) they cannot see 32-bit objects. the most prevalent example of this I can think of is using an ODBC connection with office. you can't connect a 64-bit Excel Application to a 32-Bit ODBC connector because they work in different "environments".

Perhaps the issue is that you are accessing a 64-bit Active-x control and that it is not present in the 32-bit subsystem. 

I would try to standardize on one or the other, I generally keep the office installs at 32-bit as you can run 32-bit on a 64-bit OS but not vice-versa.

 
Free Windows Admin Tool Kit Click here and download it now
September 9th, 2015 1:27am

Thanks Michael.

WHile I don't get a clear answer from Microsoft, I standardize on 32 bits OS. It is a temporary solution as I can not ask my clients to switch from 64 to 32.

I just remind you that I create the file in 32 bits environment, then I save it (without changes) in 64-bits environment then I send it to 32 bits environment and then it doesn't work anymore. I don't add any 64 bits component in between.

Regards,

Sbastien

September 9th, 2015 6:43pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics