But it works on my PC!

The random thoughts of Richard Fennell on technology and software development

Error –4002 on Access services on Sharepoint 2010

We have had an internal timesheeting system written in Access services running without any problems for the past through months. At the end of last week, when people tried to submit their timesheets they started getting a -4002 error saying the macro (that saves the weekly sheet) could not be started.

Checking the server event logs, Sharepoint logs and Access services log tables showed nothing. So as all good IT staff do we tried the traditional IISRESET command (on both our Sharepoint web servers) and it all leapt back into life. The only change on our server in the past week has been been the ASP.NET security fix, and associated reboot, but I cannot see why this should effect Access Services, it looked as if it had basically Access services just failed to restart fully after the server reboot.

One to keep an eye on.

Comments (4) -

  • richard

    10/20/2012 5:06:51 PM |

    We saw this problem again after applying SharePoint 2010 SP1 to our farm. We could add rows to the various tables in the Access Services site, but could run no macros, getting the -4002 errors

    Restarting the servers and redeploying the Access site did not fix this, also we could repeat the same problem with a brand new Access test project.

    The solution in the end was to recreate the Access Services application within the farm. Once this was done Access services worked as expected again.

  • Tomas

    12/5/2012 7:50:10 AM |

    Hi there,

    it can the problem in workflow configuration settings http://support.microsoft.com/kb/2674684.
    Applies to multi-server SharePoint farm.
    Access data macros are executed as SPD workflows inside SharePoint.

    These commands did the trick for us.
    $webapp = Get-SPWebApplication -identity https://webapplication
    $webapp.UpdateWorkflowConfigurationSettings()

    I also recommend to start Web Application Service and Workflow Timer Service together only on the servers - web front-ends. Never independently. Otherwise other problems arise.

  • Tomas

    12/5/2012 7:50:27 AM |

    Hi there,

    it can the problem in workflow configuration settings http://support.microsoft.com/kb/2674684.
    Applies to multi-server SharePoint farm.
    Access data macros are executed as SPD workflows inside SharePoint.

    These commands did the trick for us.
    $webapp = Get-SPWebApplication -identity https://webapplication
    $webapp.UpdateWorkflowConfigurationSettings()

    I also recommend to start Web Application Service and Workflow Timer Service together only on the servers - web front-ends. Never independently. Otherwise other problems arise.

  • Tomas

    12/5/2012 7:50:39 AM |

    Hi there,

    it can the problem in workflow configuration settings http://support.microsoft.com/kb/2674684.
    Applies to multi-server SharePoint farm.
    Access data macros are executed as SPD workflows inside SharePoint.

    These commands did the trick for us.
    $webapp = Get-SPWebApplication -identity https://webapplication
    $webapp.UpdateWorkflowConfigurationSettings()

    I also recommend to start Web Application Service and Workflow Timer Service together only on the servers - web front-ends. Never independently. Otherwise other problems arise.

Pingbacks and trackbacks (1)+

Comments are closed