-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
InstallUtil exception on Windows Server 2008 #4
Comments
Can you please provide more information so that we can find the problem? In our environment we have Windows 2008 R2 without .NET 4.5 and installation works fine for us. |
I suggest running the command from where the DLL is rather than from the installutil.exe location. I think your DLL has a reference to webPages 2 DLL and when you run it from your current location it cannot load the DLL since it is not GACed. As I said, try running it from the location of your DLL. I checked and PefIt itself does not have a reference to WebPages 2 DLL. |
I have two Windows Server boxes. InstallUtil works on one and not the Both are 2008 R2 with SP1. Both have 4.5 installed. The box that works has the roles of Web Server and File Server. The box The box that works is not as up-to-date as the one that doesn't. I access the box that works using my domain account as an administrator. I run InstallUtil in the directory containing the dll that's the target. I ran InstallUtil with /showcallstack. Here is the output: An exception occurred during the Install phase. On Mon, Jul 29, 2013 at 5:25 PM, Ali Kheyrollahi
|
You need to use fuslogvw.exe: You might have to do this: That will tell you where it is looking for file and why it cannot find it. |
Working on getting it installed now. I have to get permission to install Thanks for your help. On Tue, Jul 30, 2013 at 11:40 AM, Ali Kheyrollahi
|
Just copy the file (fuslogvw.exe), that should be enough. It does not need anything else, that might be quicker [I know what pain it is to get access to boxes] |
Here is the fusion log output. It appears that it is only checking the GAC *** Assembly Binder Log Entry (7/30/2013 @ 1:55:47 PM) *** The operation failed. Assembly manager loaded from: === Pre-bind state information === Calling assembly : (Unknown).LOG: This bind starts in default load context. *** Assembly Binder Log Entry (7/30/2013 @ 1:55:47 PM) *** The operation failed. Assembly manager loaded from: === Pre-bind state information === Calling assembly : (Unknown).LOG: This bind starts in default load context. *** Assembly Binder Log Entry (7/30/2013 @ 1:55:48 PM) *** The operation failed. Assembly manager loaded from: === Pre-bind state information === PublicKeyToken=31bf3856ad364e35.LOG: This bind starts in default load context. On Tue, Jul 30, 2013 at 12:04 PM, Ali Kheyrollahi
|
OK, can you please set the fuslogvw.exe to log all events and try it on the machine that works and then compare? |
What is the command line you are running?
has
And I think this is the problem since the assembly is not known. |
The command line used is Below is the output from a successful install. The questionable assembly *** Assembly Binder Log Entry (7/31/2013 @ 1:13:34 PM) *** The operation was successful. Assembly manager loaded from: === Pre-bind state information === Calling assembly : (Unknown).LOG: This bind starts in default load context. *** Assembly Binder Log Entry (7/31/2013 @ 1:13:34 PM) *** The operation was successful. Assembly manager loaded from: === Pre-bind state information === PublicKeyToken=31bf3856ad364e35.LOG: This bind starts in default load context. *** Assembly Binder Log Entry (7/31/2013 @ 1:13:34 PM) *** The operation was successful. Assembly manager loaded from: === Pre-bind state information === PublicKeyToken=31bf3856ad364e35.LOG: This bind starts in default load context. *** Assembly Binder Log Entry (7/31/2013 @ 1:13:34 PM) *** The operation was successful. Assembly manager loaded from: === Pre-bind state information === PublicKeyToken=null.LOG: This bind starts in LoadFrom load context. On Wed, Jul 31, 2013 at 12:44 PM, Ali Kheyrollahi
|
OK, The one the works clearly has the assembly installed in GAC. My suggestion is to install MVC4 on the server that does not work. I think working server has it. |
I'll give that a shot. I was hoping that InstallUtil could be configured It might by a couple of days before I can install MVC4 on that machine. This is obviously an InstallUtil/machine setup issue and not a PerfIt On Wed, Jul 31, 2013 at 1:46 PM, Ali Kheyrollahi
|
Not a problem at all. I close the issue but happy to help on the thread. Please just add comments on this thread and I will be answering. |
It turns out that the machine already had MVC4 installed. I repaired the Thanks for your support and thanks for PerfIt. Best Regards, On Wed, Jul 31, 2013 at 2:52 PM, Ali Kheyrollahi
|
Great nice to hear that. Good luck! |
I can run installutil on my assemby on my developer box with no problem. However, on my production server I get the following output from InstallUtil:
An exception occurred during the Install phase.
System.IO.FileNotFoundException: Could not load file or assembly 'System.Web.We
bPages, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or o
ne of its dependencies. The system cannot find the file specified.
The text was updated successfully, but these errors were encountered: