ASP.NET Compilation Error on Windows Server 2019 with .NET 4.8 and IIS10

Question

ASP.NET Compilation Error on Windows Server 2019 with .NET 4.8 and IIS10

DmitriyKobrinskiy-0284 0

Hello folks,

I have strange behavior when migrating from ws2016 to ws2019. Both servers are supposed to host a WCF service, but the service is not running on the 2019.

Error output is also not particularly informative. We already did a clean install (2019) but it didn't help.

error

Thanks!

Sam Wu-MSFT 7,566 Reputation points Microsoft External Staff

2023-04-04T03:37:39.3666667+00:00

@DmitriyKobrinskiy-0284 It is difficult to reproduce your problem based on your description, you can get more error messages in the Event Viewer, if not, you can try to debug the cause using IIS Debug Diagnostics Tool, this tool will generate detail log file, which will help you to identify the problem.
DmitriyKobrinskiy-0284 0 Reputation points

2023-04-04T17:51:58.2166667+00:00

@Sam Wu-MSFT Whichever method we use, the Eventlog, the Solution compilation in the Visual Studio environment, the error is same - CS1504. Compiler Error CS1504 Source file 'file' could not be opened ('reason') A source file could not be opened or read by the compiler. The file may be locked by another application, or there could be some other operating system problem. The message includes the operating system's reason for why the compiler could not open or read the file. As you can see in the figure, the cause is an "unknown error". How the hell, do we deal with that. The question is rhetorical, I asked earlier, maybe anyone has already faced such a situation.
Sam Wu-MSFT 7,566 Reputation points Microsoft External Staff

2023-04-05T09:50:08.8333333+00:00

@DmitriyKobrinskiy-0284 These error messages cannot reproduce your problem, you still need to use IIS Debug Diagnostics Tool to troubleshoot your problem.
DmitriyKobrinskiy-0284 0 Reputation points

2023-04-06T05:35:11.66+00:00

@Sam Wu-MSFT All that is needed here is to think logically. If I have the ability to debug the compilation process in the vs environment, why complicate it? Which in the end will not clarify anything.
Sam Wu-MSFT 7,566 Reputation points Microsoft External Staff

2023-04-06T09:31:45.9666667+00:00

@DmitriyKobrinskiy-0284 If you want to find out the problem, it is not enough to just think logically. From 2016 to 2019, you can't be sure what content will affect this, so what we need to do is to get more information to troubleshoot the issue.

1 answer

Your answer

Sam Wu-MSFT 7,566 Reputation points Microsoft External Staff

2023-04-04T03:37:39.3666667+00:00

@DmitriyKobrinskiy-0284 It is difficult to reproduce your problem based on your description, you can get more error messages in the Event Viewer, if not, you can try to debug the cause using IIS Debug Diagnostics Tool, this tool will generate detail log file, which will help you to identify the problem.
DmitriyKobrinskiy-0284 0 Reputation points

2023-04-04T17:51:58.2166667+00:00

@Sam Wu-MSFT Whichever method we use, the Eventlog, the Solution compilation in the Visual Studio environment, the error is same - CS1504. Compiler Error CS1504 Source file 'file' could not be opened ('reason') A source file could not be opened or read by the compiler. The file may be locked by another application, or there could be some other operating system problem. The message includes the operating system's reason for why the compiler could not open or read the file. As you can see in the figure, the cause is an "unknown error". How the hell, do we deal with that. The question is rhetorical, I asked earlier, maybe anyone has already faced such a situation.
Sam Wu-MSFT 7,566 Reputation points Microsoft External Staff

2023-04-05T09:50:08.8333333+00:00

@DmitriyKobrinskiy-0284 These error messages cannot reproduce your problem, you still need to use IIS Debug Diagnostics Tool to troubleshoot your problem.
DmitriyKobrinskiy-0284 0 Reputation points

2023-04-06T05:35:11.66+00:00

@Sam Wu-MSFT All that is needed here is to think logically. If I have the ability to debug the compilation process in the vs environment, why complicate it? Which in the end will not clarify anything.
Sam Wu-MSFT 7,566 Reputation points Microsoft External Staff

2023-04-06T09:31:45.9666667+00:00

@DmitriyKobrinskiy-0284 If you want to find out the problem, it is not enough to just think logically. From 2016 to 2019, you can't be sure what content will affect this, so what we need to do is to get more information to troubleshoot the issue.

Answer 1

Limitless Technology 45,126

Hello

Thank you for your question and reaching out. I can understand you are having query\issues related to ASP.NET exception error cs1504.

The filesystem has already removed the file "Global.asax.cs." I believe a yellow warning icon is displayed next to the file in the Visual Studio solution. Windows Explorer should be used to verify that the file is present in those places.

Please Clean every project individually (Right click> Clean).
PleaseR ebuild every project individually (Right click> Rebuild).
Then Rebuild the startup project.

--If the reply is helpful, please Upvote and Accept as answer--

DmitriyKobrinskiy-0284 0 Reputation points

2023-04-06T11:12:37.2233333+00:00

@Sam Wu-MSFT Hätte ich auch, aber...man hat nur das was man hat. Wenn Projekt-Developer dafür Interesse hätte, hätte er auch hier Frage gestellt, ist nicht der Fall. Also alles gute. Umsonst quatschen ist nicht produktiv.
DmitriyKobrinskiy-0284 0 Reputation points

2023-04-06T11:41:37.1866667+00:00

@Sam Wu-MSFT Ich schlage vor, dass Developer erst in der VS MSBuild Log Optionen auf "Diagnose" stellt und das Projekt kompiliert. Dann warten wir auf seine Post, um mehr Informationen zu bekommen.
Sam Wu-MSFT 7,566 Reputation points Microsoft External Staff

2023-04-07T06:18:51.03+00:00

@DmitriyKobrinskiy-0284 You can also open a support ticket for this, one of our engineers will help find the root cause.
DmitriyKobrinskiy-0284 0 Reputation points

2023-04-08T11:16:26.17+00:00

@Sam Wu-MSFT Hello Sam Wu-MSTF, Thanks for the work, I just imported the project folder (WebService) from the TFSService as a project-folder again in Visual Studio and compiled it. After deploying precompiled webapp (service) to my WS2019 Evaluation VM, there was no error. I assume our software developer, were just slowing things down. Or he has problems with his development environment. At least it doesn't affect me much now. Thanks again.

Share via

ASP.NET Compilation Error on Windows Server 2019 with .NET 4.8 and IIS10

1 answer

Your answer