guitartom47

Dave, thanks again for your help! I did everything you suggested. Still failing in the same places, but I did find some other info that may provide a clue. sql server - Error starting localDb on Windows 11 - Database Administrators Stack Exchange the link shows "Windows 11 and Windows Server 2022 does not report correct sector information for some storage devices, particularly NVMe M.2 SSD devices. This causes issues with SQL Server IO when reported sector sizes are over 4K." My sector size shows 32k!! - same type of ssd I think. Now I'm not sure what to do to fix things but i think I'm closer to an answer maybe?

Thanks for getting back so fast! Yes the database program is installed. I checked it, and I've re-installed it 2 or 3 times as well in the past 24 hours. Next I followed your list, opened command prompt as admin and the 3rd command [SQLLocalDB create "MSSQLLocalDB"] failed. Here's the message I got: [Start of LocalDB instance "MSSQLLocalDB" failed because of the following error: Error occurred during LocalDB instance startup: SQL Server process failed to start.] First 2 commands worked, and the second 2 did not.

I've been trying for a few days to solve this now. I believe that this probably isn't so much a Pilot2Atc bug as a security/permissions problem with the SQL software, but I'd like some input. So far when I try to use pilot2atc with msfs, this is the message I've been getting: Unable to initialize database the underlying provider failed to open. a network-related or instance specific error occurred while establishing a connection to SQL server. The server was not found or was not accessible. Verify that the instance name is correct and that the SQL server is configured to allow remote connections. (provider: SQL Network interfaces, error: 50 - Local Database Runtime error occurred. Error occurred during LocalDB instance startup: SQL Server process failed to start.) after I click okay, pilot2atc starts up but is unable to connect to msfs.