Sap Solution Manager Versions

[Manases Blakemore]

IntroscopeEnterprise Manager version compatibility with SAP Solution Manager needs to be confirmedErrors occurred when importing Introscope Enterprise Manager into the SAP Solution Manager landscape e.g. Unexcepted error occurred in the method AddExistingInstallation

Introscope em compatibility, enterprise manager compatibility, wily compatibility, Introscope versions, Convergent Charging, grey introscope metrics , KBA , XX-PART-WILY , Introscope by CA Technologies , SV-SMG-DIA-WLY-EMS , Enterprise Manager Setup , How To

I have yet another situation which requires the expertise of users with more knowledge than I posses. I am in the process of setting up a new Solution Manager 7.1 system. We run SAP on two kinds of servers, AS400 and Windows. My current task is to set up Diagnostics Agent 7.3 on all the hosts we run an SAP system on. I finished installing Diagnostics Agents on my AS400 systems but I have run into something while working with one of our Windows systems.

I noticed something was wrong first when I went to do the Managed System Configuration through solman_setup. We have two SAP systems on the host uksapmiiprd, an abap system and a java system. I started out with the config of the the abap system. Once I got to the step Assign Diagnostics Agent I realized something must be wrong with the agent I installed on this host. In the Agent Assignment tab, when I choose Assign, there are no agents on this host to choose from.

I continued to the next tab on this page, SLD Agent Candidates, I see that connection to uksapmiiprd has failed... Makes sense then why the previous tab seems to think there aren't any Diagnostics Agents on this host.

I also took a look at the Agent Administration tool. This screen shot is from the agent administration tool. As you can see I am getting the message "Agent Version Differs from LMService" and further right you can see I am getting a status of deploying applications. Under the application management tab, if I try to deploy applications to the agent on uksapmiiprd I get a bunch of errors about how the host can't be found. Under the application viewer tab I can see there are only 6 applications associated with the agent on host uksapmiiprd, but agents on all the other hosts have like 36 applications.

Since I realized something was wrong with this particular diagnostics agent I started researching but didn't find a whole lot to go on. I am a novice at best when it comes to SAP as a whole so I have little idea where to look for the answers. I read a suggestion to look at the diagnostics agent troubleshooting guide, but I just didn't see a fix. So I guess what I would like is some help figuring out why this diagnostics agent isn't connecting to the solution manager correctly, or maybe an explanation as to why the Agent version differs from LMService. Which seems strange to me since I have this same version of Diagnostics Agent on another Windows host and there aren't any messages about the agent version differing from the LMService. Please direct me to any logs I should be looking for, or any documentation that exists which would assist me. If I can not resolve this within the next few days I will probably just try to reinstall the Diagnostics Agent, but I would prefer to just fix the one I have. Thanks for all the help in advance.

From SMD Admin page, when it says "Agent version differs from LMService", just wait for few mins. and Managed System's SMDAgent binary gets automatically synced from Managing System (Sol Man) & then status can be seen as active/in Green.

I didn't see any .lock file for smdagent.properties and also SAP has OSS note 1931100 - "Agent version differs from LMService" Error in Solution Manager 7.1 Agent Administration ...and both of this not applied/applicable in my case.

taking the chance replying to this old thread also. I had the same issue, and in my case the solman j2ee dispatcher threads have been exhaused. I increased the default value 200 to 300 in configuration tool at

Visual Studio 2017 and higher automatically includes NuGet Package Manager when a .NET-related workload is installed. To install it individually in Visual Studio Installer, select the Individual components tab, and then select NuGet package manager under Code tools .

For Visual Studio 2015, if you're missing the NuGet Package Manager, check Tools > Extensions and Updates and search for the NuGet Package Manager extension. If you're unable to use the extensions installer in Visual Studio, download the extension directly from

In Visual Studio 17.11 and higher, package owners are shown as profile hyperlinks when supported by the selected package source.Package ownership is defined by the package source. For example, see Manage package owners on nuget.org.

Visual Studio installs the package and its dependencies in the project. When installation is complete, the added packages appear on the Installed tab. You can also find packages in the Dependencies > Packages node of your project in Solution Explorer. After you install a package, you can refer to it in the project with a using statement.

Select the Updates tab to see packages that have available updates from the selected Package source. Select Include prerelease to include prerelease packages in the update list.

For some packages, the Update button is disabled and the following message appears: Implicitly referenced by an SDK. To update the package, update the SDK to which it belongs. This message indicates that the package is part of a larger framework or SDK and can't be updated independently. Such packages are internally marked with True. For example, Microsoft.NETCore.App is part of the .NET Core SDK, and the package version is different than the version of the runtime framework used by the application. To download a new version of the .NET Core, update your .NET Core installation. For more information, see .NET Core metapackages and versioning. This scenario applies to the following commonly used packages:

Developers typically consider it bad practice to use different versions of the same NuGet package across different projects in the same solution. Visual Studio allows you to use a common version for your NuGet packages. To do so, use the Consolidate tab of the NuGet Package Manager window to discover where packages with distinct version numbers are used by different projects in the solution.

Visual Studio ignores the order of package sources, and uses the package from whichever source is the first to respond to a request. For more information, see Restore packages. For information about how to load a package from a specific source, see Package source mapping.

If a package source reappears after you delete it, it might be listed in a computer-level or user-level NuGet.config file. For the location of these files, see Common NuGet configurations. Remove the package source in the files by editing them manually or using the nuget sources command.

When you select a package, the NuGet Package Manager displays an expandable Options control below the Version selector. For most project types, only the Show preview window option is provided.

Force uninstall even if there are dependencies on it: When selected, uninstalls a package even if it's still being referenced in the project. This option is typically used in combination with Remove dependencies to remove a package and whatever dependencies it installed. Using this option may, however, lead to broken references in the project. In such a case, you might need to reinstall those other packages.

CA Introscope Enterprise Manager is part of CA APM Introscope(R), an application performance management solution to manage Java Application performance. With the Right to View (RTV) version of CA APM Introscope, SAP ships a read-only version of the full product that is bundled with SAP Solution Manager (SolMan). This version only supports products that are licensed and supported by SAP. CA APM Introscope is integrated in the SolMan infrastructure. While the CA Introscope Enterprise Manager(s) are directly connected to SolMan, the Introscope Host Adapters (also known as Wily Host agents) are running inside the SolMan Diagnostics agents (SMD agents) that are installed on each SAP host that is monitored by SolMan.

The Onapsis Research Labs found two critical vulnerabilities in the application. The first one is an OS command injection vulnerability that is patched with SAP HotNews Security Note #2969828. This note is the third one in 2020 that has assigned a CVSS score of 10. It affects all CA Introscope Enterprise Manager versions with release 10.7.0.304 or lower. The vulnerability can allow an attacker to inject OS commands and thus gain complete control of the host running the CA Introscope Enterprise Manager. The CVSS score of 10 considers the fact that an exploit can be started remotely and does not require authentication orany privileges.

The second vulnerability, detected by the Onapsis Research Labs, is patched with High Priority Note #2971638, tagged with a CVSS score of 7.5. It allows a remote attacker to bypass authentication if the default passwords for Admin and Guest have not been changed.

After patching, customers with default passwords are forced to set new credentials for Enterprise Manager. Furthermore, the connection between SAP Solution Manager/Focused Run and Introscope must be restored manually. For details, refer to the SAP Security Note.

The second HotNews Note is the well-known SAP Security Note #2622660, announcing another update of the Chromium version that is shipped with SAP Business Client patch. This update patches 25 security issues, seven of them with High Priority.

3a8082e126