As a SQL Server professional, it is not uncommon to encounter new challenges and errors while working on different projects. These experiences provide valuable opportunities to learn and share knowledge with others. In this blog post, we will discuss how to fix the “The filename, directory name, or volume label syntax is incorrect” error that occurs when starting SQL Server Analysis Services.

When attempting to start the SQL Server Analysis Services using the configuration manager, you may encounter the following error message in the system event log:

Log Name: Application
Source: MSSQLServerOLAPService
Date: 7/2/2018 7:50:33 AM
Event ID: 0
Task Category: (289)
Level: Error
Keywords: Classic
User: N/A
Computer: SQLAUTHVM1
Description:
The service cannot be started: The following error occurred during a file operation: The filename, directory name, or volume label syntax is incorrect. (\\?\E:).

Upon further investigation, you may notice that the path mentioned at the end of the error message is “\\?\E:”. While this may seem like a valid path, it can actually be the cause of the error.

In one particular case, the issue was traced back to the configuration file “msmdsrv.ini” located in the “C:\Program Files\Microsoft SQL Server\MSAS14.MSSQLSERVER\OLAP\Config” folder. The file had been modified to reference the E drive, as the DBA wanted to move the databases to that location.

However, it is important to note that Windows does not allow writing directly to the root of a drive. This restriction can lead to the “The filename, directory name, or volume label syntax is incorrect” error. In this case, the error message was misleading, as one would expect an “Access is denied” error instead.

To resolve this issue, the configuration file “msmdsrv.ini” was updated to reference a folder on the E drive, rather than the root of the drive. After making this change, the SQL Server Analysis Services were able to start successfully.

It is crucial to ensure that any modifications made to configuration files are done correctly and adhere to the necessary file system rules. This will help avoid errors and ensure the smooth operation of SQL Server Analysis Services.

As SQL Server professionals, we must always be prepared to troubleshoot and resolve various issues that may arise. By sharing our experiences and solutions, we can help others facing similar challenges in their SQL Server environments.

Thank you for reading this blog post. Stay tuned for more SQL Server tips and tricks!

Author: Your Name

Date: Current Date