Timeout (30000 milliseconds) waiting for a transaction response from the ‘ServiceName’ service.
A timeout was reached (30000 milliseconds) while waiting for the ‘ServiceName’ service to connect.
The ‘ServiceName’ service failed to start due to the following error:
‘The service did not respond to the start or control request in a timely fashion.’
Here is what to do:
- Click Start, click Run, type regedit, then click OK.
- Locate then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
- In the right pane, locate the ServicesPipeTimeout entry.
Note: If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:
- On the Edit menu, point to New, then click DWORD Value.
- Type ServicesPipeTimeout, and press ENTER.
- Right-click ServicesPipeTimeout, then click Modify.
- Click Decimal, type 360000, then click OK.
This value represents the time in milliseconds before a service times out.
- Restart the computer.
Do not use your SharePoint databases as the database for SPDocKit. When configuring SPDocKit, you should always create a new database that is dedicated for SPDocKit.
Note: If there is an existing SPDocKit database you can connect to it.
If you choose “run only”, the following features will not be available:
- Permissions Explorer
- Queries and Rules
You can install SPDocKit on a workstation and generate documentation from it, but to gather data you will still need to run or install the tool on the actual SharePoint server. SPDocKit needs to be installed on the SharePoint server to load the data because there aren’t any APIs to retrieve from workstations.
The application is easy to install — the Installation Wizard will guide you through it. If you need help with the deployment please contact us so we can provide you with adequate support.
Yes, you can do that via the SPDocKit Configuration Wizard by navigating to: File > Configuration > Configure.
Bare installation takes around 30MB of disk space, but additional disk space will be required for farm snapshots and saved farms. A typical farm snapshot is a ~50KB file.
SPDocKit uses an SHA256 application signing certificate which Windows Server 2003 Service Pack 2 does not support by default. Here is an article that will help you resolve this issue: http://blogs.technet.com/b/pki/archive/2010/09/30/sha2-and-windows.aspx.
Make sure you install both KB 938397 and KB 968730.