TFS 2017 web application not displaying well - tfs

We installed TFS 2017 update 3 and we are having issues when displaying the icons in the web application. We are having issues with the "Files" section inside "Code" for each one of our projects, the contents of the files aren't displaying. In the browser console, we can see these issues. Our Bowtie.woff file has 39KB.
CSS3111: #font-face encountered unknown error. bowtie.eot
CSS3111: #font-face encountered unknown error. bowtie.woff
CSS3111: #font-face encountered unknown error. fabricmdl2icons.woff
CSS3114: #font-face failed OpenType embedding permission check.
Permission must be Installable. fabricmdl2icons.ttf
CSS3111: #font-face encountered unknown error. fabricmdl2icons.woff
CSS3114: #font-face failed OpenType embedding permission check.
Permission must be Installable. fabricmdl2icons.ttf
The request are showing errors:
_content/Fonts/Icons/bowtie.eot?iefix 500 internal server error
_content/Fonts/Icons/bowtie.woff 500 internal server error
_content/Fonts/Icons/bowtie.eot?iefix 500 internal server error
/_scripts/TFS/min/VersionControl/scenarios/Shared/HookSplitterResizeEventToNativeEvent.js
500 internal server error
_content/Extensions/CodeEditor/0.8.3/vs/Editor/editor.main.css 500 internal server error
_scripts/Extensions/min/TFS.extension.js 500 internal server error

I checked the Bowtie.woff file on my side, it's also 39KB. Seems it's not caused by the file.
Seems it's related to the privilege of the service account.
If you are seeing HTTP 500 when servicing static content, most likely
your service account does not have "Impersonate a client after
authentication" privilege.
Refer to Vladimir's answer in this thread : TFS 2017 Missing Icons
To check/add permission you can do the following:
Windows Start > Administrative Tools
Open "Local Security Policy" editor.
Navigate to Security Settings Local Policies > User
Rights Assignment
Double click on "Impersonate a client after authentication"
Another possibility is the web.config file issue which under below path:
C:\Program Files\Microsoft Team Foundation Server 15.0\Application Tier\Web Services\_static\tfs\Dev15.M125.1\_content\Fonts
Refer to this thred for details : TFS 2015 Update 2 Missing Icons

Related

The requested page cannot be accessed because the related configuration data for the page is invalid. (with a "catch"...)

Another user in my organization put a folder with source code on a central server. I copied the source code to my local machine and when I try to run the application in VS on my local machine I get the following error:
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Detailed Error Information:
Module IIS Web Core
Notification Unknown
Handler Not yet determined
Error Code 0x80070005
Config Error Cannot read configuration file due to insufficient permissions
Config File \\?\UNC\...\users\username\My Web Sites\Website1\web.config
The issue is with the file location of the problematic .config file:
\\?\UNC...\users\username\My Web Sites\Website1\web.config
This location does not exist on my local machine. I have confirmed with the other user that it does exist on his machine - so it appears that the application is referencing a file location that simply does not exist. My suspicion is that there is some kind of folder/cache that needs to be cleared out, but I don't know what to do in this situation. Any ideas?
Ended up actually finding a duplicate question with an answer regarding deleting an applicationhost.config file and then recreating it in VS:
HTTP error 500.19 - Cannot read configuration file

Publish Failed to sign msix

Using Visual Studio 2019 to publish an update to an existing windows store application. This worked a week ago.
Our solution builds without error. When I go to create the setup package I get an error "Failed to sign 'D:\dev\MeyerMusic\MeyerTablet\TabletDistribution\bin\AnyCPU\Release\MeyerMusicTabletSetup_2.6.6.0_AnyCPU.msix'."
We are distributing the application as a Microsoft Store app under the existing app name.
Last week on this same development computer I built version 2.6.5 as well as many packages before that.
The error number is blank or missing. I do not have a reason for the failure. I only see one fact in the error message and that points to line 4574 in the file: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets
That line is this:
<SignAppxPackage Condition="'$(AppxPackageSigningEnabled)' == 'true'"
AppxPackageToSign="$(AppxMainPackageOutput)"
CertificateThumbprint="$(PackageCertificateThumbprint)"
CertificateFile="$(PackageCertificateKeyFile)"
CertificatePassword="$(PackageCertificatePassword)"
HashAlgorithmId="$(AppxHashAlgorithmId)"
EnableSigningChecks="$(EnableSigningChecks)"
SignAppxPackageExeFullPath="$(SignAppxPackageExeFullPath)"
TempCertificateFilePath="$(TempCertificateFilePath)"
VsTelemetrySession="$(VsTelemetrySession)"
SigningTimestampServerUrl="$(AppxPackageSigningTimestampServerUrl)"
SigningTimestampDigestAlgorithm="$(AppxPackageSigningTimestampDigestAlgorithm)"
/>
Troubleshooting steps:
Attempted to build a side load package. Results in same error
Successfully built a side load package that was not signed
I have restarted Visual Studio
I have rebooted the machine
I have deleted OBJ, BIN for the entire solution
I have looked for errors in the event log but none have been found so far.
After uninstalling KB4535996 the problem was resolved.
I found this via a tip from the following post: https://developercommunity.visualstudio.com/content/problem/934967/uwp-error-failed-to-sign.html

