...
On this page:
|
---|
ERROR: 500 - Internal Server Error
...
Question
Why am I getting "Server Error - 500 - Internal Server Error" after a new on-premise Timetracker installation.
...
Answer
This error appears when the required version of ASP.NET Core Runtime - Windows Hosting Bundle is not installed.
7pace Timetracker version | Required minimal bundle version | Download link |
5.53 and up | 8.0.103 | |
5.46 to 5.52 | 6.0.21 | |
5.11 to 5.45 | 3.1.32 |
Please refer to THIS this article in order to check all of the requirements for the Timetracker installation.
ERROR: Could not grant access to 7pace Timetracker database for user
Symptom:
During the installation and configuration process of 7pace Timetracker (on-prem), while "Applying Settings", an error appears: "Could not grant access to 7pace Timetracker database for user ..."
...
The following SQL statements are being run:
IF
...
NOT
...
EXISTS
...
(SELECT
...
name
...
FROM
...
master.sys.server_principals
...
WHERE
...
name
...
=
...
'SERVICE_ACCOUNT_USER_NAME')
BEGIN
...
CREATE
...
LOGIN
...
[SERVICE_ACCOUNT_USER_NAME]
...
FROM
...
WINDOWS
END
SELECT
...
su.name
...
AS
...
DatabaseUsername
...
...
FROM
...
sys.sysusers
...
su
...
...
JOIN
...
sys.syslogins
...
sl
...
ON
...
sl.sid
...
=
...
su.sid
...
WHERE
...
sl.name
...
=
...
'SERVICE_ACCOUNT_USER_NAME'
IF
...
NOT
...
EXISTS
...
(
SELECT
...
su.name
...
as
...
DatabaseUsername
...
FROM
...
sys.sysusers
...
su
...
JOIN
...
sys.syslogins
...
sl
...
on
...
sl.sid
...
=
...
su.sid
...
WHERE
...
sl.name
...
=
...
'SERVICE_ACCOUNT_USER_NAME'
...
)
BEGIN
...
CREATE
...
USER
...
[SERVICE_ACCOUNT_USER_NAME]
...
FOR
...
LOGIN
...
[SERVICE_ACCOUNT_USER_NAME]
...
WITH
...
DEFAULT_SCHEMA=[db_owner]
END
ALTER
...
ROLE
...
[db_owner]
...
ADD
...
MEMBER
...
[SERVICE_ACCOUNT_USER_NAME]
Remedy:
Preferred: Change the Application Pool Account user and ensure that the current user running the Configuration tool has permissions to execute the SQL statements, above.
It is also possible to skip the step by clicking "Skip database permissions modification" and configure permissions manually after installation.
Why can’t 7pace Timetracker find my TFS installation?
...
Question
We are unable to install 7pace Timetracker (on-prem) to our TFS 2018 (Update3) server. We’re stuck at the step: "What Microsoft Team Foundation Server should we use?" No matter what TFS Server URL we enter (we tried http, https, direct IP, localhost and combinations of these), we get an error message:
A valid version of TFS was not found or connection to it has failed. 7pace Timetracker supports TFS 2015 Update 2 and higher. Please check that the TFS server is available and your user has rights to access it.
How can we install this successfully?
...
Answer
The reason this issue is occurring is because of security/crypto policies. The solution is to check your security policies.
Please temporarily enable all the weak cryptos (like TLS 1.0, TLS 1.2), to check if this solves the issue with installation. You can then disable them back after configuration has completed successfully.
Why do I get a Network Error/Access Denied message when trying to access Timetracker Hubs?
...
Question
Why do I get a Network Error/Access Denied message when trying to access Timetracker Hubs?
...
Answer
This error has occurred when a user attempts to access any of the TFS Timetracker hubs within the application.
...
Until this defect is fixed by Microsoft, we are recommending the current workaround to assist in alleviating the resulting network error/access denied messaging:
Create different URL addresses for TFS in the TFS Administration Console and Timetracker in Timetracker Configuration Tool respectively, i.e. webapptfstest for TFS and webapptttest for Timetracker.
OR
Create non-standard, differing ports for TFS in the TFS Administration Console and Timetracker in the Timetracker Configuration Tool, e.g. 4433 for TFS and 8090 for Timetracker. IMPORTANT: Please make sure that the TFS port number doesn’t start with Timetracker's port number, i.e. TFS: 844 and Timetracker: 8443; this will generate the error.
What are the required SQL Server permissions to install Timetracker for DevOps Server?
Question
When installing Timetracker, I get the error, below, when I run the 7pace Timetracker for DevOps Server Configuration Tool:
...
InnerException: User does not have permission to perform this action.
Can you help?
...
Answer
If a user does not have sufficient permissions to create a user on SQL server and to add this user to the Timetracker database Configuration Tool, the error you described, above, will display.
...
Please note: These permissions are required only for the configuration step, and can be reduced, if necessary, after successful setup.
Why are we are getting CorruptedAuthorization errors after a fresh install of 7pace Timetracker on-prem?
Question
After installing Timetracker on-prem, we get the error below, many of them within the browser console:
Error: Connection disconnected with error 'Error: Server returned an error on close: Connection closed with an error. HttpException: CorruptedAuthorization'.
Ans
...
wer
This error usually appears when the IIS webSocket protocol is not installed and enabled on the server running 7pace Timetracker. In order to resolve it, please install the protocol and ensure that it is enabled. This protocol is a requirement for DevOps server and without it, both DevOps and Timetracker will not function correctly.
...