Here is the link for the offline update.
Click the Generate button. Download all of the files, copy them to the server that has no internet access and overwrite the existing files (default location: %ProgramData%\SPDocKit\Settings).
After you copy these files to the installation folder please restart the application in order to apply the changes.
This is the issue on servers that don’t have access to the Internet. The Windows server will try to check the code signing certificate that was used to sign the application executables. Allow access to the Internet for the server, then start the service and the issue is solved. Please note that you need to do this only once—the first time Windows will check the Acceleratio code signing certificate and from then on it will work fine.
If this is not possible contact us and we will provide you with a certificate and instructions on how to import it to your problematic server.
SPDocKit uses WMI which connects over RPC to fetch information about the servers configuration. This information is displayed in the Farm Explorer -> Servers List (disk, processor, memory). This requires that the RPC service is running on the remote machine and as well that the following inbound rule is enabled in the firewall to allow connections: RPC TCP 135 (COM+ network access (DCOM-IN))
When I tried to load a SharePoint farm with the SPDocKit I received the following error:
This product cannot be activated because this is not a SharePoint Server or you do not have the right privileges to access theSharePoint Farm. Check if SharePoint is installed or contact your administrator.
- The product needs to run on the same server as SharePoint, so make sure SharePoint is installed on the server where you are trying to load the farm.
- In order to load the SharePoint farm you need to have the proper privileges. Check this article for more details.
You might encounter the following error if you are upgrading to the latest version of the application:
Error 1001. An exception occurred while uninstalling. The exception will be ignored and the uninstall will continue. However the application might not be fully uninstalled after the uninstall is complete. -> The specified service does not exists as an installed service.
When this error occurs you are not able to start the application and you cannot Remove/Repair it from Control Panel > Programs.
The installation was not able to remove the Windows service. The existing installation needs to be repaired then removed before you can proceed with the upgrade.
Here is what you need to do:
- Obtain the original MSI file you used to install the product (product version e.g. 1.0.3 is listed in Control Panel > Programs, but you can contact us to obtain the original installation).
- Right-click the MSI file and choose Repair to repair the application.
- Use Control Panel > Programs to uninstall the application.
- Once uninstalled, you can install the latest version as planned.
During this procedure you might get the “Service Marked for Deletion” error message. In such a case, make sure the Services dialog box is not running (Control Panel > Administrative Tools > Services). If the dialog box is not running you will have to restart your computer before proceeding to the next step.
The account on which I have installed the SPDocKit has permissions to run it, but two other accounts receive errors when trying to load the farm with all the webapps. The users have both farm administrator and local administrator rights. The problem occurs on SharePoint 2007.
The user account that you use to log on to the web server is not a member of either of the following roles:
- the Security Administrator role on the SQL server
- the Database Creator role on the SQL server.
For more information please see this article.
The application will work on both the console and the Remote Desktop session.
- Locate the application installation directory in Program files and find the SPDocKit.exe file (usually: C:\Program files\Acceleratio\SPDocKit).
- Create a shortcut for that file on the desktop.
- To execute the application, right-click the shortcut then choose Run as the administrator.
- The UAC dialog box will be shown and you will be prompted to run the application as the administrator.
- Click Yes and SPDocKit will run without any issues.
Please note: You must create a shortcut that points directly to the file in the application directory, and not to the file in the Start menu.
When trying to upgrade to the latest version of SPDocKit you might receive an error:
The specified service already exists.
The previous version has not been removed correctly. Here is what you need to do:
- Go to Add/Remove programs and uninstall the SPDocKit manually (if the product is not listed, you do not have the proper privileges or somebody else installed the application, e.g. an Administrator user, so logon as the user who initially installed the application then remove it).
- Once the program has been removed you can restart the new installation you have downloaded and install the application.
In case you encounter a similar error again, try the following:
Stop the SPDocKit Service in the services MMC console, then open the Command Prompt and type in the following to delete the service:
sc delete SPDocKitService
The service will be reinstalled with the new installation.
We have an internal list of SQL server and SharePoint product versions so that we can match build numbers to description. For example, if your SQL server build number is 10.50.1765.0, you will see “SQL Server 2008 R2 CU6, 21 Feb 2011” in your reports.
If the warning appears as in SPDocKit (as you can see in the picture below), you can click the Update button and it will just get the data from our server if you have Internet access on your servers.
In order to install SPDocKit on a Windows server you will have to run it with administrative privileges.
If you have a firewall between the server hosting the application and the servers that are being monitored you need to have the following ports open (In brackets are the rule names in Windows Server 2008):
- All ports from 49152 and above should be open – during the IIS load we use Microsoft component that utilize dynamic ports and that is the main reason why we require to open these ports on firewall. Read more
- Inbound rules on Windows Server 2008, 2008 R2, 2012 and 2012 R2 are (this is inside the windows firewall):
- File and printer sharing (NB-Session-In)
- Network Discovery (NB-Name-In)
- Network Discovery (NB-Datagram-In)
- COM+ Remote Administration (DCOM-In)
- In case you have the third party firewall the ports are:
- RPC TCP 135
- NetBIOS Datagram Service UDP 138
- NetBIOS Name Resolution UDP 137
- NetBIOS Session Service TCP 139