Upon creating a Maintenace Plan in SSMS 17.6, SSMS automatially restarts upon attempting to schedule the task to run - scheduled-tasks

The architecture is Server 2016 with SQL 2016 Standard. SSMS has been set to run as administrator. SSMS 17.6 has been installed and re-installed. All Microsoft updates have been installed to the serer and the application.
Creating a Maintenance Plan and manually executing does not cause an issue.

today i ran into exact same issue at a system from my customers. It looks like a version specific issue.
Errors i got:
.NET Runtime Event ID 1026
Application Error ID 1000
Windows Error Reporting Event 1001
CLR20r3
System.NullReferenceException
Environment:
New Windows Server 2016 with all updates,
latest SQL Server 2016 Standard available,
SQL Server Management Studio 17.6.
I'm also not able to edit the scheduler for the maintenance sub-plans. While clicking on the icon to modify the scheduler, the application crashes and restarts automaticly.
Uninstalling all SSMS 17-Versions and reinstalling a previous version solved the issue for me. I have tested it with version 17.4 and 17.5 without problems. As long 17.6 was installed, also 17.4 shows the same effect, so uninstalling 17.6 seams to be mandatory in this case.
best regards,
Sven

This appears to be a known issue with SSMS 17.6, the suggested workaround is to uninstall 17.6 and reinstall 17.5 (or earlier) until the fix can be released in the next version of SSMS.
Per https://learn.microsoft.com/en-us/sql/ssms/sql-server-management-studio-changelog-ssms?view=sql-server-2017
There is a known issue where SSMS 17.6 becomes unstable and crashes when using Maintenance Plans. If you use Maintenance Plans, do not install SSMS 17.6. Downgrade to SSMS 17.5 if you already installed 17.6 and this issue is affecting you.

As of 2018-08-11, SSMS 17.8.1 is available for download. The scheduler button under each subplan section for each Maintenance plan does NOT crash or restart the studio.

Related

Entity Framework error on a MacBook Pro M1 running Windows 11 via Parallels

I have a 2021 MacBook Pro M1 that is running Windows 11 via Parallels.
I'm working on a Windows Forms project (Visual Studio 2022) that is using EntityFramework. When I create a new EntityFramework model the next error occurs:
Error after creating new EF model
After trying to compile the app, the next erros occur:
Errors while running
I have a Windows laptop and I did the exact same installation process of VisualStudio 2022 and when creating a new EntityFramework model, everything works "out of the box".
If anyone has any ideas to what is causing the problem I would appreciate the answer very much.
Thanks.
I tried fresh install of Windows 11 on Parallels.
I tried fresh install of Visual Studio (multiple times).
I tried installing EntityFramework package via NuGet Package Manager.
And nothing worked. Always the same errors.
Running into the same issue. Seems that MS is not supporting the port yet for EDMX and also the Data & Storage Workloads for ARM yet.

Entity Framework Exception on Windows 2019 when using MSDTC

