7 Replies Latest reply on Nov 27, 2018 8:20 PM by Bryan Riley

    2018 SP0.1 Web2

    Martin Solem
    Martin Solem Jan 11, 2018 7:27 AM

      Hey forum,

       

      I have a problem running 2018 SP0.1 Web2 on a new Windows Server 2016 virtual machine. Everything looks good, IIS is fine, i can access <webserver> but when i try to access <webserver>\SOLIDWORKSPDM (default) application pool, my browser just freezes, and on the server-side, the process w3wp.exe is using 97-100% CPU. The same thing happens if i try browsing on the server.

      Installation runs fine, files are in place, local view is in place, the whole thing is set up by the book and i have spent hours troubleshooting what causes this. Local client works fine, all users that i have tested have logged into the local vault view first. Registry looks OK. All rights to folders and the application pools has ben cross-checked countless times, firewall is shut off. I am at a dead end. I have also tried creating a new application pool, and even tried to remove and reinstall Web2 and IIS7.

      As a last resort i have set up a brand new 2016 server, which has only IIS and Web2 files installed, but i'm getting the exact same errors and behavior.

      There is nothing in the PDM Client log, but this from the Event Viewer:

       

      This appears when i kill the w3wp.exe process:

       

      A process serving application pool 'SOLIDWORKS PDM Web2' suffered a fatal communication error with the Windows Process Activation Service. The process id was '3660'. The data field contains the error number.

      Event ID: 5011

      -Reported from WAS

       

      Sometimes an error has been logged, right before i kill the w3wp.exe process, saying something like:

      The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

      {D63B10C5-BB46-4990-A94F-E40B9D520160}

      and APPID

      {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}

      to the user CCS-WEB-02\Administrator SID (S-1-5-21-1124329904-2597292670-2506141146-500) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

      -Reported from DistributedCOM

       

      I think have managed to fix these by adjusting Launch and Activation permissions in DCOMConfig, they belong to "Runtime broker" and there was another too, with just some Application ID.

       

       

      I am now on my 3rd webserver, and they are all acting the same way. Something is dead wrong here, and it could easily be me, but i cannot see what it is.

       

      Has anyone deployed Web2 successfully on a Win Server 2016, and/or is anyone aware of something the installation manual doesn't cover in Win Server 2016?

       

       

      Kind regards,

      Martin

        • Re: 2018 SP0.1 Web2
          Charley Saint
          Charley Saint Jan 10, 2018 8:01 AM (in response to Martin Solem)

          I haven't tried but I would suspect it's dependencies. I'd start with making sure ASP.NET is registered:

           

          How to register ASP.NET on Microsoft Windows Server 2016

            • Re: 2018 SP0.1 Web2
              Charley Saint
              Charley Saint Jan 9, 2018 5:49 PM (in response to Charley Saint)

              Or try the steps outlined in S-071653

              • Re: 2018 SP0.1 Web2
                Martin Solem
                Martin Solem Jan 10, 2018 10:13 AM (in response to Charley Saint)

                Thank you Charley,

                 

                I have done a couple things different on yet another webserver.

                I used the SOLIDWORKS Installation Manager to install the client and web2 server, to make sure all prereqs are in place.

                Then i ran the command for registering ASP.NET, which completed successfully.

                 

                The same thing happens - absolutely nothing, IE/Chrome is not responding, and w3wp.exe is taking up 97% of CPU.

                 

                As far as S-071653 goes, that is "not an option" in 2016:

                 

                Start installing ASP.NET (4.0.30319.0).

                This option is not supported on this version of the operating system.  Administrators should instead install/uninstall ASP.NET 4.5 with IIS8 using the "Turn Windows Features On/Off" dialog,  the Server Manager management tool, or the dism.exe command line tool.  For more details please see http://go.microsoft.com/fwlink/?LinkID=216771.

                Finished installing ASP.NET (4.0.30319.0).

                 

                And in Server 2016 it's IIS 10 and ASP.NET 4.6, so even that message seems outdated.

              • Re: 2018 SP0.1 Web2
                Miha Ravselj
                Miha Ravselj Jan 11, 2018 8:03 AM (in response to Martin Solem)

                I've had similar problem on Windows Server 2012R2:

                 

                I have into same issue with high CPU usage from w3wp.exe. I manage to solve the issue by checking Event viewer for errors. The cause for Web2 not working was the following:

                 

                Souce: Application Error

                 

                Faulting application name: OILink.exe, version: 8.5.3.0, time stamp: 0x5711461a

                Faulting module name: MSVCP120.dll, version: 6.3.9600.17415, time stamp: 0x5450559e

                Exception code: 0xc0000135

                Fault offset: 0x00000000000ec5a0

                Faulting process id: 0x74

                Faulting application start time: 0x01d38ac5d653ef75

                Faulting application path: C:\inetpub\wwwroot\SOLIDWORKSPDM\Web2\lib\OutsideInWebView\OILink.exe

                Faulting module path: MSVCP120.dll

                Report Id: 14138e61-f6b9-11e7-80d0-00155d008b07

                Faulting package full name:

                Faulting package-relative application ID:

                 

                It looks like there was a problem with MSVCP120.dll so I had to reinstall vcredist12( both x86 and x64). I don't know if both are needed but I installed them anyway. VC2013 wasn't listed in PDM prerequisites so I didn't install it but I think they should list it at least for web2. I am not sure if it was corrupt or missing but installing vcredist12 seems to have solved the issue for me.

                 

                Now Web2 app loads successfully.

                 

                Hope this helps.

                  • Re: 2018 SP0.1 Web2
                    Martin Solem
                    Martin Solem Jan 11, 2018 10:06 AM (in response to Miha Ravselj)

                    Hi, thank you. Unfortunately, my Eventlog has no recorded errors.:(

                    • Re: 2018 SP0.1 Web2
                      Martin Solem
                      Martin Solem Apr 6, 2018 4:43 AM (in response to Miha Ravselj)

                      Miha Ravsel,

                      I didn't try this immediately as i was creating an SR to SOLIDWORKS support at the same time, and wanted to have the error in case they wanted to have a look.

                       

                      They suggested i go through with your solution, and lo and behold, it works! Microsoft Visual C++ 2013 Redist. should DEFINITELY be on the prereq list for Web2.

                      Thank you so much, you have no idea how much time i spent on this!

                       

                      EDIT:

                      There is now an SPR for this:

                      SPR 1063460 - 'Update the Web2 Prerequisites in the installation guide with C++ 2013 Runtimes in order to use 2018 Web2 - Without them the Login page will hang and 'IIS Worker Process' shows high CPU'

                       

                      EDIT2:

                      SPR is implemented for 2018 SP3 release.

                       

                       

                      Martin

                    • Re: 2018 SP0.1 Web2
                      Bryan Riley
                      Bryan Riley Nov 27, 2018 8:20 PM (in response to Martin Solem)

                      Thank you, this fixed the same problem for me...