blade3
blade3

Reputation: 211

Invoke or BeginInvoke cannot be called on a control until the window handle has been created

I am trying to install SQL Server 2008 Developer Edition x64 on a Windows Server 2008 VM. I run the installer for a standalone installation and this works fine for the setup support rules bit. That passes ok but then I get this error:

TITLE: SQL Server Setup failure.

SQL Server Setup has encountered the following error:

Invoke or BeginInvoke cannot be called on a control until the window handle has been created..


BUTTONS:

OK

How can I resolve this? I am getting 2008 R2 CTP but this is just a CTP. My download is from DreamSpark.

Thanks

Upvotes: 21

Views: 56218

Answers (11)

M.Doos
M.Doos

Reputation: 101

Before Installation, close all windows explorer and web browser. :)

.

Upvotes: 1

KRichardson
KRichardson

Reputation: 1010

For Server 2003 with this issue, I installed 2008 R2 management tools - which should work fine with 2008.

http://www.microsoft.com/en-us/download/details.aspx?id=22985

Note: Needs PowerShell on 2003 to install: http://www.microsoft.com/en-us/download/details.aspx?id=20020

Upvotes: 0

Sandip Patel
Sandip Patel

Reputation: 31

I've did another trick:

  1. In the Installation Disc you will find a folder, x86 and x64

  2. Select as per your OS and go inside the folder

  3. Click on the LandingPage.exe

  4. It will show the page, in that click on the second Option on the left hand menu "Installation"

  5. Click on "Start Standalone installation from the menu at the right side

  6. It will ask for the location files on the disc

  7. Show the location, e.g. <Your Disc Drive>/SQL Server Enterprise 2008/x86

It will complete the installation successfully

Upvotes: 3

LAXMI
LAXMI

Reputation: 21

In Windows 7 64 Bit, press ctrl+alt+delete, start the task manager and end the landing page process and it will successfully install.

Upvotes: 2

eyesark
eyesark

Reputation: 11

Had the same problem; made sure no other instance of setup was running from process explorer and then restarted installation and it worked fine for me

Upvotes: 1

JSG
JSG

Reputation: 11

I had the same problem when i was installing on Window 7. The only thing I could find was to retry the install again right after the failure and it worked after some time.

Upvotes: 1

user217974
user217974

Reputation:

I had this same error a number of times trying to install SQL Express 2008 x64 on a 2008 R2 64-bit server (VMWare) and I finally got it working doing the following:

Start the installation and when it gets to the point where the security window pops up asking you if you authorize the installation to run, open the temp folder. C:{GUID} and copy that folder (contains setup.exe and supporting files) to your desktop.

Click "OK" on the security dialog and it will probably error.

Once the error dialog goes away just run the setup.exe from the temporary directory on your desktop and it works.

Hope this helps someone else.

~Matt Heidenreich

Upvotes: 1

sgf
sgf

Reputation: 1

closing all open windows worked for me. definitely a UI problem with 64 bit.

Upvotes: 0

Nick Bolton
Nick Bolton

Reputation: 39550

This isn't really a real solution, but it worked for me after the 5th attempt. Not sure if it makes a difference, but on the 5th attempt I minimized all other windows (so that SQL setup is the only window that has focus) since the issue appears to be UI related.

Update: After overcoming the 1st issue, I got another issue where the actual database engine component failed to install without reason. The solution was to restart and try again.

The x64 installer seems to be really buggy.

Upvotes: 25

Neal
Neal

Reputation: 21

I see MS has answered this. It's because the release of MSSSQL is newer than the SP is. They have a hotfix that apparently needs application. Oh joy!

http://support.microsoft.com/kb/975055

You then have to request the Hotfix, and wait for the link to be sent to you. They say 5 minutes, but we'll see.

Upvotes: 2

James Bailey
James Bailey

Reputation: 1245

I had the same problem once with installing the service pack. The only thing I could find was to retry the install again right after the failure. It took about five times, but it eventually worked. I think there's something odd about the installer on 64-bit Windows.

Upvotes: 0

Related Questions