Help with Sims Individual reports

[Demerton]

Thanks for this suggestion. we have our support for SIMS through our local council, and I had never come across this routine, I will run it at half term and see what happens.

 

Again Many Thanks

 

John

We have done this as part of normal keeping procedure, our doc storage is approx 2GB

 

It would for me now on all machines, but not the admin users - reset CC4 profile, removed appdata folders and cleared cached profiles in all instances.

 

SIMS are now closing the call, indicating they don't know how to fix it... or what is wrong..... RM have stated that there are no issues, as expected, SIMS are saying the same.

 

Works on my CC4 PC and also a vanilla PC under my login, juts no one else.

 

I will keep testing is suppose.

[calwyn]

Hi everyone.

 

Just wondering is anyone ever found a solution to this issue. I am experiencing it with certain users, but not others... unfortunately the one person who really needs to be able to run this report is effected.

[calwyn]

Right...

 

Having had a play with this yesterday, I compared the users policies of those who this report works for and those that it doesn't. One thing that stood out between the two was that Macros were restricted on the users that didn't work. I changed this and now the report seems to work.

 

Calwyn

[Edgehill]

Right...

 

Having had a play with this yesterday, I compared the users policies of those who this report works for and those that it doesn't. One thing that stood out between the two was that Macros were restricted on the users that didn't work. I changed this and now the report seems to work.

 

Calwyn

Out of interest what settings did you change to get around this?

We have the same issue for all users. I've tried setting the following via GPO with no luck; Enable all macros, Trust access to VBA project object model and adding "%TEMP%" as a trusted location.

Any help would be greatly appreciated.

[Techie98]

Did you ever get anywhere with this?

[Edgehill]

No, unfortunately I'm still having no luck with this.

Out of interest are other people who are getting this running RM networks or vanilla windows?

[calwyn]

Hi

 

Yes, I'm running on an RM network

[JAYC]

We are finally making some progress with this! We have 5 schools with the issue, all RM CC4, Windows 10, Word 2016. The problem appears to be with Macro security settings. At the moment we can only run the reports with absolutely all macro security turned off in Word. We are now rebuilding the machine, to start trying to work out which setting is key to the issue... I'll post again when we know more

[Edgehill]

We are finally making some progress with this! We have 5 schools with the issue, all RM CC4, Windows 10, Word 2016. The problem appears to be with Macro security settings. At the moment we can only run the reports with absolutely all macro security turned off in Word. We are now rebuilding the machine, to start trying to work out which setting is key to the issue... I'll post again when we know more

 

Strange, the macro theory doesn’t fit what I’ve seen.

I’ve joined a raw windows 10 PC to our domain and checked the same GPOs are applying, in this case the report runs fine opening but the template shows “Macros are disabled”.

It’s the same for our 2012 R2 RDSH (non CC4) server, template shows “Macros are disabled” but report runs fine.

Furthermore I have successfully replicated the issue on Win 8.1 (with office 2016) and Windows 10 with office 2010.

 

I have also found that sometimes after changing various settings the report will run fine for the first attempt but will fail on a second attempt or after closing and reopening SIMS (and rerunning the report).

So it sometimes looks like changes have resolved the issue, but on repeat testing the issue persists.

[JAYC]

We are back to the drawing board too After a rebuild, disabling macros did not fix the issue

[Techie98]

I’ve still got nowhere, I assume this is the same for everyone else? Capita just brush you off.

[Edgehill]

I’ve still got nowhere, I assume this is the same for everyone else? Capita just brush you off.

 

Unfortunately I haven't been able to get anywhere with this either. From what I've seen the issue is RM based so I wouldn't expect Capita would be able to provide any guidance on this.

 

Since my last update I tried removing all RM packages from a workstation and this seemed to stop the issue form occurring, but I was unable to pinpoint the issue to a particular package as the issue reoccurred at different times each time I started putting packages back on.