locked
server error (runtime) when uploading VS 2019 template RRS feed

  • Question

  • User1396030708 posted

    hello all,

    I have GoDaddy as a hosting company and others have complained about this before.  Attached is an image of what I see.  This is the "default.aspx" page from a web forms template created with VS 2019.  no code was modified before upload.  this is just a test run to see if GoDaddy is risky to run ASP.NET apps on their IIS servers.  Has anyone seen this before?  I have tried 3 different fixes, and every attempt has followed the instructions listed in the new error message that pops up on the page.  The attached image shows the very first error seen when first attempting to run the app after uploading the unmodified template.  Can anyone assist me where to look to solve this?  The hosting company agents provided no value, but I did manage to talk to someone who was willing to try.

    thanks.

    Adam

    template_server_error

    https://drive.google.com/file/d/1BbJykY4E6exeDx6iajTffDXOI3zwe9Nz/view?usp=sharing

    Wednesday, August 12, 2020 1:48 PM

All replies

  • User-1330468790 posted

    Hi ajetrumpet,

     

    Sorry that I can not see the error image.

    Could you please post the error message in this thread directly?

    If you want to attach picture in the thread, you could refer to this thread: Insert picture

      

    Best regards,

    Sean

    Thursday, August 13, 2020 3:13 AM
  • User1396030708 posted

    thank you so much for responding Sean.  I do not like Microsoft because of this stuff, but I just think VS is so complicated and hosting companies run so much automation, that those 2 things combined makes life a living he$$.  I have gone through 5 different errors after trying 5 different solutions from various goog searches and forum finds.  every solution posted results in a different error.  Here is the relevant XML config code I am currently running inside the compiled and uploaded template, I believe:

    <configuration>
      <system.web>
        <trust level="Full"/>
        <customErrors mode="Off"/>
        <compilation strict="false" explicit="true" targetFramework="4.8" />
        <httpRuntime targetFramework="4.8" />
        <pages>
    .......................

    Here is the part of the error message that is relevant (the entire message is one huge stack trace.  but everytime I've seen that happen, there has been only one source issue that causes the dominoes):

    Exception Details: System.ComponentModel.Win32Exception: This program is blocked by group policy. For more information, contact your system administrator

    and the first line of the trace is this:

    [ExternalException (0x80004005): Cannot execute a program. The command being executed was "G:\PleskVhosts\website.com\httpdocs\bin\roslyn\vbc.exe" /shared /keepalive:"10" /noconfig @"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\05f594c0\e3f54f3c\ibiq1uj2.cmdline".]

    I really appreciate your help.  I was hoping to get a response from a veteran.  I'm obviously a beginner.

    Adam

    Thursday, August 13, 2020 3:26 AM
  • User1396030708 posted

    oh, and one other thing Sean.  GoDaddy claims that there is an issue with the ""vbc.exe"" file inside this path that resulted from the build inside VS:

    ""root\bin\roslyn""

    do you think that is even relevant?  hosting companies are notorious the world over for not knowing anything.  thanks.  =)

    Thursday, August 13, 2020 3:46 AM
  • User-1330468790 posted

    Hi ajetrumpet,

     

    It is not related to your codes which, I guess, is working from your side normally. 

    I think that go-daddy disabled compiling on their servers so no malicious code can somehow be inserted and compiled/executed.

     

    Since it is possible to upload your site to your hosting without compiling it. Then the site will be compiled on the initial request using the compiler settings as seen in the web.config.

    If you pre-compile your site but still have code in the App_code folder those settings will be used to compile that code.

    If you don't use the App_code folder and you pre-compile your website you can delete/comment the below web.config section.

    <system.codedom>
      <compilers>
        <compiler language="c#;cs;csharp" extension=".cs"
          type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
          warningLevel="4" compilerOptions="/langversion:6 /nowarn:1659;1699;1701"/>
       <compiler language="vb;vbs;visualbasic;vbscript" extension=".vb"
          type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.VBCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
          warningLevel="4" compilerOptions="/langversion:14 /nowarn:41008 /define:_MYTYPE=\&quot;Web\&quot; /optionInfer+"/>
      </compilers>
    </system.codedom>

     

    Best regards,

    Sean

    Monday, August 17, 2020 8:41 AM
  • User1396030708 posted

    Sean,,

    I have 2 folders in the directory where my uncompiled application sits.  and in one folder there is nothing, in the other one, named ""App_Start"", there are 2 files.  I assume this is normal?  the 2 files in that dir are BundleConfig.vb and RouteConfig.vb.  are either of these files used in my folder, that you are talking about that would otherwise be used in the folder ""App_code"", if I had one?

    per your other words:

    If you don't use the App_code folder and you pre-compile your website you can delete/comment the below web.config section.

    <system.codedom>
      <compilers>
        <compiler language="c#;cs;csharp" extension=".cs"
          type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
          warningLevel="4" compilerOptions="/langversion:6 /nowarn:1659;1699;1701"/>
       <compiler language="vb;vbs;visualbasic;vbscript" extension=".vb"
          type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.VBCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
          warningLevel="4" compilerOptions="/langversion:14 /nowarn:41008 /define:_MYTYPE=\&quot;Web\&quot; /optionInfer+"/>
      </compilers>
    </system.codedom>

     

    I pre-compiled this application, uploaded everything to the root dir (which did NOT include an ""App_code"" folder, and I got the following error.  this is the same original error I got when I tried to upload the compiled version.  I fixed every error, one at a time, through google searches, but after I got to error #3 I quit. 

    error_again_after_Sean_upload

    https://drive.google.com/file/d/1RlDlHib6_2A2UApEyXWyhZsaNFGE5Z_B/view?usp=sharing

    Monday, August 17, 2020 5:35 PM
  • User409696431 posted

    That error is just telling you that it won't show you the error, and giving you modifications to the web.config so that it will show you the error.

    Monday, August 17, 2020 9:45 PM
  • User1396030708 posted

    That error is just telling you that it won't show you the error, and giving you modifications to the web.config so that it will show you the error.

    Kathy, I realize that.  however, if you look at my previous replies, you would see that I said I already went through this.  this original error (in the goog cloud drive link), when fixed per the instructions in the error itself, results in error after error.  and with each error that results, I have followed the instructions in it to fix the error, but following those instructions only results in other errors.  again, time after time.  like I told Sean, after fixing 3 subsequent errors in a row, I gave up.  this is a SIMPLE visual studio 2019 template.  I would have assumed that even a hosting company's shared server would not block that if uploaded properly.  correct?

    Tuesday, August 18, 2020 2:34 AM
  • User409696431 posted

    You posted that link, which shows you didn't change the web.config to show the error.

    If you fixed the web.config to show the error, why post that link?  Instead post the actual error you are still getting.

    Adding: What VS2019 template are you using, and what asp.net framework does it target?  Does your GoDaddy account support it?   Since you posted this in a  Webforms section, I find it hard to imagine they don't, but it's worth asking.

    Tuesday, August 18, 2020 3:32 AM
  • User1396030708 posted

    Adding: What VS2019 template are you using, and what asp.net framework does it target?  Does your GoDaddy account support it?

    i am seriously new to the .NET framework in general.  godaddy has to support it, because literally everyone in the world is obsessed with using the .NET framework.  I have no idea why.  and most small businesses use hosting companies.

    I am using .NET 4.8 in the VS template.  However, the Plesk backend dashboard at GoDaddy says the version of .NET that is running is 4.8.xx.  does this matter?  I would think not.

    If you can answer those questions I would appreciate it.  Then I will post images of all 3 subsequent errors I am getting after fixing each per the instructions.  I still have them on my machine in a dir.  thanks Kathy.

    Tuesday, August 18, 2020 3:47 AM
  • User409696431 posted

    Post the error you are still getting.  No one can help without that.

    Supporting asp,.net doesn't mean every host supports all frameworks and all variations.  "Asp.Net" is a rather large field now.  But for WebForms, if your account version is the same as the one you are targeting in Visual Studio, that should work.

    Also, how are you publishing?   FTP?  WebDeploy?

    If using FTP, what are the settings in the Publishing Profile you set up?  If it's set to precompile during publishing, as it should be, you should upload only the files that are needed, after compiling the application.  You don't upload all your files.   If you use WebDeploy (which needs to be enabled on GoDaddy), it will know which files need to be uploaded.

    Tuesday, August 18, 2020 4:29 AM
  • User932909087 posted

    KathyW

    That error is just telling you that it won't show you the error, and giving you modifications to the web.config so that it will show you the error.

    Kathy, I realize that.  however, if you look at my previous replies, you would see that I said I already went through this.  this original error (in the goog cloud drive link), when fixed per the instructions in the error itself, results in error after error.  and with each error that results, I have followed the instructions in it to fix the error, but following those instructions only results in other errors.  again, time after time.  like I told Sean, after fixing 3 subsequent errors in a row, I gave up.  this is a SIMPLE visual studio 2019 template.  I would have assumed that even a hosting company's shared server would not block that if uploaded properly.  correct?

    Hi Ajet,

    Unable to see your error here. Please post what is the error message here. Have you contacted your support team? 

    Tuesday, August 18, 2020 4:43 AM
  • User1396030708 posted

    KathyW

    Also, how are you publishing?   FTP?  WebDeploy?

    If using FTP, what are the settings in the Publishing Profile you set up?  If it's set to precompile during publishing, as it should be, you should upload only the files that are needed, after compiling the application.  You don't upload all your files.   If you use WebDeploy (which needs to be enabled on GoDaddy), it will know which files need to be uploaded.

    ok you guys, thanks for replying!  what I'm really trying to find out here is just how complicated this .NET framework really is.  I patternize literally *everything* I write with regard to code.  and I don't think that tactic will work with something like this.

    Kathy, I am using filezilla for my FTP client.  I literally did not do anything in VS in terms of compiling it, debugging or anything else.  There is so much stuff included in a SIMPLE template from VS, that there's 650+ files the program spits out when a template is created!  that's just ridiculous.  I have never worked with a huge framework before, and I despise them completely.  I know all professional programmers use them, but I am more of a manager and leader.  So, per your request Kathy, here are the 3 different images I get, one after the other:

    1) https://drive.google.com/file/d/1Hehl62yQftc4uOr00tZFaoOjTmGmOH_f/view?usp=sharing

    2) https://drive.google.com/file/d/1f0raqfmH3-HGxLi8HSGLZIV1Fypjb9Ig/view?usp=sharing

    and after that #2 error I searched google for it:  https://www.google.com/search?q=System.Security.SecurityException%3A+Request+failed+.net+template , and tried the solution in answer #2 here: https://stahttps://stackoverflow.com/questions/11524582/system-security-securityexceptionckoverflow.com/questions/11524582/system-security-securityexception

    and of course, full trust results in this:

    3) https://drive.google.com/file/d/1qDFMz7hBFJPsK1C5xbrSyi_9lnkTFiMk/view?usp=sharing

    oh, and Masterpiece, I do not work for any given company.  I have no support team. 

    Tuesday, August 18, 2020 7:13 AM
  • User409696431 posted

    "Kathy, I am using filezilla for my FTP client. "

    Why?  Visual Studio will publish for you.  You don't need Filezilla.  And if you used Filezilla and uploaded all the files, you uploaded files that shouldn't be there in a pre-compiled web application.

    "I literally did not do anything in VS in terms of compiling it, debugging or anything else."

    That's your problem.  You don't know how to use VS.  You compile the application, then test it locally by previewing in a browser.  You publish using VS with the the release version selected so you get the right files.  You don't just publish all the files.  And the roslyn errors mean you didn't pre-compile it, and it's trying to run that on the server and GoDaddy won't let you.

    Adding some details: the "Build" menu lets you compile the application.  Before publishing, set the dropdown below/near the Build menu to Release.  Then, Build -> Build Solution.  Using the template, it should build without errors.  Publishing your application is also handled in the Build menu.  Build -> Publish.  That will open a page where you put in your publishing profile (or profiles if you want to publish using different methods or to different locations, such as a staging server vs a production server).  When you've set up your publishing profile,  validate the connection, and publish your site with the Release build.  The necessary files, including the compiled part of the site now in the bin folder, will be published.  Before doing this, you might want to clear out the files in your site that you published with Filezilla.  Start fresh.

    And as for " I have never worked with a huge framework before, and I despise them completely. I know all professional programmers use them, but I am more of a manager and leader."  Asp.net is not for a non-coder, or someone who hasn't got the time to learn it.  Expect it to take time, and follow tutorials rather than just plowing ahead.  (Or hire someone to create the application you need.)

    Tuesday, August 18, 2020 8:12 AM
  • User1396030708 posted

    And as for " I have never worked with a huge framework before, and I despise them completely. I know all professional programmers use them, but I am more of a manager and leader."  Asp.net is not for a non-coder, or someone who hasn't got the time to learn it.  Expect it to take time, and follow tutorials rather than just plowing ahead.  (Or hire someone to create the application you need.)

    I very much appreciate your last post Kathy.  it was extremely valuable.  thanks!  and, the reason I posted here was in hopes that I could talk to someone like you.  tutorials are not needed if professionals like yourself are willing to tell me what any given platform is all about.  you have now told me enough to where I can bypass pretty much any tutorial I have ever seen.   (I have seen some on VS 2019 and many others).  the post also was more or less about trying to understand, if by some miracle I ever did need to use this stuff from MS, I know what it is all about.  I hope you follow what I'm saying.

    I will give it a go and report back to you very soon if I run into any other issues.  once again, thank you so much.  =)  (by the way, I ask questions like this, some easy some difficult on many internet forums (20 different ones to be exact), because I'm a firm believer in the notion that veterans in any given discipline / platform can give me the knowledge needed in ''x'' short hours or days that it would take me a lifetime to learn from any college / book / tutorial).  have a good day.

    Adam

    Tuesday, August 18, 2020 12:59 PM
  • User409696431 posted

    Please mark posts that answer your problem as the answer (or answers).  That highlights that post for future readers.

    Tuesday, August 18, 2020 3:17 PM
  • User1396030708 posted

    KathyW

    Please mark posts that answer your problem as the answer (or answers).  That highlights that post for future readers.

    I will do that Kathy, as soon as I run the appropriate tests on the server based on everything that you have said.  I have yet to do that, and when I do you will get a message here from me about the success or failure.  If I need further assistance, I will ask you or masterpiece.  thanks.

    Tuesday, August 18, 2020 3:35 PM
  • User1396030708 posted

    Kathy,

    I have now followed your instructions to the letter, and I did see the compilations in the BIN folder.  obviously binaries are needed, right?  Whopsie!  I should've recognized that before.  Almost everything I've seen compiled in 20 years of doing this has had a BIN folder, so I apologize for not recognizing that. 

    regarding your process, when I actually did the BUILD from the BUILD menu, it automatically published the solution in the \Release\Publish folder.  so apparently your 2nd process was not even necessary.  I was unaware of this.  However, I still tried to formally publish it after building it, and the default dir was still \Release\Pulbish.  So naturally I assumed that VS had already done the necessary work for me.

    and unfortunately, after I went through this process and uploaded all of the resulting files to the server with GoDaddy, it reverted right back to the exact same error I got the first time around days ago.  here is the error:

    https://drive.google.com/file/d/19GLA61PErYmJoteOzjF0RC-9p1hJ6Y1p/view?usp=sharing

    https://drive.google.com/file/d/19GLA61PErYmJoteOzjF0RC-9p1hJ6Y1p/view?usp=sharing

    Sunday, August 23, 2020 1:17 AM
  • User409696431 posted

    What I did, following my actual instructions, works when publishing to my host.  If it doesn't work for you, you've done something wrong.  (Including: did you remove all the files on GoDaddy before trying again, per my instructions?  Did you set up publishing instructions for GoDaddy in VS, and use VS to publish, not an external FTP client?)

    Also, "same error" is useless when you are not showing the actual error.  That page, again, is just telling you that something is wrong and you need to modify the web.config to see the actual error.  You haven't followed the instructions to show the actual error.

    Sunday, August 23, 2020 10:03 PM
  • User1396030708 posted

    What I did, following my actual instructions, works when publishing to my host.  If it doesn't work for you, you've done something wrong.  (Including: did you remove all the files on GoDaddy before trying again, per my instructions?  Did you set up publishing instructions for GoDaddy in VS, and use VS to publish, not an external FTP client?)

    I appreciate you sticking with me through this Kathy.  I've been a developer for 12 years but this is the first time I am staring to use what the professionals call "frameworks".  I'm sure you understand that.  So, to answer your question, the following link shows the dir structure I see when VS builds and publishes the solution for me, per your instructions on how to do it through the menu:

    https://drive.google.com/file/d/1-q3ZAq99FSA34zFibIxRY5cN2Qx6m9Yn/view?usp=sharing

    can you see that image?  that is the actual DIR content that I uploaded to the shared hosting server in the root dir.  and yes, to upload all of that I did use an FTP client.  Filezilla.  I have yet to explore all of the buttons and menus to click in VS.  And per what GoDaddy told me (coming from their developers, who, IMO, have never been the smartest people in the world), they said this:

    based on what you have in your GLOBAL.ASAX file and WEB.CONFIG file, your application will not run on a shared server. 

    They provided no information other than that, because technically it is out of their scope of support.  And I'm pretty sure they wouldn't know how to answer questions like this anyway.  But, maybe I'm wrong.

    So, based on what I've said, I'm assuming my process is still in error?  once again, thanks.

    Adam

    Sunday, August 23, 2020 11:03 PM
  • User409696431 posted

    My test was on a shared server.  I can't help you with GoDaddy.  I never host with them.

    Also, you never answered if you used the same process as I did, if you set up publishing inside VS, and if you first removed all the files you FTP'd up there before publishing.

    Sunday, August 23, 2020 11:46 PM
  • User1396030708 posted

    Also, you never answered if you used the same process as I did, if you set up publishing inside VS, and if you first removed all the files you FTP'd up there before publishing.

    yes, I removed all the files from the server that I had uploaded via the FTP client.  as for publishing inside of VS, the only thing I did, which I explained in a previous post, is the following:

    => built the solution by way of clicking on the ""build menu => build option""
    => published the solution by way of clicking on the ""build menu => publish option""

    is there anything more to it than that?  is there some sort of publishing profile I have to set up in VS?

    Sunday, August 23, 2020 11:51 PM
  • User409696431 posted

    "is there some sort of publishing profile I have to set up in VS?"  Yes, as I said in my earlier reply.

    What did you set up for the publishing configuration?   FTP or WebDeploy?  Also, did you make any changes from the template itself?  You describe, earlier, making changes to try and fix errors.

    And, once again, what is the actual error showing now, not the "you have an error and we can't tell you what it is" page?

    Monday, August 24, 2020 12:30 AM
  • User1396030708 posted

    And, once again, what is the actual error showing now, not the "you have an error and we can't tell you what it is" page?

    when I pushed the ""publish"" button in the "'build"" menu, it did not give me any dialog for options.  It just simply ran a process in the background and I saw the result in the process log in the bottom window frame.  the same place where you see the words ""build started ...... success, etc....""

    in terms of showing you the errors, you still have not yet told me whether you can see the images when I post links to them on the google cloud drive.  can you?  if not, how do you want me to show you?  there are 3 errors that happen, one after another, when I follow the instructions in every error printout as to how to solve the current issue.  like I said, after 3 fix attempts, I gave up.  I can post images any way you, however the ""image"' button on this forum doesn't seem to result in the actual image showing in a post, even though there is a "source link" argument in the dialog when inserting an image here.

    Monday, August 24, 2020 1:12 AM
  • User409696431 posted

    As I already said, your error link is not useful.  You have to change the web.config to show the real error.

    Also, you didn't answer: did you make changes to the default template?  If GoDaddy says the Global.asax and web.config are problematic, did you make any changes there?

    As for not having any options for publishing, there is no way it would publish to GoDaddy unless you set up the publishing options for GoDaddy.

    Monday, August 24, 2020 1:38 AM
  • User1396030708 posted

    Also, you didn't answer: did you make changes to the default template?  If GoDaddy says the Global.asx and web.config are problematic, did you make any changes there?

    As for not having any options for publishing, there is no way it would publish to GoDaddy unless you set up the publishing options for GoDaddy.

    1) I did NOT make any changes to the template, no.  this was simply a test to see how VS and the entire .NET platform works.  that's the entire point of this.  I will be getting work from other people and they will want me to understand .NET very well.  thus, this whole process is necessary.

    2) and what exactly do you mean by ""publish to GoDaddy""??  and what about ""publishing options for GoDaddy""??  are you saying that I should have seen a file dialog after pushing the ""publish"" button in the ""build"" menu?  if that's what you mean, maybe the following link will help you.  I recorded the entire process of "publishing" the web application using the game bar with windows 10.  does this help you help me?

    thanks Kathy.

    Adam

    <edit>

    OK, for some reason I need to go through the configuration of a publishing profile.  I did not see that last time and I don't know why!  the "publish" dir just appeared after clicking the menu option.  so.....here is the video (mp4 format):

    https://drive.google.com/file/d/1goBoeqqBCa-lkK8yWcQer6BSQYsdWP2f/view?usp=sharing

    Monday, August 24, 2020 1:52 AM
  • User409696431 posted

    The video doesn't show you clicking the Start button.  So it doesn't show publishing.

    In any event, if unmodified Global.asax and Web.config files cause GoDaddy to say it won't run in your account, it means you are out of luck.  I have no idea what they don't support.  The actual error message might give a hint, if the pre-compiled site was actually published.

    The Publish dir doesn't mean it has published.  That's an intermediate step before publishing.

    Monday, August 24, 2020 1:59 AM
  • User1396030708 posted

    The actual error message might give a hint, if the pre-compiled site was actually published.

    so does that mean that I am left to figure out how to publish the site on my own by navigating through the publishing menu and figuring out what is what?  and can you tell me what publishing with an FTP spec vs. a WebDeploy spec does?  what's the difference?  and what kind of output in a dir will I see with one over the other?

    Monday, August 24, 2020 2:12 AM
  • User409696431 posted

    I have no more time to spend on this tonight.  Click the start button on publishing and go through it.  If you don't have webdeploy set up on GoDaddy, use FTP.    The difference between the two is that WebDeploy is smarter about republishing after making changes and could also handle publishing a database if you had one.

    Monday, August 24, 2020 2:21 AM
  • User1396030708 posted

    I will handle it Kathy.  don't worry about it.  you've already spent enough time.  I will repost later on with results of what I will go through the publishing interface.  thank you for dedicating as much time as you have thus far with this.  I really didn't expect this much.  no one else ever gives this much effort.  =)

    Monday, August 24, 2020 2:32 AM