>This page is being updated>> please check back later or send a ticket to support for immediate assistance with networking

We recommend reviewing all the information before starting. Consult with 3D support if you have any questions.

Note: If a workstation is already connecting to the database running locally on the workstation rather than the database located on your server, you or your network administrator will need to use report writer Preferences > Preferences, File Locations folder to Open the user and temporary files folder. Cancel out of preferences and close the program. Then delete the config.ini file there to reset the connection. Then when launching 3D, the wizard should appear again, allowing selection of “Connect to local or network SQL” > “Connect to a database” > “The database is On Another Computer”, entering the appropriate computer name and connection information to access the database stored on the server machine. Afterward the workstation data folder may be adjusted to point to the shared data folder per the above link information.

LICENSING: When installing 3D desktop software on additional computers, please verify with 3D Inspection Systems that appropriate licensing has been obtained or arrange to purchase additional licensing seats. The server/host machine for the data (regular computer or server) will use one license seat, and each additional client/workstation computer with 3D Inspection System software installed will use a license seat. A separate file server containing only shared reports via a mapped drive connection that does not have 3D installed does not require a license seat. 3D Inspection Systems reserves the right to deny future support, activations, or other services or revoke licensing (or pursue other legal actions) where users fail to purchase appropriate licensing for additional computers in compliance with the EULA,

HARDWARE: Please verify the server and networked computers on which 3D Inspection System is to be installed meets current System Requirements.

Your personal qualified network administrator should be consulted for assistance with setup and general connecting of computers on your actual network. Your IT may submit a ticket to 3D support directly for assistance on your behalf. Since every network is different, 3D Inspection Systems cannot directly assist with the actual networking of the computers or troubleshooting network settings. In some cases, IT may need to temporarily elevate rights on the profile to be used on each computer to install and initially set up the software.

One installation of the 3D Inspection System software must be installed on the host/server computer, and on each client/workstation where it will be used. Full backups of your data that include the Office Management information can only be made from the host/server machine using its local connection to the SQL database. Backups made from a connected client/workstation machine may be made, but will be missing this important data and may display this type of message.

Backups may also be missing data (but no message will occur) if the data folder has not been properly networked to be shared in common.

STEP A- HOST/SERVER SETUP:

Use the appropriate scenario steps below to set up the host/server computer.

A1. New Installation (new setup of 3D Inspection System software for a business):

1. Install 3D desktop software on the server, launch, and activate as appropriate. IT or other parties may choose Activate Later to defer activation and continue with setup, allowing the registered user to actually activate later.
2. launch 3D Inspection System and use Welcome Wizard to set up a new company database. Note: Users may later adjust company and inspector information using Maintain options in Office Management.
3. Note: The default data folder location is normally \Documents\3D Inspection System 11\  You will need to share this folder with the other client/workstation computers on the network that will be running the 3D Inspection System software.. If you wish to change the location of this folder or relocate it to a separate file server, this may be done by (a) copying the folder to another drive letter accessible location, (b) using 3D Inspection System Actions pane to switch to the Report Writer, then use Preferences > Preferences, File locations tab Location of data files to change the Data folder location (use the meatballs menu to select new location), (c) close and reopen 3D.
4. Allow data folder location in #3 to be shared with other computers on the network.
5. Go to Step B1 to setup and connect client/workstation machines to the 3D host/server data.
6. Note that periodically a backup should be made from 3D Inspection System launched on the server machine using File > Backup All Files to create a complete backup with which the 3D support team is able to assist. We recommend verifying the 3dbackup .zip files can be opened and store them safely off the drive. If you choose to backup SQL and data files by other means, 3D support may or may not be able to offer assistance with those items.

A2. Upgrading prior 3D version 12 series to newer 3D version for Existing Installation:

1. Launch existing 3D software and use File > Backup All Files to create a fresh backup of all the data. If any issue is experienced during backup, please contact 3D support. We recommend opening the 3dbackup .zip files after they are made to confirm the files are good.
2. Uninstall the prior version of 3D from Windows Apps and Features.
3. Install the new version of 3D Inspection System.
4. Launch 3D to verify the program reopens without issue. If database migration or updating is needed, initial launch may take slightly longer as it completes the process.
5. Go to Step B2 to update the workstations to the same version and reconnect to the SQL data if needed.

A3. Moving from an old Host/Server to a new Host/Server:

1. Launch existing 3D software and use File > Backup All Files to create a fresh backup of all the data. If any issue is experienced during backup, or if the backup creates multiple 3dbackup .zip files for the backup date, please contact support for advice.
2. Install the 3D software on new Host/Server. Choose Activate Later to continue for now.
3. Initially use Welcome Wizard to set up a new company database. You may enter minimal information like only company and inspector name as this data will not be kept.
4. Transfer the 3dbackup.zip made in step 1 to the new computer and use Office Management, use File > Restore from Backup to select and restore the 3dbackup file items.
5. Go to Step B3 to update the workstations and connect them to the new server SQL data and data folders as needed.

