Unable to installing the SQL server 2022 reporting services on the Windows 10 Pro and Windows 11Pro
I am writing to you because I am encountering an issue while attempting to install SQL Server 2022 Reporting Services on Windows 10 Pro and Windows 11 Pro machines. While I have been able to start the installation process, I am unable to run the SQL Server 2022 Reporting Services .exe file. I have included the error message log details below for your reference. Application: SQLServerReportingServices.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 6CD5D612 (6CA70000) with exit code 80131506. I would greatly appreciate any assistance you can provide in resolving this issue. Thank you for your time and attention to this matter.
SQL server compatible with macbook pro m3 max via Parallels VM?
I'm having problems in installing SQL server on my macbook pro m3 max via parallels virtual machine. But I have this downloaded together with the SQL server management studio on my macbook pro m1 via parallels virtual machine. I feel like I've wasted so much money buying the m3 max and I couldn't even install the SQL server and SQL server management studio. I hope someone can help me.SQL Server 2022 - Product Keys?
I have the Microsoft Action pack with a visual studio subscription. As part of that, i have SQL server standard and Enterprise available for download. It says on the link that no keys are required. How is that possible? Is this only going to be like a 30 day trial? I need it longer than that. Historically the license was perpetual for earlier versions. This is for a lab environment (non prod)
MS Access passthrough query performs very slow when executing a stored procedure
I have a passthrough query in my Access frontend that I use to import data from a sql server db. I work with MS 365 MSO Version 2302 32 Bit. Before executing the passthrough query I pass the connectionstring and the sql to the querydef object and then I pass the output to a DAO recordset: Set qdf = CurrentDb.QueryDefs("myPTQuery") qdf.Connect = myconnectionstring qdf.SQL = "EXEC MyStoredProc " & param1 & ", " param2 Set rstDAO = qdf.OpenRecordset When I execute the stored procedure in SSMS using the same parameters it takes 2 seconds. In MS Access I need to set the ODBCTimeout parameter to 4 minutes to avoid a timeout error. This problem occures rarely, i.e. only under certain parameters. But I cannot figure out any significant difference between the cases the passthrough query performs well and the ones it doesn't. It seems like the timeout occures regardless on which parameters are passed to the stored proc. It worked before. Could it be caused by some office update? Any ideas on how to improve the performance of the passthrough query?SQL Server installation error on Windows 11 Pro system
Hi All, I'm facing the decimal error code while installing the SQL Server 2022(Developer edition) on my local system. I tried the few of the methods suggested which are - 1. removing all components of previously installed instance. 2. Running setup.exe file with admin access. 3. Turn off the firewall. Didn't get expected results. It would be very helpful if someone support me. Thanks in advance. ERROR - exit code decimal 2068052377 Error Description: Invalid command line argument. Consult windows installer SDK for detailed command line help. Regards, ManuSQL Server 2022: AlwaysOn AG databases can not sync after applying CU6 or higher
The setup is: OS - Win Server 2022 & MSSQL - SQL Server 2022 AlwaysOn Availability Groups are enabled on two (primary + secondary) replicas and use WSFC. Several availability groups are created and a database in each of them. AGs are configured with Sync Commit and Automatic failover mode, also they use dedicated separate VLAN for data sync. The issue we noticed is that after applying CU6 or higher ones , in case of we restart any of two replica hosts, on the secondary replica not all databases switch back to Synchronized state, part of them remain in Not Synchronizing state . Any ideas what could be the reason of that behavior change? Had someone similar issue ?I have Visual Studio 2022 and SQL Server 2022 (same versions) on 2 machines. DB file only works on 1
Hi I have a database file that I am able to connect to SQL Server 2022 using Visual Studio 2022 on computer_1, but when I move that file to computer_2 (also with the same versions of SQL Server 2022 and Visual Studio 2022) I get the error in the first image, "the file is not compatible with Current instance of SQL Server". If I upgrade the file on the computer_2, it can be attached, BUT when I move the file back to the original machine, I get the error in the second image, "the file cannot be opened because it is version 904".... Both computers have the most recent versions of SQL Server 2022 and Visual Studio 2022. Both computers have previous versions of SQL Server. It is as if the second computer is not using the same server as the first. The file was originally created in Visual Studio 2010, but again, works fine with SQL Server 2022 on computer_1. Does anyone know how I can clarify this situation and force the two machines to use the same versions of SQL Server (if that is the problem)? Note: I have confirmed the versions of SQL Server 2022 and Visual Studio 2022. They are the same. Thanks!
