AnsweredAssumed Answered

2016 Administrative Image Install Failing

Question asked by Nathan Hill on Oct 22, 2015
Latest reply on Feb 6, 2016 by Peer Larson

Like • Show 0 Likes0
Comment • 14

I'm having a problem getting an install from an administrative image to work. It starts and almost immediately goes to the screen saying 'cancelled'. I've attached the install log file as well, though probably not helpful considering how generic the error looks.

Anyone else had this issue or been able to successfully install from a 2016 admin image?

Tried on Windows 10 & Windows 7. With & without virus scanner enabled.

*edit: I skimmed too quickly some serial numbers were in the log files. I'm just removing them. The pertinent line seems to be:

"INTERNAL ERROR: EXCEPTION in InstallNext!"

Attachments

2016 error.PNG278.1 KB

No one else has this question

Outcomes

14 Replies

Deepak Gupta Oct 22, 2015 12:59 PM
Mark Correct
Correct Answer
Don't share log blinding on public forums with removing the serial number from them.

Can you recreate the admin image? Also make sure you've admin right before you make image OR install from image.
Like • Show 0 Likes0
Actions
- Nathan Hill @ Deepak Gupta on Oct 22, 2015 1:07 PM
  Mark Correct
  Correct Answer
  I've already recreated the admin image twice. And yes I have admin rights while creating and installing.
  Like • Show 0 Likes0
  Actions
  - Jim Sculley @ Nathan Hill on Oct 22, 2015 1:33 PM
    Mark Correct
    Correct Answer
    I had the same problem with the same error message. I was installing the admin image on a test machine that also acted as an EPDM archive and database server. If I installed on a different machine, all was well. In the end, I just installed without the admin image on the test machine.
    
    Jim S.
    Like • Show 0 Likes0
    Actions
    - Nathan Hill @ Jim Sculley on Oct 22, 2015 2:42 PM
      Mark Correct
      Correct Answer
      I've only tried creating the image from my laptop so far. I've tried before and after I had a standalone installation of 2016... which incidentally does work.
      Like • Show 0 Likes0
      Actions
Brian Hoerner Oct 22, 2015 2:25 PM
Mark Correct
Correct Answer
Was the Admin Image created on the same server/workstation that it is kicked off on?

Brian
Like • Show 0 Likes0
Actions
- Nathan Hill @ Brian Hoerner on Oct 22, 2015 2:43 PM
  Mark Correct
  Correct Answer
  Tried it that way and on another machine.
  Like • Show 0 Likes0
  Actions
  - Jim Sculley @ Nathan Hill on Oct 22, 2015 2:51 PM
    Mark Correct
    Correct Answer
    Is this a network license? Have you upgraded the license server to 2016?
    Like • Show 0 Likes0
    Actions
    - Nathan Hill @ Jim Sculley on Oct 22, 2015 2:54 PM
      Mark Correct
      Correct Answer
      Yes & Yes
      Like • Show 0 Likes0
      Actions
Scott Slovik Nov 12, 2015 5:37 PM
Mark Correct
Correct Answer
Nathan,

I have the same error with my SW2016 SP0 and SP0.1 Admin images.
I created the Admin images on the same VM server that all my previous installs are located.

The computer I'm trying to install on is Win7 x64 workstation.
It did have SW2016 betas installed on it, but I uninstalled everything, and even
used ccCleaner to remove all old remnants of SolidWorks.

I have not tried to do a normal install yet, as I need to use the admin image
for mass deplyment to my users.

UPDATE 11-3-2015...
I installed 2016 using the normal (non-admin image) installer from the same download.
This installed just fine on my test workstation.
I'm not sure if some prerequisite is missing from the admin image or not, but i'm not
100% convinced that my 2016 admin image is bad.
Need more investigation.

UPDATE 11-12-2015...
Worked with VAR today on this issue, but still no luck.
Neither my server or my client machines have the kb 3072630 update installed.
I download Solidworks 2016 SP0.1 to my file server, and built the Admin Image on the same server.
(Just like I have been doing on this server since 2011).
I tried installing with local Administrator account, not domain account. Still fails at 1%
I copied my Admin image to my local client machine. Still fails at 1%
The SolidWorks logs generated seem to offer no help pointing to the problem.
Like • Show 0 Likes0
Actions
- Nathan Hill @ Scott Slovik on Nov 5, 2015 5:12 PM
  Mark Correct
  Correct Answer
  I've run out of ideas and I've opened a ticket with our vendor who will hopefully escalate up to Solidworks directly. I've tried every permutation and troubleshooting step I can think of. Standalone installs do work, but I REALLY don't want to have to do that on 12+ machines hoping I (and other staff) pick the right options and features every time.
  
  This isn't my first time creating an admin image either. I've been fighting with their finicky installer since 2010 I believe.
  
  We'll see what support says.
  Like • Show 0 Likes0
  Actions
Nathan Hill Nov 25, 2015 1:47 PM
Mark Correct
Correct Answer
Thought I'd update this since we figured it out. Despite the installation guide specifically saying that the PDM Client addin for AutoCAD does NOT require AutoCAD be installed..... that's what the problem was. In the admin image unselecting the AutoCAD addin & Inventor as well allowed an install to go through.

My thought was I'd install the AutoCAD addin in case we needed it. We do have a handful of AutoCAD installs, but if the machine didn't have AutoCAD installed it would install the addin and make it available IF AutoCAD was installed in the future.

Anyways, it's fixed now. Hope this helps someone else some headaches and cursing! Scott Slovik
Like • Show 1 Like1
Actions
- Scott Slovik @ Nathan Hill on Nov 30, 2015 10:13 AM
  Mark Correct
  Correct Answer
  Thanks for the update Nathan.
  I uninstalled all SolidWorks from my test laptop, and I'm currently running another attempt at installing 2016 SP0.1 from my admin image without the AutoCAD Add-in for PDM Client enabled. All looks good so far, since I'm past the 1% failing point.
  
  I think it also might have something to do with the SolidWorks Electrical being installed.
  I already had SQL server installed on the local test computer from SW2015, so I think
  part of my issue was that my SW2016 admin image was trying to create a new instance
  of SQL server with a name that already existed.
  Like • Show 1 Like1
  Actions
- Peer Larson @ Nathan Hill on Feb 6, 2016 6:14 PM
  Mark Correct
  Correct Answer
  Hello Nathan,
  
  Thanks for paying your solution, that worked for as well (on a day the KB was down for maintenance too!). If this was the answer for you can you please mark the thread as solved, just so others know.
  
  Thanks!
  
  Peer
  Like • Show 0 Likes0
  Actions
Chris Saller Nov 25, 2015 2:04 PM
Mark Correct
Correct Answer
Download to the server folder, then run.
If creating the Admin Image from your PC: When it asks for the installation directory, it needs to be your local folder.
The Admin Image will install in the server folder.
I don't know why it's setup this way.
Like • Show 0 Likes0
Actions

2016 Administrative Image Install Failing

Attachments

Outcomes

Related Content

Recommended Content