Client Server install fails with "invalid service" name erro
Posted: January 14th, 2012, 3:29 amDoing Client/Server Full install fails with “invalid service” name error.
At the end of the Client/Server Full installation process user received the following error message “Pervasive.SQL 2000 (transactional) is an invalid service name.” In this case it turned out that the user was trying to direct the Pervasive installation to a mapped drive. As general guidelines, the Client/Server Full install must be done directly at the server computer. And it is preferable to accept the default location for Pervasive, but if a different, specific drive is desired, a local, physical drive letter must be specified. (NOTE: this does not apply to Novell Netware installations.)
At the end of the Client/Server Full installation process user received the following error message “Pervasive.SQL 2000 (transactional) is an invalid service name.” In this case it turned out that the user was trying to direct the Pervasive installation to a mapped drive. As general guidelines, the Client/Server Full install must be done directly at the server computer. And it is preferable to accept the default location for Pervasive, but if a different, specific drive is desired, a local, physical drive letter must be specified. (NOTE: this does not apply to Novell Netware installations.)