"We can't verify who created this file. Are you sure you want to run this file?"

"We can't verify who created this file. Are you sure you want to run this file?"

Q - When I started Elliott V7 or V8 from my workstation, I received a message: "We can't verify who created this file. Are you sure you want to run this file?" It also display the following message at the bottom of the dialog box:

This file is in a location outside your local network. Files from location you don't recognize can harm your PC. Only run this file if you trust the location.

See sample screen below:


But if you use Windows Explorer to look at the property of EL800.EXE, it clearly indicates the signer is Necellent System, Inc. See sample screen below.  Why is that not recognized by Windows when I tried to launch the task?



A - In Spring 2013, the Windows team made a change such that anything executed from a network share will show a prompt even if validly signed.  To counter this problem, you can define the network share as a trusted server in your intranet. Here is how you do it:

(1) Bring up Internet Explorer, and go to Internet Options, then go to "Security" tab. See sample screen below.



(2) Choose the "Local intranet" zone, and click on the "Sites" button.

(3) Add your Elliott PSQL server as a local intranet site.  For example, if your server name is Server-Name, then you will enter that as
    \\Server-Name
See sample screen below:


Once you click on Add, you should see the following entry show up:
    file://Server-Name
See sample screen below:


(4) Now try to start up your Elliott session again to see if the message goes away.

You can also handle this by editing the corresponding registry.  For more registry info, please see the the following articles:

  https://support.microsoft.com/en-us/help/303650/intranet-site-is-identified-as-an-internet-site-when-you-use-an-fqdn-o


EMK







    • Related Articles

    • The Run Local or Hybrid Feature in Elliott 8.5

      Release Date: 12/3/2018 In Elliott 8.5, you can run Elliott in three different modes based on the location from which you execute Elliott application programs: Run Local: This is the recommended default method. Run Hybrid: This is designed to run for ...
    • File Created in C:\ Root Directory Disappears

      Q - In ACH Processing Setup, I choose to write my NACHA file directly to the local C:\ root folder. The NACHA File Creation Journal shows that the NACHA file was created successfully at C:\20150129-155424.TXT. See example below: However, when I use ...
    • How to Subscribe to Add Order Event So I Only Receive E-mail When Credit Memo Is Created

      Q - Do we have a way to trigger an event when a credit memo is added? I am aware that there's an "Add Order" event that can be subscribed to from the customer file. But I only want to know when a credit memo is entered. A - You will need to use the ...
    • Run Time Error 166 in Deferred Processing

      Release Date: 2/16/2022 Version: 7.5 & Up Q - I couldn't find documentation about error 166. Our deferred processes locked and had this error. Can you provide any information about what this message means? EL850RP.EXE - COBOL Text Window Execution ...
    • Report Desk Company DSN missing. Ask your administrator to run EL860CF

      Release Date: 6/26/20 Version: 8.6 & Up Q - When I try to run a report in Elliott 8.6, I receive the following message: "Report Desk Company DSN missing. Ask your administrator to run EL860CF." See sample screen below: What should I do? A - Report ...