Layton Support - New pages [en]

Layton ServiceDesk - Errors - OleDbException (0x80004005)

2025-11-26T06:42:52Z

Jpainter: Added link to "Layton TLS Files.zip"

[[File:btn_back_up.png|link=User Guide for Layton ServiceDesk]] [[User Guide for Layton ServiceDesk|Back to Contents]]
__FORCETOC__
=Error Code: OleDbException (0x80004005)=
Server Error in '/LaytonServiceDesk' Application.

[DBNETLIB][ConnectionOpen (SECCreateCredentials().]SSL Security error.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.OleDb.OleDbException: [DBNETLIB][ConnectionOpen (SECCreateCredentials().]SSL Security error.

Source Error:

[OleDbException (0x80004005): [DBNETLIB][ConnectionOpen (SECCreateCredentials().]SSL Security error.]

=Issue Summary=

The LaytonServiceDesk ASP.NET application, deployed on Windows Server 2016 and developed using .NET Framework 4.5, is encountering a SQL Server connection failure. The error message is:

[DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.

This issue occurred after TLS 1.0 and TLS 1.1 were disabled on the SQL Server (Windows Server 2019) to enforce modern security protocols.

=Root Cause Analysis=

*The error results from a failed SSL/TLS handshake.
*The application uses a legacy SQL client (e.g., DBNETLIB or SQLOLEDB) that does not support or default to TLS 1.2.
*Additionally, .NET Framework 4.5 does not enable TLS 1.2 by default, even though the operating system supports it.

=Proposed Resolution=

Upgrade to a modern SQL client. Update the application's connection string to use ''MSOLEDBSQL'' or ''System.Data.SqlClient'', both of which support TLS 1.2. ''MSOLEDBSQL'' was chosen for minimal required changes and to resolve the issue quickly.

=Steps to Implement the Fix=
==IIS Configuration (''Layton ServiceDesk'' Site)==

1. Open IIS Manager (''Run > inetmgr'').

2. Expand the ''Sites'' node.

3. Locate and right-click the ''Layton'' site.

4. Select ''Explore'' to open the root directory:

[[File:Oledbexception_0x80004005_01.jpg]]

6. Navigate to the ''bin'' folder:

[[File:Oledbexception_0x80004005_02.jpg]]

7. Backup the existing files: 
**''App_Code.dll''
**''App_Code.compiled''

8. Download a replacement set of files:

[https://laytontechnology.com/support/images/7/79/layton_tls_files.zip Layton TLS Files]

9. Unzip and replace the above files.

==SQL Client Installation==
1. Download the [https://go.microsoft.com/fwlink/?linkid=2318001 x64 Installer] from Microsoft.

2. Run the installer.

==Final Steps==
*Reboot the server.
*Restart IIS.
*Run the application to verify connectivity to the SQL Server.

[[File:btn_back_up.png|link=User Guide for Layton ServiceDesk]] [[User Guide for Layton ServiceDesk|Back to Contents]]

Layton ServiceDesk - Release Notes - Version 6.9.4

2025-09-23T07:01:24Z

Jpainter: Minor text changes

[[File:btn_back_up.png|link=Layton ServiceDesk - Release Notes]] [[Layton ServiceDesk - Release Notes|Back to List]]
[[File:btn_back_up.png|link=Layton ServiceDesk - Release Notes - Version 6.9.3]] [[Layton ServiceDesk - Release Notes - Version 6.9.3|Earlier Version]]
=Overview=
Layton ServiceDesk 6.9.4 is an update-patch release of the product. Both update and full installers are available.

==Determining the Currently Installed Version==
Please refer to '''[[Layton ServiceDesk - Procedures - General - How to Find the Version Number|this article]]''' to determine the currently installed version.

==Earliest Version that Can Be Updated to 6.9.4==
'''You must be using ServiceDesk 6.2.0 or later before you can update to the latest version.''' If you are using an earlier version please update by downloading v6.2.0 from the ''Update ➤ Layton ServiceDesk'' menu in the '''[https://client.laytontechnology.com/ Client Support Portal]''' before attempting to update to the latest version.

==.NET 4 Requirement==
6.7.0.2 introduced the need for .NET 4. If you are currently running a version prior to 6.7.0.2, it will need to be installed. '''[[#Install Microsoft .NET Framework 4.5|Instructions are given below]]'''.

==Test Installation==
'''We recommend that you create a [[Layton ServiceDesk - Installation - Test Installation|Test Installation]] and update it before committing to updating your live system.'''

==Obtaining the Update==
Please log in to the '''[https://client.laytontechnology.com/ Client Support Portal]''' to download the update installer.

==Obtaining the Full Installer==
The full installer is the currently available trial version, which can be downloaded from '''[https://www.laytontechnology.com/trialsoftware/LaytonServiceDesk.zip here]'''. Please log in to the '''[https://client.laytontechnology.com/ Client Support Portal]''' to obtain your license details to register the application after installation.

=Updating from a Version Earlier than 6.7.0.2=
==Install Microsoft .NET Framework 4.5==
#If you are updating from a version earlier than 6.7.0.2, install '''[https://www.microsoft.com/en-au/download/details.aspx?id=30653 Microsoft .NET Framework 4.5]'''.
#Launch Internet Information Services (IIS) Manager.
#In the ''Connections'' pane on the left-hand side, click the server name.
#In the ''Actions'' pane on the right-hand side, click ''Change .NET Framework Version''.
#Change the .NET Framework Version to ''v4.0.30319'' and click the ''OK'' button. [[File:Lsd 6702 net4 config 02.png|link=]] 
#In the center panel, double-click ''ISAPI and CGI Restrictions''.
#There are two items with the description ''ASP.NET v4.0.30319''. Right-click each and select ''Allow''. [[File:Lsd 6702 net4 config 01.png|link=]] 
#Close Internet Information Services (IIS) Manager.
#Continue in the next section, '''[[#Updating from a Version Later than 6.7.0.2|Updating from a Version Later than 6.7.0.2]]'''.

=Updating from a Version Later than 6.7.0.2=
==Layton ServiceDesk==
Do not uninstall Layton ServiceDesk prior to updating.

#Extract the '''lsd_update_694''' folder from the archive to the root of an attached, local drive.
#Back up your database.
#If your server is virtual, snapshot the server. If it's not virtual, back it up using whatever backup software you use.
#In Windows Services Console, stop the following services:
#*IIS Admin Service
#*LaytonServiceDesk
#*World Wide Web Publishing Service.
#Disable anti-virus software on the server, if running. This has been known to prevent the copying of files, especially .exe files, to the Program Files folder.
#Open the '''lsd_update_694''' folder.
#Right-click the shortcut '''Right-Click and Run as Administrator''' and select ''Run as administrator''. This will avoid permission issues. Note that the progress dialog may report that it is not responding, but this process may simply take some time.
#In Windows Services Console, start the above services.
#Re-enable anti-virus software, if applicable.

=Full Installation=
==New Installation==
If you are installing for the first time, refer to '''[[Layton ServiceDesk - System Requirements|System Requirements]]''' and follow the links at the right bottom of each related article.

==Clean Reinstallation==
If you are doing a Clean Reinstallation, follow the '''[[Layton ServiceDesk - Installation - Clean Reinstallation|Clean Reinstallation procedure]]'''.

=Database Update=
It is possible to update just the database using a SQL Server script. The most common reason for doing this is the installation of the full version on a new server, then connecting it to the database, as opposed to running the update process, which does the database modifications.

==Procedure==
#Download the '''[https://client.laytontechnology.com/wp-content/themes/layton-admin/Update/bntlsd201/queries/lsd_update_database_684.zip 6.9.4 Update Script]'''.
#In Management Studio, back up your database.
#Run the script on the database.

=Bug Fixes=
{| class="wikitable" border="1"
! style="background:#009999; width: 50px; color: #FFFFFF"|#
! style="background:#009999; width: 250px; color: #FFFFFF"|Title
! style="background:#009999; width: 700px; color: #FFFFFF"|Description
|-style="vertical-align:top;"
|68714
|LDAP Import Not Working Due to Incorrect Value in ''sys_manualcreate'' Column
|A new column was added to the database in a recent version. The LDAP import process had not been updated to allow for this. This has been resolved.
|-style="vertical-align:top;"
|68789
|Installation Issues with .NET 4.5
|Additional bug fixing for this configuration was done.
|}

Released 2026-02-10.
[[File:btn_back_up.png|link=Layton ServiceDesk - Release Notes - Version 6.9.3]] [[Layton ServiceDesk - Release Notes - Version 6.9.3|Earlier Version]]
[[File:btn_back_up.png|link=Layton ServiceDesk - Release Notes]] [[Layton ServiceDesk - Release Notes|Back to List]]
[[Category:Update Notes]]

Layton ServiceDesk - Troubleshooting - The specified path '' is unavailable

2025-09-10T06:15:22Z

Jpainter: New page

[[File:btn_back_up.png|link=User Guide for Layton ServiceDesk]] [[User Guide for Layton ServiceDesk|Back to Contents]]
__FORCETOC__
=Overview=
In rare circumstances, the installer might get close to finishing, then stop with the message:

The specified path <nowiki>''</nowiki> is unavailable.

It has been discovered that this issue can be due to the absence of the ''Default Web Site'' in Internet Information Services (IIS). This is an unusual situation which has occurred on installation of Windows Server. It doesn't directly relate to Layton ServiceDesk.

=Instructions=
#Run IIS Manager as Administrator.
#Expand ''SERVER > Sites''. There should be no ''Default Web Site''.
#Right-click ''SERVER > Sites'' and select ''Add Website...''.
#In the ''Site name'' field, enter ''Default Web Site''. This will populate the ''Application pool'' field with ''Default Web Site''.
#Click the ''Select...'' button next to the ''Application pool'' field and select ''DefaultAppPool'', then click the ''OK'' button.
#Enter ''%SystemDrive%\inetpub\wwwroot'' in the ''Physical path'' field.
#Don't change any of the other settings. Click the ''OK'' button. The ''Default Web Site'' will now appear under ''Sites''.
#Run the Layton ServiceDesk installer again.