Sage 100

Try: IPAddress\InstanceName ...which should always work, as long as the SQL instance is running.

Check the SQL install... make sure it was installed using Mixed Mode, with the correct collation method.

Windows administrator login, UAC off, Run As Administrator (autorun.exe).

We do folder paths like D:\Accounting\Sage2024\MAS90\

(Don't try to just swap out files for a Premium install from server to server... you need to go through a data migration, and for a server move we typically do an upgrade at the same time, to save on costs).

Sooo it was the SQL password was too long and the Sage 100 installer was truncating it. I guess there is a limit of 15 characters (I am getting the official documents) and changing it too shorter worked. 

Try: IPAddress\InstanceName ...which should always work, as long as the SQL instance is running.

Check the SQL install... make sure it was installed using Mixed Mode, with the correct collation method.

Windows administrator login, UAC off, Run As Administrator (autorun.exe).

We do folder paths like D:\Accounting\Sage2024\MAS90\

(Don't try to just swap out files for a Premium install from server to server... you need to go through a data migration, and for a server move we typically do an upgrade at the same time, to save on costs).

Dear Sage 100 programmers,

You are no longer coding for a PC with 2 floppy drives and no hard drive...

------------------------------
Phil McIntosh
Friendly Systems, Inc.
------------------------------


Original Message:
Sent: 09-24-2024 13:11
From: Tina Meacham
Subject: Installation Error - Error 10: Illegal pathname specified

Sooo it was the SQL password was too long and the Sage 100 installer was truncating it. I guess there is a limit of 15 characters (I am getting the official documents) and changing it too shorter worked. 

------------------------------
Tina Meacham
RKL eSolutions, LLC


Original Message:
Sent: 09-24-2024 12:52
From: Kevin Moyes
Subject: Installation Error - Error 10: Illegal pathname specified

Try: IPAddress\InstanceName ...which should always work, as long as the SQL instance is running.

Check the SQL install... make sure it was installed using Mixed Mode, with the correct collation method.

Windows administrator login, UAC off, Run As Administrator (autorun.exe).

We do folder paths like D:\Accounting\Sage2024\MAS90\

(Don't try to just swap out files for a Premium install from server to server... you need to go through a data migration, and for a server move we typically do an upgrade at the same time, to save on costs).

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

@Phil McIntosh great response.  @Tina Leonard so the SQL 'sa' password for Sage 100 "must be" between 8 and 15 characters?  interesting... 

Dear Sage 100 programmers,

You are no longer coding for a PC with 2 floppy drives and no hard drive...

Sooo it was the SQL password was too long and the Sage 100 installer was truncating it. I guess there is a limit of 15 characters (I am getting the official documents) and changing it too shorter worked. 

Try: IPAddress\InstanceName ...which should always work, as long as the SQL instance is running.

Check the SQL install... make sure it was installed using Mixed Mode, with the correct collation method.

Windows administrator login, UAC off, Run As Administrator (autorun.exe).

We do folder paths like D:\Accounting\Sage2024\MAS90\

(Don't try to just swap out files for a Premium install from server to server... you need to go through a data migration, and for a server move we typically do an upgrade at the same time, to save on costs).

Yes, the error is a little misleading in the log files. What is odd, is that you do a precheck of the sa account during the installation wizard without issue, it's just when the system is creating the files in SQL during the installation that you get the Error 10: Illegal Pathname Specified. 

Here is what Sage sent regarding the password, because they said it was documented. 

Sage KB Solution ID:  225924850098671

Error: "Set SQL setting returned a failed" during Sage 100 Premium installation 

• Change length of SQL 'SA' account password to 8-13 characters
  NOTE: Can be changed to more secure password after Sage 100 installation

@Phil McIntosh great response.  @Tina Leonard so the SQL 'sa' password for Sage 100 "must be" between 8 and 15 characters?  interesting... 

Dear Sage 100 programmers,

You are no longer coding for a PC with 2 floppy drives and no hard drive...

Sooo it was the SQL password was too long and the Sage 100 installer was truncating it. I guess there is a limit of 15 characters (I am getting the official documents) and changing it too shorter worked. 

Try: IPAddress\InstanceName ...which should always work, as long as the SQL instance is running.

Check the SQL install... make sure it was installed using Mixed Mode, with the correct collation method.

Windows administrator login, UAC off, Run As Administrator (autorun.exe).

We do folder paths like D:\Accounting\Sage2024\MAS90\

(Don't try to just swap out files for a Premium install from server to server... you need to go through a data migration, and for a server move we typically do an upgrade at the same time, to save on costs).

Yes, the error is a little misleading in the log files. What is odd, is that you do a precheck of the sa account during the installation wizard without issue, it's just when the system is creating the files in SQL during the installation that you get the Error 10: Illegal Pathname Specified. 

Here is what Sage sent regarding the password, because they said it was documented. 

Sage KB Solution ID:  225924850098671

Error: "Set SQL setting returned a failed" during Sage 100 Premium installation 

• Change length of SQL 'SA' account password to 8-13 characters
  NOTE: Can be changed to more secure password after Sage 100 installation

@Phil McIntosh great response.  @Tina Leonard so the SQL 'sa' password for Sage 100 "must be" between 8 and 15 characters?  interesting... 

Dear Sage 100 programmers,

You are no longer coding for a PC with 2 floppy drives and no hard drive...

Sooo it was the SQL password was too long and the Sage 100 installer was truncating it. I guess there is a limit of 15 characters (I am getting the official documents) and changing it too shorter worked. 

Try: IPAddress\InstanceName ...which should always work, as long as the SQL instance is running.

Check the SQL install... make sure it was installed using Mixed Mode, with the correct collation method.

Windows administrator login, UAC off, Run As Administrator (autorun.exe).

We do folder paths like D:\Accounting\Sage2024\MAS90\

(Don't try to just swap out files for a Premium install from server to server... you need to go through a data migration, and for a server move we typically do an upgrade at the same time, to save on costs).

If anyone in Sage development is reading, this article goes over NIST's latest password guidelines, including this great blurb:

• Verifiers and CSPs SHALL require passwords to be a minimum of eight characters in length and SHOULD require passwords to be a minimum of 15 characters in length.
• Verifiers and CSPs SHOULD permit a maximum password length of at least 64 characters.

Yes, the error is a little misleading in the log files. What is odd, is that you do a precheck of the sa account during the installation wizard without issue, it's just when the system is creating the files in SQL during the installation that you get the Error 10: Illegal Pathname Specified. 

Here is what Sage sent regarding the password, because they said it was documented. 

Sage KB Solution ID:  225924850098671

Error: "Set SQL setting returned a failed" during Sage 100 Premium installation 

• Change length of SQL 'SA' account password to 8-13 characters
  NOTE: Can be changed to more secure password after Sage 100 installation

@Phil McIntosh great response.  @Tina Leonard so the SQL 'sa' password for Sage 100 "must be" between 8 and 15 characters?  interesting... 

Dear Sage 100 programmers,

You are no longer coding for a PC with 2 floppy drives and no hard drive...

Sooo it was the SQL password was too long and the Sage 100 installer was truncating it. I guess there is a limit of 15 characters (I am getting the official documents) and changing it too shorter worked. 

Try: IPAddress\InstanceName ...which should always work, as long as the SQL instance is running.

Check the SQL install... make sure it was installed using Mixed Mode, with the correct collation method.

Windows administrator login, UAC off, Run As Administrator (autorun.exe).

We do folder paths like D:\Accounting\Sage2024\MAS90\

(Don't try to just swap out files for a Premium install from server to server... you need to go through a data migration, and for a server move we typically do an upgrade at the same time, to save on costs).

If anyone in Sage development is reading, this article goes over NIST's latest password guidelines, including this great blurb:

• Verifiers and CSPs SHALL require passwords to be a minimum of eight characters in length and SHOULD require passwords to be a minimum of 15 characters in length.
• Verifiers and CSPs SHOULD permit a maximum password length of at least 64 characters.

Yes, the error is a little misleading in the log files. What is odd, is that you do a precheck of the sa account during the installation wizard without issue, it's just when the system is creating the files in SQL during the installation that you get the Error 10: Illegal Pathname Specified. 

Here is what Sage sent regarding the password, because they said it was documented. 

Sage KB Solution ID:  225924850098671

Error: "Set SQL setting returned a failed" during Sage 100 Premium installation 

• Change length of SQL 'SA' account password to 8-13 characters
  NOTE: Can be changed to more secure password after Sage 100 installation

@Phil McIntosh great response.  @Tina Leonard so the SQL 'sa' password for Sage 100 "must be" between 8 and 15 characters?  interesting... 

Dear Sage 100 programmers,

You are no longer coding for a PC with 2 floppy drives and no hard drive...

Sooo it was the SQL password was too long and the Sage 100 installer was truncating it. I guess there is a limit of 15 characters (I am getting the official documents) and changing it too shorter worked. 

Try: IPAddress\InstanceName ...which should always work, as long as the SQL instance is running.

Check the SQL install... make sure it was installed using Mixed Mode, with the correct collation method.

Windows administrator login, UAC off, Run As Administrator (autorun.exe).

We do folder paths like D:\Accounting\Sage2024\MAS90\

(Don't try to just swap out files for a Premium install from server to server... you need to go through a data migration, and for a server move we typically do an upgrade at the same time, to save on costs).

If anyone in Sage development is reading, this article goes over NIST's latest password guidelines, including this great blurb:

• Verifiers and CSPs SHALL require passwords to be a minimum of eight characters in length and SHOULD require passwords to be a minimum of 15 characters in length.
• Verifiers and CSPs SHOULD permit a maximum password length of at least 64 characters.

Yes, the error is a little misleading in the log files. What is odd, is that you do a precheck of the sa account during the installation wizard without issue, it's just when the system is creating the files in SQL during the installation that you get the Error 10: Illegal Pathname Specified. 

Here is what Sage sent regarding the password, because they said it was documented. 

Sage KB Solution ID:  225924850098671

Error: "Set SQL setting returned a failed" during Sage 100 Premium installation 

• Change length of SQL 'SA' account password to 8-13 characters
  NOTE: Can be changed to more secure password after Sage 100 installation

@Phil McIntosh great response.  @Tina Leonard so the SQL 'sa' password for Sage 100 "must be" between 8 and 15 characters?  interesting... 

Dear Sage 100 programmers,

You are no longer coding for a PC with 2 floppy drives and no hard drive...

Sooo it was the SQL password was too long and the Sage 100 installer was truncating it. I guess there is a limit of 15 characters (I am getting the official documents) and changing it too shorter worked. 

Try: IPAddress\InstanceName ...which should always work, as long as the SQL instance is running.

Check the SQL install... make sure it was installed using Mixed Mode, with the correct collation method.

Windows administrator login, UAC off, Run As Administrator (autorun.exe).

We do folder paths like D:\Accounting\Sage2024\MAS90\

(Don't try to just swap out files for a Premium install from server to server... you need to go through a data migration, and for a server move we typically do an upgrade at the same time, to save on costs).