32809-Application-defined or object-defined error

[marco_groenendijk]

Two users within my usergroup have a problem running specific EVDRE input schedule that have been working for a long time (for them as well). The error is as per title of this question (or similar, just with a different number in front). The schedules work fine for other users and one of the users tried using the schedule on a different PC and there it works fine for her. So from that I sort of conclude it is not a specific BPC error (we are on BPC 7.5 MS, version 7.5.108.02) but probably more an excel issue. I am just wondering if someone on this forum has had a similar issue and has found out the way to correct for this.

Regards,

Marco

[JohnL]

Hi Marco,

Does the user have the MS security updates mentioned in Note

2107965 - Issues in EPM Add-in / BPC for Excel after installing Microsoft updates

Thanks,

[marco_groenendijk]

Hi John,

I followed the link but seem to have a problem accessing the SAP marketplace. Is this regarding the Microsoft update by the end of last year which impacted macros and made buttons not work anymore in excel? If so, then yes, we did have this update and the build in buttons in our EVDRE did no longer work. But the users followed the below fix which seemed to solve the issue for all of them and buttons now work again.

However, if my current issue could also be caused by this as well what would be the fix be for this?

To fix it, do this:

1.        Close all Office applications.

2.        Do a search in Windows Explorer – make sure to include hidden and system files and folders – for *.exd files (note: that’s not *.exe !!) and delete any you find.
Make sure you get these:
C:\users\username\AppData\Local\Temp\Excel8.0\MSForms.exd
C:\users\username\AppData\Local\Temp\VBE\MSForms.exd

3.        Reboot the computer (this is not always necessary, but probably better safe than sorry)

4.        Restart your Office apps and test the controls again.

Please note that the .exd files will be recreated when you next use a workbook with an embedded active control – this is quite normal and should not cause you a problem!

[Former Member]

Hi Marco

Did you solve this ?

We also have the problem with a number of users having error 32809 after seemingly nothing being changed!

We had the problems with Windows update but these were 'solved' last month.

Happens for a random number of machines

Thanks

Ian

[former_member186498]

Hi Marco and Ian,

have you a lot of fixed values in memberset of your report? If so please read this note 1915176 - How to configure MemberSet cell to create EVDRE report with big volume of fixed members -...

Regards

     Roberto

[marco_groenendijk]

Hi Roberto,

not really. One of the users that has the problem has it with the an input schedule that expends 1 column based on a property in the dimension and 1 row based on an account hierarchy where 2 accounts are excluded (see below).

PARAMETER     EXPANSION 1               EXPANSION 2

ExpandIn             COL                            ROW

Dimension          ACCTDETAIL                ACCOUNT

MemberSet       SL_SCHED_INPUT="Y"  BAS(IE_SL) AND ID<>"SL101A" AND ID<>"SL226A" AND                                                      ID<>"SL330A"

I do think it has something to do with excel more than with BPC as the same user can use the input schedule without problems on another laptop. We did apply the fix for the microsoft update as I mentioned above. However, looking at the link John provided there are some other options to follow so I will have to have a go at those (and also think the note mentioned 3 .exd files to be deleted where we only did 2).

[Former Member]

Hi Marco

We made some progress on this yesterday.  To explain our problem..

60% of our worldwide users had the MS update problem.  These were all fixed with the MISFixit file supplied by Microsoft.

Our Input Schedules were changed and saved by a client with a 'fixed' machine.  This Input Schedule was then found to not work on machines who had not received the patch and subsequently been fixed!  The error was 32809.  Weird.

We tried deleting the msforms.exd in the following temp folders:

c:\users\username\appdata\local\temp\excel8.0

c:\users\username\appdata\local\temp\vbe

(Remember the above are likely to be hidden so you may have to type the folder in the address bar)

Deleting the files did not work!

However, we did find a solution.  Collect the msforms.exd files from a PC where the problem does not exist and replace these files on the machine where the problem exists.  The working PC will have had the windows problematic patch and fix applied.

Bingo!

If anyone can explain why this might be causing a problem then do reply to this threat.  It's clearly VB related in some way.