Versions Compared

Old Version 5

changes.mady.by.user Paul Berkowitz

Saved on

compared with

New Version 6

changes.mady.by.user Paul Berkowitz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Solution: Make sure the FQDN (Fully Qualified Domain Name) name you defined exists in the DNS. You also need to make sure that TCP port 389 is open to the domain controller, as your traffic might be getting blocked by the firewall.

 

5. Database connection problem. 
Solution: Verify that: 

  • The CardioLog Scheduling Service login account can connect to the CardioLog database

...

  • and is assigned a db_owner role.
  • Your system has enough resources according to system requirements.
  • There is sufficient free space in the CardioLog database transaction log file and in the TEMP database transaction file.

 

Note: For more details turn details turn on extended logging for the ADTree web application and view the log file - ADXMLTree.log

...

1. Insufficient permissions to the SharePoint databases

Errors in the log file:

  • "Error: Cannot open database "SharePoint_Config" requested by the login. The login failed. Login failed for user [login user account]. SQL Server: [SQL server name], SQL Database: SharePoint_Config" 
  • "Error: Cannot open database "[Content database name]" requested by the login. The login failed. Login failed for user [login user account]. SQL Server: [SQL server name], SQL Database: [Content database name]"
  • "Error: The SELECT permission was denied on the object 'UserInfo', database '[Content database name]', schema 'dbo'. SQL Server:[SQL server name],, SQL Database: [Content database name]"

 

Solution: Verify that the CardioLog Scheduling Service login account has read access to all SharePoint configuration and content databases, and read access to the SharePoint TEMPLATE path: \\[SharePoint WFE server name]\C$\Program Files\Common Files\Microsoft Shared\web server extensions\[XX]\TEMPLATE (12 - for MOSS 2007, 14 - for SharePoint 2010, 15 - for SharePoint 2013)

2. Insufficient resources

Error in the log file:

  • "Error : Exception: There is insufficient system memory to run this query."
  • "Error : Exception: Exception of type 'System.OutOfMemoryException' was thrown."

Solution: Verify that your system has enough resources according to system requirements.

3. Network errors

Error in the log file:
"Error: 401 Not authorized"

Solution: Verify that the CardioLog user account has access to browse to the tree adaptor and sufficient read permissions on the server where the site tree is located.

4. Database connection problem 
Verify that:

  • The CardioLog Scheduling Service login account can connect to the CardioLog database and is assigned a db_owner role.
  • Your system has enough resources according to system requirements.
  • There is sufficient free space in the CardioLog database transaction log file and in the TEMP database transaction file.

 

Note: For more details turn details turn on extended logging for the SP20XXTree web application and view the log file -SP20XXTree.log  (XX - 07 for MOSS 2007, 10 for SharePoint 2010, 13 for SharePoint 2013)

...