Notes:

• 3D Inspection System 12 installations create and use a SQL 2022 “ThreeD2” instance. e.g. connecting via SQL Management Studio,  server name and instance would be COMPUTERNAME\THREED2  (instance name should not be included in the Computer Name selected from the 3D Welcome wizard- only the computer name of the server itself)
• If your network is using Windows Authentication, the network administrator will need to install SQL Management Studio on the local machine (server) actually containing the database and add the other machines as users so they are in a proper domain.
• If your network is using TCP/IP with SQL Authentication (not recommended by Microsoft), please contact 3D support for default credential information, unless you have already changed credentials using SSMS for connecting workstations.
• IMPORTANT NOTE: When connecting the server to its local database, we recommend either connecting using Windows Authentication or using “(local)” as the computer name with SQL Authentication, as using a specific computer name on the machine hosting the database may prevent it from updating to future versions of 3D as well as including the database in backups made from 3D on the local machine. You may opt to make backups separately in SQL, however assistance with this is outside of the scope of 3D support.
• Note that when updating the program, we recommend installing any update on the machine hosting the database first, and then afterward update workstations. All computers should be updated to run the same version to ensure compatibility.
• Any questions regarding proper network or domain setup should be directed to an appropriate qualified IT technician or Microsoft. 3D Inspection Systems support would only be able to assist with setup on the local machine where the database is located, or advise regarding settings to use in 3D once a copy of SQL Management Studio on the workstation is able to connect properly to the database on the server.

Once the program is installed and working on the server, the network administrator will then need to make any workstation connections as needed.

STEP B – CLIENT/WORKSTATIONS:

Once version 12 is running properly on the server, workstations may be set up: On each workstation, install version 12 (for new installs, the owner may activate each computer immediately or later).

Networking the data involves two pieces, networking the SQL THREED2 database instance, and networking the data folder containing the remaining data such as reports, forms, documents, actions, etc.

3D Inspection System installs mixed mode for flexibility, but Windows Authentication is preferred and recommended by Microsoft. If the networked computers are not domain joined or you cannot use Windows Authentication but must use SQL Authentication, please contact 3D Inspection System support for assistance with the default credentials or use SSMS to adjust the sa credentials in THREED2 as desired (note that if the default credentials are changed, it is your responsibility to record them for future use as 3D will expect the default options).

After the appropriate Step A scenario has been finished for the host/server, use the matching scenario # steps below to set up the client/workstation computer(s).

B1. New Installation on a replacement or new client/workstation:

1. Make sure the server is already running the same version of 3D you will be installing on the client/workstation.
2. Install 3D desktop software on the client/workstation, launch, and activate as appropriate. IT or other parties may choose Activate Later to defer activation and continue with setup, allowing the registered user to actually activate later.
3. Use Welcome Wizard to initial set up a new company database locally to verify SQL functions properly on the computer. Use the workstation name as the company for easier clarity later, and only enter an Inspector name to proceed. We will connect to the real database later.
4. Switch to report writer. Use Preferences > Preferences, File Locations tab to Open the user/temp folder on the local C: of the client/workstation. Leave File Explorer open and Cancel the Preferences window and close the software.
5. Map shared data folder on server to drive letter.
6. Reset string and connect to server SQL.
7. Note that periodically a backup should be made from 3D launched on the server machine using File > Backup All Files to create a complete backup that 3D support team can assist with. If you choose to backup SQL and data files by other means, 3D support may or may not be able to offer assistance with those items.

B2. Upgrading prior 3D version 12 series to newer 3D version for Existing Installation:

1. Server should already be running the newer version (see step A scenarios). On client/workstation, uninstall the prior version of 3D from Windows Apps and Features.
2. Install the newer version of 3D and launch the software to verify it opens and reconnects. Verify the latest jobs in the SQL database on the server are present in Office Management. If prior connection was not made via Windows Authentication you may need to reset the database connection and connect fresh to the newer SQL instance on the server. If upgrading from 12.3 or earlier, and non Windows Authentication was used, you may need to contact support for assistance. Or use SSMS on the server to adjust the sa password or use SSMS to add user permissions as needed.

B3. Reconnecting workstations after moving an old Host/Server to a new Host/Server:

1. Reset connection string on Workstation
2. Launch 3D Inspection System. In Welcome Wizard use the Connect option to reconnect to the server.

 

Notes:

• Connect Office Management database:  From the Welcome wizard options, choose “Connect to SQL”.  If the database is on another computer (server), use that option and select and enter the appropriate connection settings for your network setup (only the network administrator can assist with this).  When you enter the Computer Name for the server, and appropriate connection options, the Select Database prompt will appear, allowing you to select the Database for the company name you set up there.

Troubleshooting tips, if the Company Name does not appear:

