Description

When trying to register the ProjectDox DLL files from the ProjectDox Control Panel, the first three DLLs register successfully but on the fourth an error message is received saying "The module E:\ProjectDox\bin\CDLServiceWrapper.ocx".The reason that the error message is received is because the file can not be found in the \ProjectDox\bin folder.

Solution

To correct the issue, navigate to the \ProjectDox\bin folder and unzip the MSVCR71.ZIP file into the \ProjectDox\bin folder and then try to run the "Register COM" task again from the ProjectDox Control Panel.  You should not see an error this time and instead you should receive a success message for each of the DLLs being registered.

Revised 02-18-2015

 
The information below is to provide general information regarding adding an additional storage location to ProjectDox and does not provide step by step instructions.

ProjectDox is flexible and can store the UserFilesPublish and UserFilesSource shared folders across multiple storage devices. For example, current storage location may be \\Server1\UserFilesSource and \\Server1\UserFilesPublish and that location fills up. The files uploaded to ProjectDox to date would have those paths stored in the database so the application knows where to access them when being worked with by a user logged into ProjectDox.

Since storage location 1 is filled up, additional file shares can be created with the same NTFS permissions and File Share permissions on the new storage device, \\Server2\UserFilesSource2 and \\Server2\UserFilesPublish2.  A copy of the web.config file that is located at the root of the directory of the original storage location \\Server1\UserFilesPublish needs to be place at the root of the new storage location \\Server2\UserFilesPublish2.   Then you would add storage location 2 into the ProjectDox configuration.  In order to use the new storage location 2, we would modify the ProjectDox Admin / Configuration / Core tab and set the path for the new UserFilesSource and UserFilesPublish folders that way any Projects created with files uploaded from that point on would be stored in the new location.

We would then add an additional Virtual Folder / Application in IIS configuration and call it UserFilesPublish2 and point it to storage location 2. The last step would be to update the UserFilesPublish virtual folder name field under the ProjectDox Admin / Configuration / Core tab to the new Application name of UserFilesPublish2.

With all of those changes applied, any new Projects that are created will have their storage location setup for storage location 2 and so as files are uploaded the path in the database will be pointed to the correct location for the files. Since both locations are setup in IIS, when a user clicks on a file to view, either path is obtained from the database and the user can be taken to both successfully.

It is actually beneficial to spread the shared folders among several locations on different physical devices so there is not so much load being placed on a single device. If your ProjectDox site has a large number of users, having the requests be distributed to multiple devices can speed up the performance so you do not have the situation where there is a bottleneck waiting for the return from a single physical device.

For questions regarding additional storage locations or to schedule time to have assistance in performing the steps outlined above, please contact Avolve Support or your Account Manager.
 

When encountering this problem, we have found that the issue could be a setting on your Firewall, which limits large uploads into your network. To correct this, check the Firewall settings and ensure that there is not a limitation on the size of files being transmitted across the Firewall into your network? Some of the settings that you may want to look for would be "tcp-mss-sender" for outbound traffic and "tcp-mss-receiver" for inbound traffic. The values for those settings controls the maximum amount of data that can be sent in a single packet, and can sometimes be troublesome when transmitting large files.