Invalid Digital Signature

[jacintor]

Hello,

I am trying to install the gateway on a customer server. I am getting the same error message everytime I try to install it:

"A file that is required cannot be installed because the cabinet file C:/Documents and Settings\Administrator.SC.000\Dados de aplicativos\OnePacs Gateway (2.2.0.3)\install\disk1.cab has an invalid digital signature. This may indicate that the cabinet file is currupt."

How can I fix this? I have tried downloading the gateway for a second time without any luck.

Thank you!

Rodrigo

[justin]

Hi Rodrigo,

What version of Windows are you running? Also, please verify that you are connected to the internet when running the installer. Windows needs that to validate the digital signature.

Regards,

Justin

[jacintor]

Thank you for the quick reply Justin.

It is a Windows 2003 server and it is connected to the internet because we downloaded the gateway straight from the machine. Is it possible Windows is blocking only the digital signature verification? What else?

Thanks!

Rodrigo

[justin]

Do you have all Windows updates applied? I know Microsoft had an issue with their certificate repository a while back. That was supposed to be resolved in a Windows update.

Thanks,

Justin

[jacintor]

Hello Justin,

We installed Windows 2007 32b in the new virtual machine and successfully finalized the gateway installation. However, everytime we try to test "telnet localhost 4104" the computer does not recognize the port. Firewall and Windows defender have been deactivated.

Why would that happen?

Thanks,

Rodrigo

[justin]

Hi Rodrigo,

Can you expand on what you mean by "the computer does not recognize the port"? Are there errors in the log?

Here are some guesses:
- Is telnet enabled on your system? It is not for some versions of Windows 7. See this article for instructions on how to enable: http://www.wikihow.com/Activate-Telnet-in-Windows-7
- Is port 4104 used by another process? You can execute "netstat -ao" from a command prompt to see which ports are in use and by which process.

Regards,

Justin

[jacintor]

Hi Justin,

Yes we installed Telnet. Port 4104 shows as not activated at all even though the gateway has been installed. The only port that shows active is 8080. Do you think it might be a problem with the virtual machine? Or the physical computer might not be creating the 4104 port for some reason?

Thanks,

Rodrigo

[justin]

Are there errors in the log (C:\onepacs\gateway\server\default\log\server.log)?

[jeremy]

Also, DICOM connectivity from localhost can be done using the following without telnet.
1. Login to the OnePacs Gateway web UI. (https://onepacshelp.com/display/ON/OneP ... +Interface)
2. Click on the AE Management Link on the top of the screen
3. Click on the Question mark (?) on the right side of the grid for the "GATEWAY" AE Title
4. A new screen should show success if the Gateway was able to successfully C-ECHO itself.

Also, you may want to verify that your windows host name doesn't contain an underscore (_) which Windows allows, but is a violation of the standards for hostnames.
Regards,

[jacintor]

Hi Justin,

Yes there are four server.log files (1-4). Does that mean it might be a problem with the gateway installation itself?

Regards,

Rodrigo

P.S. I will try to check connectivity without telnet