Navigation:  Error Messages >

Unknow Publisher

Print this Topic Previous pageReturn to chapter overviewNext page

When I run a process developed with TAS Professional (Tasruntime.exe) with address "c:\folder\Tasruntime.exe" it works properly.

However when I run it with a network address "K:\folder\tasruntime.exe"

I systematically have an "unknown publisher" warning message with a run/cancel" button selection.

How can I deactivate this warning message ?


When you run Tas Professional from the local "C" drive, it is treated as 1 security > zone. When you run it via a UNC (or any other external location) it is a different, untrusted security zone.


When the shortcut points to a share on a server, you could adjust the IE7 security settings. These are the settings that worked for a similar setup at a client.  This would work for any other aplicstion you were running on your server.

1. Open the IE.

2.  Settings from Tools, Interanet Options.

3. Click on the Security tab

4. select Local Interanet and click Sites.

5. Clear the checkbox for Automatically detect intranet and check the other 3 boxes.

6. Click the Advanced button on that same dialog box and add file://ServerName to the list of trusted sites.

7. Clear the checkbox to "Require server verification (https) for all sites in this zone.

8. Clcik Ok

9. Click Apply

10. Click Ok


The next time you use your TAS professional program there should be no error message.


Please note: The example above sets HIGH RISK files types to LOW RISK so that they can be executed without having to honor the warning dialog.  We are creating this example because many corporate customers request this change to make their day-to-day operations easier to maintain.  With that said, setting these options in IE  can put your system at risk, so please fully read the external documentation available on Attachment Manager and weigh the risks involved before making the decision to allow these files types to be executed without warning the user. We are assuming here is that all of the program on your server are safe to execute.  This would have to be done to every work station on your system.


There may be other way to do this. I found this to be easy and fast to implement. There are probably some registry settings you could change that would do the same thing.





Page url: