configuration error

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • scottrm
    #1

    configuration error

    We have two developers, call them A and B, (on Windows XP) developing a
    number of asp.net web sites on a shared server (Windows 2003). Everything has
    been ok but recently for no apparent reason whenever developer A builds a
    particular project (which builds with no errors) and then tries to access the
    web site they just built they get the error below. Other projects built by
    the developer A are ok and also if the other developer, developer B, builds
    the same project the web site runs ok.

    Server Error in '/qssweb/bwsubs' Application
    --------------------------------------------------------------------------------

    Configuration Error
    Description: An error occurred during the processing of a configuration file
    required to service this request. Please review the specific error details
    below and modify your configuration file appropriately.

    Parser Error Message: Access is denied: 'Microsoft.Appl icationBlocks.D ata'.

    Source Error:


    Line 256: <add assembly="Syste m.EnterpriseSer vices,
    Version=1.0.500 0.0, Culture=neutral , PublicKeyToken= b03f5f7f11d50a3 a"/>
    Line 257: <add assembly="Syste m.Web.Mobile,
    Version=1.0.500 0.0, Culture=neutral , PublicKeyToken= b03f5f7f11d50a3 a"/>
    Line 258: <add assembly="*"/>
    Line 259: </assemblies>
    Line 260:


    Source File:
    c:\windows\micr osoft.net\frame work\v1.1.4322\ Config\machine. config Line:
    258

    Assembly Load Trace: The following information can be helpful to determine
    why the assembly 'Microsoft.Appl icationBlocks.D ata' could not be loaded.


    === Pre-bind state information ===
    LOG: DisplayName = Microsoft.Appli cationBlocks.Da ta
    (Partial)
    LOG: Appbase = file:///C:/WebSites/1005/root/QSSWeb/BWSubs
    LOG: Initial PrivatePath = bin
    Calling assembly : (Unknown).
    ===

    LOG: Policy not being applied to reference at this time (private, custom,
    partial, or location-based assembly bind).
    LOG: Post-policy reference: Microsoft.Appli cationBlocks.Da ta
    LOG: Attempting download of new URL
    file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET
    Files/qssweb_bwsubs/63c7d454/13bd7b22/Microsoft.Appli cationBlocks.Da ta.DLL.
    LOG: Attempting download of new URL
    file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET
    Files/qssweb_bwsubs/63c7d454/13bd7b22/Microsoft.Appli cationBlocks.Da ta/Microsoft.Appli cationBlocks.Da ta.DLL.
    LOG: Attempting download of new URL
    file:///C:/WebSites/1005/root/QSSWeb/BWSubs/bin/Microsoft.Appli cationBlocks.Da ta.DLL.
    LOG: Policy not being applied to reference at this time (private, custom,
    partial, or location-based assembly bind).
    LOG: Post-policy reference: Microsoft.Appli cationBlocks.Da ta,
    Version=2.0.0.0 , Culture=neutral , PublicKeyToken= null




    --------------------------------------------------------------------------------
    Version Information: Microsoft .NET Framework Version:1.1.432 2.2032; ASP.NET
    Version:1.1.432 2.2032




    --
    Scott
    Tags: None
    • JP.Sklenka
      #2
      RE: configuration error

      Here are a couple of recommendations :
      1) Developers should be developing/debugging locally and deploying to
      Dev/QA/Prod servers and not developing directly against them.
      2) Are Dev A and Dev B using the same build configuration when they build?
      I had one member of my team decide to create his own config that excluded App
      Blocks from the build (we're using project references) and he ran into the
      same issue.
      3) Are your devs referencing the Data Block assembly or project reference?
      4) Typically you'll have a build manager or build machine that pulls the
      latest tested code out of source safe, perform a build, and then deploy to
      your target server.

      "scottrm" wrote:
      [color=blue]
      > We have two developers, call them A and B, (on Windows XP) developing a
      > number of asp.net web sites on a shared server (Windows 2003). Everything has
      > been ok but recently for no apparent reason whenever developer A builds a
      > particular project (which builds with no errors) and then tries to access the
      > web site they just built they get the error below. Other projects built by
      > the developer A are ok and also if the other developer, developer B, builds
      > the same project the web site runs ok.
      >
      > Server Error in '/qssweb/bwsubs' Application.
      > --------------------------------------------------------------------------------
      >
      > Configuration Error
      > Description: An error occurred during the processing of a configuration file
      > required to service this request. Please review the specific error details
      > below and modify your configuration file appropriately.
      >
      > Parser Error Message: Access is denied: 'Microsoft.Appl icationBlocks.D ata'.
      >
      > Source Error:
      >
      >
      > Line 256: <add assembly="Syste m.EnterpriseSer vices,
      > Version=1.0.500 0.0, Culture=neutral , PublicKeyToken= b03f5f7f11d50a3 a"/>
      > Line 257: <add assembly="Syste m.Web.Mobile,
      > Version=1.0.500 0.0, Culture=neutral , PublicKeyToken= b03f5f7f11d50a3 a"/>
      > Line 258: <add assembly="*"/>
      > Line 259: </assemblies>
      > Line 260:
      >
      >
      > Source File:
      > c:\windows\micr osoft.net\frame work\v1.1.4322\ Config\machine. config Line:
      > 258
      >
      > Assembly Load Trace: The following information can be helpful to determine
      > why the assembly 'Microsoft.Appl icationBlocks.D ata' could not be loaded.
      >
      >
      > === Pre-bind state information ===
      > LOG: DisplayName = Microsoft.Appli cationBlocks.Da ta
      > (Partial)
      > LOG: Appbase = file:///C:/WebSites/1005/root/QSSWeb/BWSubs
      > LOG: Initial PrivatePath = bin
      > Calling assembly : (Unknown).
      > ===
      >
      > LOG: Policy not being applied to reference at this time (private, custom,
      > partial, or location-based assembly bind).
      > LOG: Post-policy reference: Microsoft.Appli cationBlocks.Da ta
      > LOG: Attempting download of new URL
      > file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET
      > Files/qssweb_bwsubs/63c7d454/13bd7b22/Microsoft.Appli cationBlocks.Da ta.DLL.
      > LOG: Attempting download of new URL
      > file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET
      > Files/qssweb_bwsubs/63c7d454/13bd7b22/Microsoft.Appli cationBlocks.Da ta/Microsoft.Appli cationBlocks.Da ta.DLL.
      > LOG: Attempting download of new URL
      > file:///C:/WebSites/1005/root/QSSWeb/BWSubs/bin/Microsoft.Appli cationBlocks.Da ta.DLL.
      > LOG: Policy not being applied to reference at this time (private, custom,
      > partial, or location-based assembly bind).
      > LOG: Post-policy reference: Microsoft.Appli cationBlocks.Da ta,
      > Version=2.0.0.0 , Culture=neutral , PublicKeyToken= null
      >
      >
      >
      >
      > --------------------------------------------------------------------------------
      > Version Information: Microsoft .NET Framework Version:1.1.432 2.2032; ASP.NET
      > Version:1.1.432 2.2032
      >
      >
      >
      >
      > --
      > Scott[/color]

        Comment

        • Steven Cheng[MSFT]
          #3
          RE: configuration error

          Thanks for JPSklenka's informative inputs.

          Hi Scott,

          In addition to JPSklenka's suggestions. Here are some of my suggestion:

          From the error info you provided, the ACCESS DENIED error seems caused by
          the DataAccess Application Block's assembly can't be correctly load. I
          think the project (with error) must have referenced the DAAB's assembly ,
          yes? And is the DAAB assembly referenced in your project a strong-named
          version? If so, have you put it in the server's GAC or just directly use it
          in the web project's private bin path? There is a known issue that
          strongnamed assembly must be put in GAC when used in asp.net web
          application. Please have a check , if there are any other new findings
          ,please feel free to post here.

          Thanks.

          Regards,

          Steven Cheng
          Microsoft Online Support

          Get Secure! www.microsoft.com/security
          (This posting is provided "AS IS", with no warranties, and confers no
          rights.)

            Comment

            • scottrm
              #4
              RE: configuration error

              Thanks for your reply.

              In response to JP Sklenka dev a and b are using the same build configuration
              and neither of them changed anything before the problems occurred. We are
              referencing by project but that has worked fine before as did working on a
              shared server.

              I don't think the error is specific to the data access application block
              because previously I got the same error with a different assembly which I
              removed because it was no longer in use, but as soon as I removed it I got
              the same error with the DAAB so I guess none of the assemblies could be
              loaded.

              Bizzarely the problem seems to have fixed itself without any changes or even
              a reboot. I would still be interested to know if you have any more ideas in
              case it happens again.

              "Steven Cheng[MSFT]" wrote:
              [color=blue]
              > Thanks for JPSklenka's informative inputs.
              >
              > Hi Scott,
              >
              > In addition to JPSklenka's suggestions. Here are some of my suggestion:
              >
              > From the error info you provided, the ACCESS DENIED error seems caused by
              > the DataAccess Application Block's assembly can't be correctly load. I
              > think the project (with error) must have referenced the DAAB's assembly ,
              > yes? And is the DAAB assembly referenced in your project a strong-named
              > version? If so, have you put it in the server's GAC or just directly use it
              > in the web project's private bin path? There is a known issue that
              > strongnamed assembly must be put in GAC when used in asp.net web
              > application. Please have a check , if there are any other new findings
              > ,please feel free to post here.
              >
              > Thanks.
              >
              > Regards,
              >
              > Steven Cheng
              > Microsoft Online Support
              >
              > Get Secure! www.microsoft.com/security
              > (This posting is provided "AS IS", with no warranties, and confers no
              > rights.)
              >
              >[/color]

                Comment

                • Steven Cheng[MSFT]
                  #5
                  RE: configuration error

                  Hi Scott,

                  Thanks for your response. If the problems went away without doing anything,
                  I'm afraid it must still exists, but not occur currently. The DAAB I
                  mentioned in the last message just means strong-named assembly , if there
                  are any strong-named assemblies used in your asp.net project and are put in
                  the private bin path, please move them to the GAC , that sometimes will
                  cause such unexpected problems.

                  Thanks.

                  Regards,

                  Steven Cheng
                  Microsoft Online Support

                  Get Secure! www.microsoft.com/security
                  (This posting is provided "AS IS", with no warranties, and confers no
                  rights.)

                    Comment

                    Previous template Next
                    Working...