Wix ICE Error from 01 to 07

I have to update our build-system from the old "XML-System" to the newer vNext.
Now I have the problem, that in a build progress, I'm getting errormessages from ligther.exe:
[error]light.exe(0,0): Error LGHT0217: Error executing ICE action 'ICE01'. ...
up to ICE07.
And at the end:
[error]light.exe(0,0): Error LGHT0216: An unexpected Win32 exception with error code 0x643 occurred: Action - 'ICE09' Fatal error during installation
When I make the same build with the "old" XML-Version it works without any problems, any ideas?
Thanks a lot.
Kriz
According to the error prompting message: An unexpected Win32 exception with error code 0x643 occurred: Action - 'ICE09' Fatal error during installation
It's probably a permissions problem with validation. You could try to give the build service account more privileges such as local administrator permission on the build agent.
Besides, there are no tools to convert XAML build definition to vNext directly, so please double check you have manually created fully in a accord.
I saw this issue only on the build machine, where the build task has no admin rights.
I didn't saw this on my developer machine, where I have admin rights. This error is written by the light.exe, which is the Windows Installer XML linker contained in the Wix Toolset.
In order to solve this I suppressed validation of the light.exe. This can be done in two different ways:
On the commandline of light.exe
-sval
On the commandline, when using WixSharp
Compiler.LightOptions = "-sval";

HTTP Error 500.21 - Internal Server Error

While trying to run my application hosted in IIS, its giving me following error.
Module IIS Web Core
Notification BeginRequest
Handler Not yet determined
Error Code 0x80070021
Config Error This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".
Config File \\?\C:\inetpub\wwwroot\Planner\web.config
After googling i found some suggestion, i tried to run the following comment in command prompt it got unlocked.
%windir%\system32\inetsrv\appcmd.exe unlock config -section:system.webServer/handlers -commitpath:apphost
Now i am getting the following new error.
Module IIS Web Core
Notification ExecuteRequestHandler
Handler BlockViewHandler
Error Code 0x8007000d
Requested URL http://localhost:80/Planner/Views
Physical Path C:\inetpub\wwwroot\Planner\Views
Logon Method Anonymous
Logon User Anonymous
Most likely causes:
Managed handler is used; however, ASP.NET is not installed or is not installed completely.
There is a typographical error in the configuration for the handler module list.
Any help please?
Thanks in advance.
I have the same error on windows 7 when testing my new website with .Net 4.
The cause of this problem is that your .Net is not registered with your IIS.
To solve this error I run CMD as administrator and run this simple command in it:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i
After registering IIS with .Net 4 my problem solved.

Error "File or directory corrupted" when an MVC template is being loaded

How do we deploy the application
Publish to local filesystem with Visual Studio.
Create an application on production server (IIS)
Copy the files to the app directory
There is an error in our production server.
Server Error in '/' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: The disk structure is corrupted and unreadable.
Source Error:
Line 1: <div class="row-fluid">Line 2: <div id="graph" class="span24">Line 3: </div>
Source File: /Views/ProductionOrder/ProductionOrderFlow.cshtml Line: 1
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272
I have checked the file system and no error found.
The template file can be successfully opened with notepad.
Any other possible reasons?
If you used a shared folder in order to copy the files, you may check this answer from super user: link. Your files might be blocked due to security reasons. Right click and properties for the root folder to check for this.
Second option might be replacing the hard disk drive of the server.
Third option might be different file encoding between your computer and live computer.

Resources