We have 2 servers. One box is a MS SQL Server 2017 (14.0.3192.2) running on Windows Server 2016. The other is a Windows Server 2019 box running a web service with EF 6.2.0. The 2019 box is new, the production web service is running on a Win 2k12 R2 server currently with no issues. When EF needs to perform multiple transactions in a call it sounds like the call is promoted to use MS Distributed Transaction Coordinator. On the new 2019 server we are seeing these requests as being aborted. The exception we are seeing thrown in code is "The operation is not valid for the current state of the enlistment". I've run through all the DTC troubleshooting, but everything seems to check out. We don't use the Windows Firewall and no firewall is between the servers. The Local DTC config matches our existing server and the dtcping.exe tool reports no issues talking between servers. If we turn off the code that is causing multiple transactions then the issue goes away so everything is pointing to an issue between EF and MSDTC.
We haven't been able to get the multiple transactions working on our development computers either (Windows 10). Is it possible something broke with EF and DTC in more recent versions of windows or are we missing something?
I asked in the EF github project and was told this may be more for the sql-client team than EF. I tagged sqlclient as well on this.
We attempted to pull down the Entity Framework 6.3.0 preview 9 nuget package and tested it on the new Windows 2019 servers and magically DTC works (doesn't abort) with the Scoped Transactions. Something in the 6.3.0 build of EF must fix the issue we are experiencing with our DTC transactions aborting using the EF 6.2.0 public nuget build.
Since the 6.3.0 is still in preview we have rolled back to 6.2.0 in the meantime and turned off our scoped transactions until 6.3.0 is in full release. I'll update the github issue regarding this so the development team is aware.

While installing PostgreSQL on windows getting an popup "Microsoft Visual C++ 2013 Redistributable (x64)-12.0.40660 has stopped working"

I am trying to install the PostgresSQL on windows7 (64-bit). I have referred the installation steps, downloaded the postgresql-9.4.12-1-windows-x64.exe file.
But when I am running this file, an popup occurs and installation gets interrupted.
getting this pop up
Then I tried to install the postgresql-9.6.3-3-windows-x64.exe also but facing same error.
After searching for the solution and then I tried several ways like
"Run as administrator",
modified the file name to "postgresql-9.4.12-1-windows-x64.exe --install_runtimes 0",
installed the other visual c++ packages from microsoft support.
But still facing the same error popup.
Could someone help me to understand why I am getting this and suggest any solution for this.
You get this message because you are on an unsupported state (Windows 7 RTM without Sp1 and any update with the version 6.1.7600.16385).
To be able to install new Visual C++ Runtimes, you need to install the Windows 7 Sp1, next the April Servicing Stack update and June 2016 Rollup, reboot, run Windows Update, scan for new updates and install all offered updated.
Reboot and now install postgresql-9.4.12-1-windows-x64.exe.

PIA_INSTALL_FAIL during PeopleSoft Server Administration

I'm following the online installation example (https://www.youtube.com/watch?v=7ElSGLkprkY) to install PeopleSoft with PeopleTools on Windows 7 with SQLServer 2008 R2.
My PS and PT installation version differs from the online videos since I'm using most recent available versions:
PeopleSoft HM 9.2
PeopleTools 8.55
Tuxedo 12.1.3.0.0 with VS2012
WebLogic 12.1.3.0.0 64bit
JDK 7u55 x64
SQL Server 2008 R2
I could install each element with no error, excepted one VIEW during HC database creation (PS_EP_APPRMOB_PNDG), but I could re-create the view manually by slightly modifying the SQL query.
Now I'm trying to configure the Web (PIA) Server and I encounter an error while creating the domain. The piainstall_HC.log file contains following:
Tue Sep 20 09:48:32 CEST 2016:Starting PIA installation...
PS_HOME: c:\PT8.55
Install Action : CREATE_NEW_DOMAIN
Creating Domain...
Deploying Web Applications...
Deploying WebLogic Extension files...
Deploying PeopleSoft Site files...
Deploying PeopleSoft Site Doc files...
Completed.
PS_CFG_HOME: C:\PS_CFG_HOME
PIA_INSTALL_FAIL
After intensive googling, I found that some other people got a similar issue which was caused by a wrong version of the JDK: the JRockit jvm was required.
Of course I tried to use JRockit JDK 64bit, but I still get the same error. I also tried several other oracle JDK versions, among others the JDK 7u55 x64, which is provided with PeopleTools installation elements.
Unfortunately, I definitively get the same error and cannot find any other logfile which could give more information on the root cause.
Did someone experienced the same issue and could fix it ?
Thanks for help
I finally could fix the issue.
It seems that my error was to install the wrong weblogic version: originally, I installed weblogic by using the "setup_fmw_12.1.3.0.0_ohs_win64.exe" installer which was provided with PeopleTools.
It appears that the other one (fmw_12.1.3.0.0_wls.jar) was expected. After installing this version (with "Coherence"), the domain could be created successfully.

Active Reports 2 Install Issue on Win 10

We are trying to install Active Reports 2 on a Windows 10 system for a legacy report. We are getting this error. We tried installing .Net 2 SP2 and get the same error. Have you seen this error before? Also I was not able to locate an installer for MS Help 2.x run time if anyone knows where that might be.
Thanks
if you have vs 2003/2005 installed, the Ms help 2.x runtime should be installed. Make sure you run the installer as admin (right click, Run as Administrator), otherwise it will fail at multiple steps.