Problem:

After clicking the icon or link to start the application, screen remains blank, application does not start, why? 

Solution

There can be any number of reasons why the application will not start, one or more of the following may apply. 

Reason #1: Software update

After company forced software update, AutoPIPE does not start.

Workaround:

Cold restart the computer. After reboot try and restart AutoPIPE.

Reason #2: Malware DLL 

While using WinDbg application, AutoPIPE was opened, 

The following error occured:

*** ERROR: Module load completed but symbols could not be loaded for C:\PROGRA~2\WIA6EB~1\Datamnger.dll

Workaround:

Locate and rename / delete the offending DLL. 

Close WinDbg dialog and Windows Explorer, restart AutoPIPE

Reason #3: Malware / Security application running in the background

In one instance, user has both Cybereason Ransom Free and Malwarebytes applications running in the background. The issue is that one of the applications detected AutoPIPE sending out a request for a license (Access violation - code c0000005)  and flagged it as a malicious application and shuts it down immediately. We are not sure exactly what the security application detected (ex. checked out license if it detects a network call and this is what it is being blocked)

Workaround:

Typically these security applications have an option to add certain processes to their safe, ignore, or trusted list so they can work. Perhaps that may be something that can be set up by the IT department. 

Otherwise, suspend security application, start AutoPIPE, and then enable the security application again. Your IT department should be able to help with this.  

On one occasion, problem was related to Malwarebytes Corporate (which is a secondary and not visible AV product).

Reason #4: NVIDIA Graphics card settings

After running WINDBG application, log file provided the following information near the end:

ModLoad: 1ccc0000 1d95e000 C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_3f9eae06dd582000\ig9icd32.dll
ModLoad: 5d360000 5d36f000 C:\WINDOWS\SysWOW64\resourcepolicyclient.dll
ModLoad: 79030000 7905c000 C:\WINDOWS\System32\DriverStore\FileRepository\nvdmwi.inf_amd64_ea069416c21f849f\nvdlist.dll
(5f2c.5594): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=0019d658 ebx=1a7e81e8 ecx=00000000 edx=00000000 esi=00000000 edi=76553240
eip=00000000 esp=0019d604 ebp=0019df60 iopl=0 nv up ei pl zr na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00210246
00000000 ?? ???

Note, that lines 1 and 3 mentioned loading of DLL files. Both of these DLL files are specific to the computer's graphic card. Then on line 4 there was an access violation. 

Next, review AutoPIPE's Log files, 

2021-06-24 21:26:21.993363: <info> INITAP: setup recently used models list.
2021-06-24 21:26:21.993363: <info> INITAP: Initialize form/panel/command windows.
2021-06-24 21:26:22.013309: <info> c_InitGraphicsFromHwnd: Initialize GFW graphics from passed window handle

The last line entered was directly related to graphics.

Based on these 2 pieces of information, the issue must be related to the computer's graphic card settings. 

Workaround:

See WIKI here for suggested NVIDIA's graphic card settings. 

Reason #5: Unknown

If none of the following resolve your issue, please submit a Service Request, mentioned this WIKI, and attach / upload a zip file containing all of the file mentioned here.  

See Also

AutoPIPE Crashes / Freezes on Start-up

Bentley AutoPIPE