Cannot download the Package – Essentials 2012 R2

August 8, 2016 by 6 Comments

If you have updated to the latest UR Rollup and are trying to install the connector on a client, you may see the following notice.

‘Cannot download the package’

G1 Error

The clientdeploy log file will show you the issue is downloading this file,  http://go.microsoft.com/fwlink/p/?LinkId=799487 manually downloading this file can also cause unpredictable results.

G1 Log Snip

You can download this file ahead of time and store it centrally, or manually install it to install the base layer of the connector before running the wizard.

Incidentally, if you haven’t updated the Server and you are currently trying to install a client and receive a similar error, you will find that the file the Client Connector is trying to download is Windows10.0-KB2790621-x64.msu. Microsoft have now removed this from public availability, causing the Connector software to fail.

You should apply the update rollup to the server to resolve this issue.

Filed under Essentials, General, Tips & Tricks

About Robert Pearman
Robert Pearman is a UK based Small Business Server enthusiast. He has been working within the SMB IT Industry for what feels like forever. Robert likes Piña colada and taking walks in the rain, on occasion he also enjoys writing about Small Business Technology like Windows Server Essentials or more recently writing PowerShell Scripts. If you're in trouble, and you can find him, maybe you can ask him a question.

6 Responses to Cannot download the Package – Essentials 2012 R2

  1. Brian Weinberg says:
    September 15, 2016 at 6:25 pm

    Hi Robert,

    I have received this error message, but I am not sure I understand your post. You mention that you might receive the error if you have updated to the latest UR rollup, but then indicate the solution is to update to the latest UR rollup (or, quite possibly, I am misunderstanding what you wrote). Could you please clarify? Thanks for all your hard work.

    Reply
    • Robert Pearman says:
      September 15, 2016 at 6:57 pm

      You may get this error in either circumstance now. Prior to the update, the connector routine would download a file from Microsoft. This file is no longer available, and causes the error.

      If you have applied the update, the error may be caused by the Microsoft server being unable to complete the download. This causes the error.

      So, best bet is to do the update. Try to connect, if you get an error try to manually download the connector msi file. This msi file installs the base of the connector which the Connect routine uses to connect your client to the Dashboard.

      Reply
  2. Brian Weinberg says:
    September 19, 2016 at 9:02 pm

    Hi Robert,

    Just to clarify, where would you suggest to download the correct MSI file from, in the latter case?

    Thanks.

    Reply

Leave a reply

Fill in your details below or click an icon to log in:

Gravatar
WordPress.com Logo

You are commenting using your WordPress.com account. ( Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. ( Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. ( Log Out /  Change )

Cancel

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: