Cannot Log In Due to Blank Trimble Identity Window
If your Trimble Identity (TID) log in window is blank and rebooting your computer did not help, use the following instructions to clear the issue.
- Ensure all the Requirements for connecting to Tekla Online services have been completed; especially whitelisting the listed domains.
- Ensure .NET Framework 4.7.2 version or later is installed.
- Clear the Tekla Account registry
- Clear the local app data
- Check Microsoft Edge WebView2 Runtime
- Engage Local Area Support
Clear the Tekla Account Registry
1. Open the Registry Editor
2. Copy and paste the following path into the input field at the top of the window:
Computer\HKEY_CURRENT_USER\SOFTWARE\Trimble\Tekla Account
3. Right-click on the highlighted Tekla Accounts folder in the navigation tree on the left and delete it
4. Open your Tekla application again. This will recreate the folder in the registry and force the TID prompt.
5. If the issue persists proceed to the next section of the article, Clearing Local App Data
Please note, clearing the registry will close all open Tekla accounts regardless of the application (Structures, Connect, etc.).
Clear Local AppData
- Open file explorer
- Copy and paste the following path into the input field at the top of the window:
%LocalAppData%
- Delete the folders
CEF
andCEF-EPM-TAI
- Open your Tekla application again. This will recreate the folders in the local application data location
Check Microsoft Edge WebView2 Runtime
- Press the Windows Key ( ) + R on your keyboard at the same time. The Run Command window should come up. In this box, type 'appwiz.cpl' and click OK or press Enter on your keyboard.
- Make sure both the below applications are in this list:
- Microsoft Edge
- Microsoft Edge WebView2 Runtime
Engage Local Area Support
If the TID log in window is still blank after performing the above steps, please Contact support for further troubleshooting. To help expedite a resolution, please enable licensing logging, open the Tekla application at least once, and submit the atc-debug.log
file when Contacting support. This should record data that can help resolve the issue.