[sims] Report Error Could not open Macro Storage [SOLVED]

[linkazoid]

Hi All,

 

Our behaviour officer is unable to run a report that she has created. When the report is run, she is prompted with the following error. "Error. Could not open macro storage." This used to work OK. We're on the Latest SIMS with Office 2013.

 

Someone here has called Capita and we've been told to tick and allow all the options in Protected View. I'm not comfortable to just allow all the options and this IMO is bad advise for the Support Desk to give out.

 

Does anyone know what Protected View GPO would be causing this? My GoogleFu didn't bring up much.

 

Regards,

 

Michael

[LosOjos]

Not seen the error but it might help you diagnose it if you edit the report's template.

 

I'm assuming it's an Excel report, so it'll either be using the default template (Program Files\SIMS\SIMS .net\ExcelStandardList.xls) or a custom one - you'll need to find who has the original template if that's the case.

 

Open up the template, go to the Auto_Open sub routine and comment out the line beginning 'On Error'. Save the template with a new name, then in SIMS report designer, choose "User defined template" on the output page and select the template copy you just saved.

 

Now, when the report is run, you'll get the default VBA error box with a 'debug' button, press that and it'll show you exactly which line the error occurs on, which should give some clue as to why it's failing.

 

[This is from memory so I apologize if the menu routes/boxes aren't labelled exactly as described, should be enough for you to find it though]

[linkazoid]

Thanks for your reply.

 

It's a Word List report and seems to run OK for me. I think it's because its trying to create the file in the Appdata Temp folder.

 

Now I know where it's saving I can look at the GPO's again for protected view.

 

Thanks,

 

Michael

[linkazoid]

After calling Capita Support Desk and hearing the response that they gave to the the other member of staff I tried what they suggested. Changing the protected view settings did not resolve the issue.

 

The cause of this problem was a GPO Word 2013 File Block Setting. We had configured Word 97 binary documents and templates to enabled and "Allow editing and open in Protected View". Changing this to "Do not block" has fixed the problem.

 

Hopefully this helps someone else who encounters this problem.

 

Michael

 

[Can a mod please mark this as Solved]

Edited March 17, 2015 by linkazoid

[LosOjos]

After calling Capita Support Desk and hearing the response that they gave to the the other member of staff I tried what they suggested. Changing the protected view settings did not resolve the issue.

 

The cause of this problem was a GPO Word 2013 File Block Setting. We had configured Word 97 binary documents and templates to enabled and "Allow editing and open in Protected View". Changing this to "Do not block" has fixed the problem.

 

Hopefully this helps someone else who encounters this problem.

 

Michael

 

[Can a mod please mark this as Solved]

 

Thanks for taking the time to report back the solution - no doubt someone else will eventually stumble on this post and it'll save them the hassle you had!

[vikpaw]

After calling Capita Support Desk and hearing the response that they gave to the the other member of staff I tried what they suggested. Changing the protected view settings did not resolve the issue.

 

The cause of this problem was a GPO Word 2013 File Block Setting. We had configured Word 97 binary documents and templates to enabled and "Allow editing and open in Protected View". Changing this to "Do not block" has fixed the problem.

 

Hopefully this helps someone else who encounters this problem.

 

Michael

 

[Can a mod please mark this as Solved]

 

will do - and thanks for the solution.