Script Repository "publisher could not be verified" error

Hello,
I'm trying to add a script to the script repository, but when I test it to download it, I get the "publisher could not be verified" error. My script is not signed. I do not get this error when downloading other user's scripts, even though
their scripts are not signed either. Is this an issue with signing my script? Why does my script receive this "publisher" error while other scripts do not? I don't want to scare users away with a big red error when they try to download my script!

Not a scripting issue.
You likely need to either zip the script or give it a different extension.  The message is from your browser not from the repository.
¯\_(ツ)_/¯

Similar Messages

  • Frustrated - the publisher could not be verified error - help!

    I am really frustrated trying to get this to work - here's what I did -
    Everything was running fine with 8.2.1. with my iphone - no problems.
    I decided to upgrade using the program auto updater. Tried many times but kept getting an error and it stopped the download.
    So I thought I'll just uninstall everything and start again. I uninstalled itunes and quicktime. I uninstalled bonjour. All folders are gone. The only thing I left on there was the iPhone configuration utility, so not sure if that makes a difference. I've tried the options they suggest online. But I keep getting the warning, "the publisher cold not be verified do I want to run it" .. and when I hit RUN, nothing happens. I've also tried to take the itunessetup filed and right click, running as administrator. Sill no luck.
    What else can I do?
    I even went to an oldapps site to download the version that was working but it doesn't load now either. Appreciate any help!

    Okay, I finally got it to work. I uninstalled Norton anti-virus protection (which was not turned on anyway). Then windows installed service pack 2 tonight, then I re-downloaded the itunes installer file again. Clicked on it, and the warning came up again and I said to still run the file like I always had. For some reason this time it actually started and it's now installed. Everything appears to be working normally.

  • Publisher could not be verified with new executable

    We have a .exe file on our clients which is replaced yesterday with a new one. When a user on the client is starting the new executable then a message appears: publisher cannot be verified, do you no for sure to run this application?
    The exe file is in the program files\subfolder\
    The executable is starting with parameters: / servername.
    It is the same executable as the one that was overwritten only a newer version so i do not understand why to give permission to start this exe.
    I can choose in the message for execute but the next time it starts it must be done again. Because the users on the clients are not administrators they choose for execute in the message then they must give credentials. If in that screen the user chooses
    for NO the program executes without credentials.
    We do not want the question for publishing appearing, why is it suddenly appearing if it is the same name as the older one....
    freddie

    Hi,
    This error happens so because the application chosen to run does not have a valid signature.
    Would you please update the signature in your new version of exe file?
    Please use following tool to verify the signature or sign your exe file:
    Using SignTool to Verify a File Signature
    http://msdn.microsoft.com/en-us/library/windows/desktop/aa388171(v=vs.85).aspx
    If you know, what you open is always safe, we can try to disable this message:
    Disable: The publisher could not be verified. Are you sure you want to run this software message
    http://www.thewindowsclub.com/the-publisher-could-not-be-verified
    Kate Li
    TechNet Community Support

  • Configuration could not be verified error when connect to Cox

    Hi,
    I'm trying to connect to Cox but keep getting the "configuration could not be verified" error. I can access my Cox account through web mail and I've retyped and retried my email address and password enough times to be confident that it's correct. I've also verified my account settings (incoming/outgoing server and ports) with Cox support, and I've checked the my firewall and antivirus settings (norton 360). No luck with anything.
    I'd really appreciate any thoughts anyone has!
    Thanks,
    David

    I should have added that my Cox connection has been set up several years now with no problems but suddenly quit working. I checked everything I know to check, including firewall settings, and finally deleted email account and tried to set it up again. Still getting the same error.

  • Publisher could not be verified message

    I am very confused, I had itunes installe don my computer, and wante dto move it to an external hard drive I bought. I couldnt figure out how to move it so I uninstalled it and when I went to reinstall itunes on the external It now tells me the publisher could not be verified. I have tried to dump all temp files, and i have tried clicking run and save both. still nothing. Now we have three ipods that are worthless with out itunes....HELP!!!! please.....

    okay. try downloading fresh definitions and running vigorous spyware and virus scans. if your security software providers offer them, try running "online" scans too. (they can sometimes pick up an infection even if the security software on the PC has been compromised.)
    (checking on this because sometimes malware will disable Windows componentry relevant to the verification of digital signatures and publishers.)

  • SQL version could not be verified error while installing the SCOM 2012 R2 reporting component

    I have the below SCOM server roles in my SCOM 2012 R2 set up
    1) All servers with Windows Server 2008 R2 SP1, MS - SCOM1, DB & DW - DB1, Reporting Server - DB2
    2) All the DB servers with SQL 2012 SP1
    3) Windows firewall is turned off on all the servers.
    4) Success fully installed all the components except SCOM reporting.
    While installing the SCOM 2012 R2 reporting component on DB2 ( Iam running this set up on the server where I instllaed the SQL DB engine and reportin services in Native mode. Configured the SQL reporting database and reporting URLs successfully in SQL reporting
    configuration manager) getting the below error in the Rporting server instance page. Kindly advise.
    I ran mofcomp.exe and there is no firewall restrictions. My account also has DB owner & sysadmin permissions.
    Also tried re installing the SQL on Reporting server.
    "The installed version of SQL Server could not be verified or is not supported. Verify that the computer and the installed version of SQL Server meet the minimum requirements for installation, and that the firewall settings are correct. See the Supported
    Configurations document for further information".

    Hi,
    As far as I know, after installing SSRS, we don't need to configure the database and reporting URLs manully. When we install the reporting service for SCOM, it will configure those automatically.
    If possible, you may re-install SSRS and then install SCOM reporting service.
    Regards,
    Yan Li
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • "This disc could not be verified" error when burning CDs

    Every time I try to run the CD Burner, the disk seems to finalize then I get this error message:
    *This disc could not be verified and might be unreliable. Try again using a new, blank disc. (Error code 0x80020063).*
    I have tried with many blank disks and different data (text files, music files, etc). The CDs I am using are blank Memorex CD-RWs.
    This machine is using a Matshita DVD-R UJ-845, here's the rest of the info from the System Profiler if it helps:
    MATSHITA DVD-R UJ-845:
    +Firmware Revision: DBN9+
    +Interconnect: ATAPI+
    +Burn Support: Yes (Apple Shipping Drive)+
    +Cache: 2048 KB+
    +Reads DVD: Yes+
    +CD-Write: -R, -RW+
    +DVD-Write: -R, -RW, +R, +R DL, RW
    +Write Strategies: CD-TAO, CD-SAO, DVD-DAO+
    +Media: Insert media and refresh to show available burn speeds+
    What can I do to get my CD burner working?

    All good suggestions...thanks to all of you weighing in. I have had no issues buring DVDs or CDs (7 months) until this week and am a bit puzzled. Since this verify issue popped up, I've tried buring data from various sources and had some success. As such, I suspect it's not a hardware problem.
    I was able to review 1500 JPEGS burned to 1 DVD one-by-one until I found the single file that was an issue. I did this on an XP machine and got a 'cyclic redundancy' error which leads me to believe that I've got a software problem tied to a recent update.
    That file is not corrupted at the source and can be copied individually without issue. I've varied burn speeds, media types, file types and data sources and have not been able to identify why 3 of 11 have worked.
    The first DVD I burned using dic utility at 4x worked. I felt good that I had a workaround to burning via finder but 3 subsequent attempts with disc utility have failed, too.

  • I had to change my gmail accnt password online and now I receive msg "configuration could not be verified" when I try to sign in with new password.

    I had to change my gmail account password on line. I can access my account with the new password through my browser and my cell phone. But when I try to sign in to my gmail account in Thunderbird
    using the new password I get a "Configuration could not be verified" error message.
    Any help would be appreciated.
    Thank You
    Brendan

    That sounds like you're trying to create a new account. What exactly are you doing?

  • "The product distribution file could not be verified" while attempting to install iPhoto

    Hello,
    I have accidentally deleted my iPhoto '11 application, because the iPhoto icon was showing up twice in the Applications (F4 key) and I wanted to clear the space up.
    I have disks that came with my MacBook but they are somewhere that are inaccessible at the moment and I urgently need to reinstall iPhoto.
    I have tried going to the App Store and installing iPhoto through Purchases, but "The product distribution file could not be verified" error shows up.
    I have tried the method of using Console + deleting my 9n /var/folders and the Keychain Access OCSP and CRL methods to no avail. I even tried the Mac OS X Recovery.
    Bottom line is, I don't know where the root of the problem lies and if I'm working on an atrociously wrong tangent. I am going to bring my MacBook to an Apple Store ASAP but am hoping to get some help here even sooner.
    Thanks.

    Hot dang, I found something that worked for me!
    http://reviews.cnet.com/8301-13727_7-57530446-263/fix-corrupt-mac-app-store-down loads/
    Basically you execute a command in the Terminal Utility, delete your Appstore cache and relaunch App Store which now allows me to download iPhoto '11!

  • I am using Mac OS X 10.7.5 as of now and when I am trying to upgrade to Mavericks, it is throwing error "The product distribution file could not be verified. It may be damaged or not signed".

    I am using Mac OS X 10.7.5 as of now and when I am trying to upgrade to Mavericks, the App Store is throwing error "The product distribution file could not be verified. It may be damaged or not signed".
    Is there anything I should do differently? Is anyone else facing the same issue?
    Kindly help.

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    Third-party system modifications are a common cause of usability problems. By a “system modification,” I mean software that affects the operation of other software — potentially for the worse. The following procedure will help identify which such modifications you've installed. Don’t be alarmed by the complexity of these instructions — they’re easy to carry out and won’t change anything on your Mac. 
    These steps are to be taken while booted in “normal” mode, not in safe mode. If you’re now running in safe mode, reboot as usual before continuing. 
    Below are instructions to enter some UNIX shell commands. The commands are harmless, but they must be entered exactly as given in order to work. If you have doubts about the safety of the procedure suggested here, search this site for other discussions in which it’s been followed without any report of ill effects. 
    Some of the commands will line-wrap or scroll in your browser, but each one is really just a single line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, and you can then copy it. The headings “Step 1” and so on are not part of the commands. 
    Note: If you have more than one user account, Step 2 must be taken as an administrator. Ordinarily that would be the user created automatically when you booted the system for the first time. The other steps should be taken as the user who has the problem, if different. Most personal Macs have only one user, and in that case this paragraph doesn’t apply. 
    Launch the Terminal application in any of the following ways: 
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.) 
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens. 
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid. 
    When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign (“$”) or a percent sign (“%”). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign. 
    Step 1 
    Triple-click anywhere in the line of text below on this page to select it:
    kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}' | open -ef 
    Copy the selected text to the Clipboard by pressing the key combination command-C. Then click anywhere in the Terminal window and paste (command-V). I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting. A TextEdit window will open with the output of the command. If the command produced no output, the window will be empty. Post the contents of the TextEdit window (not the Terminal window), if any — the text, please, not a screenshot. You can then close the TextEdit window. The title of the window doesn't matter, and you don't need to post that. No typing is involved in this step.
    Step 2 
    Repeat with this line:
    { sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh|vix\.cron)|org\.(amav|apac|cups|isc|ntp|postf|x)/{print $3}'; echo; sudo defaults read com.apple.loginwindow LoginHook; echo; sudo crontab -l; } 2> /dev/null | open -ef 
    This time you'll be prompted for your login password, which you do have to type. Nothing will be displayed when you type it. Type it carefully and then press return. You may get a one-time warning to be careful. Heed that warning, but don't post it. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator. 
    Note: If you don’t have a login password, you’ll need to set one before taking this step. If that’s not possible, skip to the next step. 
    Step 3
    { launchctl list | sed 1d | awk '!/0x|com\.apple|org\.(x|openbsd)/{print $3}'; echo; crontab -l 2> /dev/null; } | open -ef 
    Step 4
    ls -A /e*/{cr,la,mach}* {,/}Lib*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Spo,Sta}* L*/Fonts .la* 2> /dev/null | open -ef  
    Important: If you formerly synchronized with a MobileMe account, your me.com email address may appear in the output of the above command. If so, anonymize it before posting. 
    Step 5
    osascript -e 'tell application "System Events" to get name of login items' | open -ef 
    Remember, steps 1-5 are all copy-and-paste — no typing, except your password. Also remember to post the output. 
    You can then quit Terminal.

  • After getting the dreaded gray/blue screen, I tried to run disk repair on the internal disk. I got an error message saying "Disk Utility can't repair this disk and restore your backed-up files. The volume Macintosh HD could not be verified completely

    After getting the dreaded gray/blue screen, I tried to run disk repair on the internal disk. I got an error message saying "Disk Utility can't repair this disk and restore your backed-up files. The volume Macintosh HD could not be verified completely." What do I do now? This is an iMac and I'm running 10.6.8.

    Clean Install of Snow Leopard
    Be sure to make a backup first because the following procedure will erase
    the drive and everything on it. See below for how to clone a drive.
         1. Boot the computer using the Snow Leopard Installer Disc or the Disc 1 that came
             with your computer.  Insert the disc into the optical drive and restart the computer.
             After the chime press and hold down the  "C" key.  Release the key when you see
             a small spinning gear appear below the dark gray Apple logo.
         2. After the installer loads select your language and click on the Continue
             button. When the menu bar appears select Disk Utility from the Utilities menu.
             After DU loads select the hard drive entry from the left side list (mfgr.'s ID and drive
             size.)  Click on the Partition tab in the DU main window.  Set the number of
             partitions to one (1) from the Partitions drop down menu, click on Options button
             and select GUID, click on OK, then set the format type to MacOS Extended
             (Journaled, if supported), then click on the Apply button.
         3. When the formatting has completed quit DU and return to the installer.  Proceed
             with the OS X installation and follow the directions included with the installer.
         4. When the installation has completed your computer will Restart into the Setup
             Assistant. Be sure you configure your initial admin account with the exact same
             username and password that you used on your old drive. After you finish Setup
             Assistant will complete the installation after which you will be running a fresh
             install of OS X.  You can now begin the update process by opening Software
             Update and installing all recommended updates to bring your installation current.
    Download and install Mac OS X 10.6.8 Update Combo v1.1.
    You may be able to backup your data if you have an erased external drive you can use. Before you do the above but after you have opened Disk Utility you can try to clone your drive:
    Clone using Restore Option of Disk Utility
      1. Open Disk Utility.
      2. Select the destination volume from the left side list.
      3. Click on the Restore tab in the DU main window.
      4. Select the destination volume from the left side list and drag
           it to the Destination entry field.
      5. Select the source volume from the left side list and drag it to
          the Source entry field.
      6. Double-check you got it right, then click on the Restore button.
    Destination means the external backup drive. Source means the internal startup drive.
    Now this will only work if the drive is accessible and can be cloned by Disk Utility. Otherwise, you would need to access your drive from another Mac that you can connect via Firewire - Target Disk Mode.

  • I can't download an app or update ,It says ( the product distribution file could not be verified) in App Store ,and in iTunes says An unknown error occurred (-50) ?

    Hi:all
    I can't download an app or update ,It says ( the product distribution file could not be verified) in App Store
    ,and in iTunes says An unknown error occurred (-50) ?
    Help Please.

    See this link from another similar question.  It may need patience to resolve.  I think Thomas Reed's suggestion is best place to start.
    App Store rejects buy of Mountain Lion: Apple Support Communities

  • I cannot download OS X Mountain Lion, I get an error message that says: "We could not complete your purchase. The product distribution file could not be verified. It may be damaged or was not signed." Why am I receiving this message?

    I cannot download OS X Mountain Lion, I get an error message that says: "We could not complete your purchase. The product distribution file could not be verified. It may be damaged or was not signed." Why am I receiving this message?

    Servers may be overloaded.
    One user reported:
    Deleted file com.apple.appstore in /var/folders/, dissabled VirusBarrier X6: problem solved!

  • When ever i'm trying to install an app from the app store i'm getting the following error "We could not complete your purchase - The product distribution file could not be verified. It may be damaged or was not signed", plz help me to rectify this .

    when ever i'm tring to install an app from the app store i'm getting the following error.
    "We could not complete your purchase - The product distribution file could not be verified. It may be damaged or was not signed".
    someone plz help me to overcome this.

    Installing the appropriate combo update may help...
    If you are running v10..7 Lion, install the OS X Lion Update 10.7.4 (Client Combo)
    For 10.6 Snow Leopard >  Mac OS X 10.6.8 Update Combo
    Then restart your Mac. Try the App Store.
    If that doesn't help, try the following..
    Quit the App Store if it's open.
    Open the Finder. From the Finder menu bar top of your screen click Go > Go to Folder
    Type this exactly as you see it here:
    /Library/Preferences/SystemConfiguration
    Click Go
    Move the NetworkInterfaces.plist file from the SystemConfiguration folder to the Trash.
    Relaunch the App Store and try downloading Mountain Lion.
    You may also need to disable anti virus software and turn off the Firewall in System Preferences > Security (or Security & Privacy) > Firewall

  • HT4414 When I try to purchase Mountain Lion i get an error message:  "We could not complete your purchase.  The product distribution file could not be verified. It may be damaged or was not signed."  I can purchase other apps, why not Mountain Lion?

    When I try to purchase Mountain Lion i get an error message:  "We could not complete your purchase.  The product distribution file could not be verified. It may be damaged or was not signed."
    I can purchase other apps, why not Mountain Lion.   I get the same message on my wife's IMAC.

    The only thing that worked for me was to boot in safe mode.
    Power down.  Then press power button and hold 'shift' key until grey screen with progress bar appears... Once booted and logged in just open safari and browse to applestore. 
    No trouble at all once I did this.
    Hope it helps.

Maybe you are looking for