Welcome to the Lounge

charlieg wrote:

I still work on a VAX system

charlieg wrote:

Years ago, there was a "consultant" whose one claim to fame was to keep the VAX running. He had it in his basement. I have no idea how much $$ he made supporting this vax, but if you know anything about the DEC hardware back then, it was built like a tank. They just sit in the corner and run.

 

mikepwilson wrote:

"Make it easy to do big things"

ALL THESE WORLDS
ARE YOURS EXCEPT
    EUROPA TRITON HELL, ALL OF THEM
ATTEMPT NO
LANDING THERE

Quote:

When the CU4 setup package runs on a SQL Server instance, the setup program creates a temporary mdf file to get a certificate using the SQL Server instance’s default database directory. The setup program tries to save this temporary file in this directory. In this case, the directory “E:\SQLServer\Data” for the SQL Server instance didn’t exist causing the CU4 setup program to fail the installation.

I’m not really sure why the SQL Server default directory was set to “E:\SQLServer\Data”; however, to fix the problem I created the directory “E:\SQLServer\Data” and restarted the server. After rebooting it, all SQL Server services were running properly and I was able to log into Microsoft Management Studio without a problem using my domain account.

To make sure this issue didn’t occur again, I modified the database default directory to an existing directory. I logged into SSMS and right clicked on the instance name to get to the properties option. Under the “Database Setting” option, I changed the “Database default locations” data and log values (see Figure 2) and used “C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data” as the default directory.