• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

FOGUserService Net Framework error 64 bit machines

Scheduled Pinned Locked Moved Solved
FOG Problems
4
9
3.9k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • H
    Hanz
    last edited by Hanz Jan 7, 2016, 12:49 PM Jan 7, 2016, 6:42 PM

    I’m getting an error on 64 bit machines that have the new client installed.

    Error Parsing C:\Windows\Microsoft.NET\Framework\v4.030319\config\machine.config  
    Parser returned error 0x80070005.
    

    FOGUserService.exe-Configuration Parser Error is the name on the popup box.

    I know this is an issue with permissions, but not sure why it’s only happening on these 64 bit machines.

    The client is being installed via gpo if that helps. The error pops up immediately upon login.

    1 Reply Last reply Reply Quote 0
    • W
      Wayne Workman
      last edited by Wayne Workman Jan 7, 2016, 1:17 PM Jan 7, 2016, 7:17 PM

      Informing @Jbob about this.

      What version of FOG? What version of the new client? What OS is it going on?

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
      Daily Clean Installation Results:
      https://fogtesting.fogproject.us/
      FOG Reporting:
      https://fog-external-reporting-results.fogproject.us/

      1 Reply Last reply Reply Quote 0
      • J
        Joe Schmitt Senior Developer
        last edited by Jan 7, 2016, 8:50 PM

        How are you deploying .NET ? Is it via GPO? Part of the image?

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        H 1 Reply Last reply Jan 8, 2016, 12:41 PM Reply Quote 0
        • H
          Hanz @Joe Schmitt
          last edited by Hanz Jan 8, 2016, 6:58 AM Jan 8, 2016, 12:41 PM

          @Jbob I am installing the client via gpo as stated above. And I’d like to also mention that this issue only presents itself sometimes.

          G 1 Reply Last reply Jan 8, 2016, 1:36 PM Reply Quote 0
          • G
            george1421 Moderator @Hanz
            last edited by Jan 8, 2016, 1:36 PM

            @Hanz Do you have the same version and patch number of .Net deployed on all computers? Are you managing this?

            In my case, I’m loading the fog client as part of the imaging process. In this imaging process I install .Net into the reference image. That way I know for sure what release is deployed on the client. Then update .Net using WSUS.

            If you are going to push out the fog client via GPO (there are better methods, but that is for a different thread) you might want to push out a consistent and known .net version as a prerequisite before updating the client.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

            H 1 Reply Last reply Jan 8, 2016, 1:39 PM Reply Quote 0
            • H
              Hanz @george1421
              last edited by Hanz Jan 8, 2016, 7:47 AM Jan 8, 2016, 1:39 PM

              @george1421 That I’m not sure about honestly…What version should I be using ? I’ll have to work on adding a package to update .NET I guess. If I update the .Net framework after FOG, will this fix the issue ?

              G 1 Reply Last reply Jan 8, 2016, 2:12 PM Reply Quote 0
              • G
                george1421 Moderator @Hanz
                last edited by george1421 Jan 8, 2016, 8:17 AM Jan 8, 2016, 2:12 PM

                @Hanz I would ensure that .Net is at a consistent level for all of your computer fleet before updating the fog client. There are many reasons to take a cookie cutter approach to system images, the primary is “Fix it for one, fix it for all” when trying to repair bugs in systems. This way if you have one system different than the rest you can compare what is different to debug. From the error above it appears that you have .net 4.0 installed on this computer .

                Just for reference the above version of .Net [v4.030319] is from 2011, which may explain why the fog client is having a problem on this computer. Somewhere I remember that .Net 4.5 is required by the fog client (@jbob comments?).

                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                1 Reply Last reply Reply Quote 0
                • J
                  Joe Schmitt Senior Developer
                  last edited by Jan 8, 2016, 7:10 PM

                  The client is built with .NET 4.5, but can be run with .NET 3.5 or higher. @Hanz can you download the 0.9.10 debugger (https://github.com/FOGProject/fog-client/releases/download/0.9.10/Debugger.exe) and run it on a machine experiencing this issue. Be sure to not run it elevated (run it as a normal user). Do you get the same Error Parsing .... ?

                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                  H 1 Reply Last reply Jan 11, 2016, 3:14 AM Reply Quote 1
                  • H
                    Hanz @Joe Schmitt
                    last edited by Jan 11, 2016, 3:14 AM

                    @Jbob I’ll have to try tomorrow and let ya know.

                    1 Reply Last reply Reply Quote 0
                    • 1 / 1
                    1 / 1
                    • First post
                      3/9
                      Last post

                    197

                    Online

                    12.0k

                    Users

                    17.3k

                    Topics

                    155.2k

                    Posts
                    Copyright © 2012-2024 FOG Project