• Did you enter the Computer Name correctly? On the computer containing the database, verify the computer name by clicking Start, right-clicking Computer, and choosing Properties.
• If choosing the Computer Name and type of authentication does not display the Database from which to select the company, try connecting directly to the database using SQL Management Studio installed on the workstation. If you cannot connect SQL Management Studio to the database, then you will need to troubleshoot your network connections so that it can connect.  Once SQL Management Studio can connect to the database, then you should be able to connect to it from 3D Inspection System software as well.

Connect to other Data files: After successfully connecting a copy of 3D Inspection System software running on a workstation to the SQL database stored on the server, one may next connect to other data used by the rest of the program (reports, forms, documents).

On the workstation, map an actual drive letter to the server computer where the other data files are stored (the default data file location is Documents\3D Inspection System 11\ in the user profile where the program is used or launched). The server drive MUST be mapped to a real drive letter and path on the workstation, because a Universal Naming Convention (UNC) path (i.e. \\server..) does not contain the standard drive letter nomenclature needed for windows to allow 3D to properly create temp folders and other program functions for reliable operation. Using a mapped drive letter is the proper way to network applications, since unmapped drives may unexpectedly disappear sometimes in Windows, which could result in data corruption. If the drive is mapped properly you should be able to access that specific drive letter and folder containing your data from My Computer in the workstation.  Note that since 3D Inspection System software needs to manipulate files to work (create directories, add/remove files, etc), you must set full privileges for the shared data folder. We recommend mapping a parent folder containing the actual 3D data folder, since Windows often restricts write privileges from the root location of a drive letter.

Once your data folder location is mapped to a real drive letter and folder name, on the workstation open the 3D Inspection System software and and set its data location to the shared folder on the server containing the actual data, forms, documents, and reports. To do this, open the 3D Inspection System software, switch to the Report Writer, click Preferences > Preferences, File Locations tab. For “Location of data files: use the browse button to the right to navigate and select your data folder and accept the change (be sure to browser to the real mapped drive letter and folder path).  Note that the “Location of user and temporary files” folder should remain set to a local location on the workstation.  This setup allows the Office Management itself to connect to the SQL database on the server, the rest of the program to share the remaining data files in the common mapped “data” folder, and workstation specific files and settings and temporary folders more efficiently accessed locally.   Finally, close and reopen 3D Inspection System to use the new data location.

If you need further assistance with networking, please consult your network specialist. 3D Inspection System support can assist when your basic network is working and that you have a mapped drive letter on the client/workstation that access your 3D Inspection System data folder on the host/server or file server, and when SQL Management Studio is able to connect to the SQL “ThreeD2” database instance on the server from your workstation.

Note that your IT person or network administrator may prefer a separate backup routine for backing up SQL data on the server directly.  Otherwise, if you want 3D Inspection System backups that are made within the program using the File > Backup All Files option to include the Office Management information stored in SQL, the backup MUST periodically be run directly from the copy of 3D Inspection System running on the server itself, as it can only access the SQL database for backup if “Local”.  Note that any backups done from within 3D Inspection System on a workstation would not include the Office Management information stored in SQL, but would only include the other custom data files used by the remainder of the program.

NOTE ABOUT TERMINAL SERVICES: For remote access, note that 3D software was not designed to work on Terminal Services, and doing so for concurrent access of multiple users from the same computer is a violation of the EULA unless appropriate licensing has been obtained.

Note that Windows often treats separate user profiles similar to as if they were separate computers/installations, so windows installer may do a “repair” each time a different windows user profile attempts access on a particular computer. Thus logging into the same computer for different users would likely annoying or cause launch reconfiguration delays.

Terminal services may also have its own general issues, usually related to managing profiles. But unless you need concurrent access for multiple users, using just a single profile for any users who need to access 3D in the environment may work, so there’s no messy switching back and forth users on the same computer. That way multiple users may use the software on the terminal when needed under the same computer profile, just not at the same time.

Otherwise for concurrent use of the program amongst multiple users, you could set up separate workstations or terminals for each user as needed (in accordance with the number of licenses purchased by the company- our software comes with a license for only 2 computers/terminals- additional licenses beyond that would need to be purchased.)  Thus one might have each workstation or separate terminal share data stored on a server location in common. With such a setup, one would simply network the data folder and set up 3D on each workstation to access the shared data folder, with each using their own workstation for their own user profile and 3D user/temp folder settings.  Each workstation could in turn be accessed remotely from another location by means of Remote Desktop if need be, while leaving all the data intact in the centralized location.

For managing multiple inspectors, using the 3D Mobile Inspector apps to retrieve and return reports is often an easy solution without requiring additional licensing or networking. Should an inspector wish to work further on final reports retrieved  back to the main office, they may remote into a networked workstation running the regular version of 3D, or opt to use a free non-timed evaluation copy of 3D on their own computer to open and perform final editing. Contact 3D support or sales for details.