Wily Instrumentation version incompatibility

First a few vitals:
Solman 7.01(EHp1 SP4) SP 20 for ST400
Enterprise Manager version 8020
Managed system (JAVA):
7.11 Diag Agent (SMD, connected and running succesfully to the Managing system)
Introscope Agent 8.1 installed
In the SMD Diagnostics Setup--Introscope Agent, I'm getting a valid connection between the J2EE Node of my Managed system, but for some reason my versioning is incorrect:
Selected Enterprise Manager version 8020 and agent instrumentation version ISAGENT.7.2.0.0-2007-11-20 are not compatible
My Wily logs suggest that I have the correct version of the agent installed and running but there seems to be some sort of disconnect with the instrumentation.
Any suggestions?

I think I have it figured out..
I'm actually trying to setup the Introscope Agent for the managed system using SolMan Diag (localhost:50000/smd/admin)
What I found is that in my Managing system, I have an old version of the ISAGENT installed on the system. Updating that component should help the situation.

Similar Messages

IMP Version incompatibility between 10.2.0.4 and 10.1.0.5.0?

Dear all,
I am trying to run to do an import from oracle 10.2.0.4 to 10.1.0.5.0
So on the source server, I did an exp of the db
And on the destination server, I am doing an IMP
I am having the below error:
IMP-00008: unrecognized statement in the export file:
Could it be related to version incompatibility??

Import: Release 10.1.0.5.0 - Production on Tue Feb 16 09:06:51 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Username: uwave
Password:
Connected to: Oracle Database 10g Release 10.1.0.5.0 - Production
Import file: expdat.dmp > 200100204.dmp
Enter insert buffer size (minimum is 8192) 30720> 150000
Export file created by EXPORT:V10.02.01 via conventional path
import done in US7ASCII character set and AL16UTF16 NCHAR character set
import server uses WE8ISO8859P1 character set (possible charset conversion)
List contents of import file only (yes/no): no >
Ignore create error due to object existence (yes/no): no >
Import grants (yes/no): yes >
Import table data (yes/no): yes >
Import entire export file (yes/no): no >
Username: uwave
Enter table(T) or partition(T:P) names. Null list means all tables for user
Enter table(T) or partition(T:P) name or . if done: PRODUCTITEM
Enter table(T) or partition(T:P) name or . if done:
. importing UWAVE's objects into UWAVE
IMP-00008: unrecognized statement in the export file:

Unable to restore SAP backup due to br*tools version incompatibility

Hi Everyone...
Our SAP 4.7 production server is taking online backup to sapbackup folder.
for restoring the data to SAP 4.7 production-dr server, I copied from production\sapbackup folder to production-dr\sapbackup folder.
Further, I installed brtools 6.20 version successfully on production-dr and while restoring data in production-dr server using brrestore command. I was receiving an error as version incompatibility and also couldn't find br*tools 6.40 in SAP market place.
Can you please address the following :-
How can i restore data successfully from production to production-dr ?
Regards,
Sridhar.

Hi Sridhar
Could you refer the SAP Note 12741 - Current versions of BR*Tools
Regards
SS

SM Wily Introscope Version 8 doc question

We also installed Wily Introscope Version 8, however there was a part mention as below
The Solution Manager Diagnostics provides an application that performs the setup of the
Introscope bytecode agent for Java automatically. This section explains the steps to run
the setup. Before you can run the Introscope agent setup, the setup wizard for the
managed system must have been executed.
1. Enable Maintenance Mode on SMD.
2. Deploy ISAGENTSMD*.SCA using SDM.
3. Disable Maintenance Mode on SMD.
4. Launch the Introscope Setup application: Diagnostics Setup -> Managed Systems ->
Introscope Agent. Your screen will look similar to the image below:
Questions:
1) How do I go into SMD ? I did use http://<SMserverFQDN>:50000/smd however I only get a header but blank content body in IE or FireFox? Where do I enable maintenance mode?
2) Where do I launch the Introscope Setup Application: Diagnostics Setup ?
I can't find it under Introscope workstation console.
Thanks.

Hi,
Regarding your questions, please kindly check
Root Cause Analysis Installation and Upgrade with SOLMAN_SETUP
>>>
from https://websmp202.sap-ag.de/diagnostics.
Hope this helps.
Cheers
SH

ITunes match gave me two identical copies of the instrumental version - want words!

Imogen Heap's "Ellipse" featured two "CD's" - One featured all her songs sung by her - The other featured all her songs as instrumentals. When syncing with iCloud, iTunes Match gives me access to only the instrumental version of all songs...twice! So now I only have access to two identical copies of the instrumental tracks - no word tracks - help :-(

The original versions are still in your iTunes library, so they haven't taken anything away from you.
It does create problems if you want them on your iOS device though. Unfortunately, I can't give you any idea how to get them on there short of turning match off.
Sorry, it is a problem at the moment, and you are not alone.

Version incompatibility issue with Interop.SAPbobsCOM.dll in SBO 2004

Hi,
I have encountered an incompatibility issue in DI API 2004 across different patch level-versions. Originally, I developed an application in SBO 2004 pl4 environment. Now, some of the customers who were installing the application, notified me that the application has a login problem. It turned out that the CompanyClass.connect() method returns an error message "object reference not set to an instance of an object", when the DI API version installed in the production environment is higher (in this case, pl7) than the DI API version which was used in the development environment.
I figured out that the problem can be fixed by replacing the Interop.SAPbobsCOM.dll file in the application directory by a newer version that reflects the DI API that is installed in the system. However, it seems a rather lousy workaround, if the customer needs to manually replace the dll. Maybe the installer could be customized to "sniff" the correct DI API level, but this too would be a pretty kludgy solution.
Does anyone know a better solution to this problem ?
Regards,
Henry

normally this is not a problem as long as they don't change the signatures on the DI-API (which they said they wouldn't) but it appears in P5 they changed that signature... we noticed some enums that got added and a few minor changes.

Wily Introscope Version for Solution Manager 7 SPS 17

Hi
We have a solution manager 4 (now 7) running on an ABAP stack only, this was recently upgraded from Solution Manager 3.2 which was installed 3 years ago as ABAP stack only, this server was never powerful enough to have the Java stack added and the project did not require it.
I am now looking to migrate this ABAP Solution Manager 7 to a new server, using ABAP & JAVA so I can make use of Solution Managaer tools like Diagnostics, RCA, WILY etc.
On a sandpit copy I have migrated the ABAP instance to a more powerful server and added the Java Instance from the Solution Manager 4 Installation Master, so I now have a dual stack SM 4, I have patched this to SP17.
I am looking to install Wily Introscope for monitoring, I have read Note 797147 - Wily Introscope Installation for SAP Customers, where it says you should always use the latest version of Wily, which is 8.0.2, but looking at the note, the downloads for Introscope Enterprise Manager and Introscope Workstation are from SAP SOLUTION MANAGER 7.0 EHP 1, but I am not running Solution Manager on EHP1, I am on SP Stack 17.
Looking in the SWDC there are downloads in SAP SOLUTION MANAGER 7.0 -> Entry by Component -> Solution Manager JAVA Stack -> WILY INTROSCOPE ENTPR MGR 8
Is this what I should be using for my SP Stack 17, or should I use the EHP1 version?
Also, setting up the Solution Manager Diagnostics, is there a setup PDF for Solution Manager 7 SP17 ? I cannot find a setup guide for this release, most are for EHP1, I would rather not have to implement EHP1 as part of this migration !
Thanks for any help.
Paul.

Hi Bhudev
Thanks for the reply, I presumed it was the Wily introscope 8 without the EHP1 I required.
As for installation guide, I have think you have misunderstood my question, I already have the wily installation guide from the note location, I wanted to know if there is any Solution Manager Diagnostics setup guides for SP17 ?
When I use transaction SOLMAN_WORKCENNTER --> System Monitoring --> Solution Manager Diagnostics --> Diagnostics System --> Diagnostics Setup --> Setup Wizard
the first 2 (of 23) setups are failing :
SSO The value of profile parameter login/accept_sso2_ticket could not be checked
BI Cannot invoke CCMSBISETUP on host localhost
Warning :
User(BI) Role SAP_BI_E2E does not exist
Then it says :
To complete the Diagnostics Setup, you should perform the following operations as documented in Diagnostics Setup Guide
I cannot find this Diagnostics Setup Guide for SP17 ?
The installation guides are mainly for EHP1, media library under sap-ag.de/diagnostics does not show this setup guide, Master Installation guide does not mention it, so was wondering if anyone could point me in the right direction for this guide ?
Thanks,
Paul.

I installed Firefox4 and I get an error message everyday about the platform version incompatibility of the XUL, which forces me to re-install firefox everyday.

Since I installed Firefox 4 I keep on getting the error "Platform version 2.0 not supported with...". Is there any way to update the XUL file? I do re-instalations everyday (after the re-instal, firefox runs smooth)

Do a clean (re-)install:
* Download a fresh Firefox copy and save the file to the desktop.
* Firefox 4.0: http://www.mozilla.com/firefox/all.html
* Uninstall your current Firefox version and remove the Firefox program folder before installing that copy of the Firefox installer.
* Don't remove personal data if you uninstall the current version.
* It is important to delete the Firefox program folder to remove all the files and make sure that there are no problems with files that were leftover after uninstalling.
Your bookmarks and other profile data are stored elsewhere (not in the Firefox program folder) and won't be affected by a reinstall, but make sure that you do not select to remove personal data if you uninstall Firefox.

QuickTime for Windows - version incompatibility with Safari 5.1?

This issue involves a Dell Laptop running Windows XP Pro, SP3.
I installed Quicktime and iTunes, and both were functioning fine.
I then installed Open Office, a couple of Windows security updates. and then Safari 5.1
Immediately after the above installations, neither QuickTime nor iTunes could play mp4 video, and QuickTime could not play m4a or mp3 audio.
I made the assumption that it must have had something to do with Open Office, or perhaps Safari 5.1.
I completely uninstalled all Apple software on the PC. I then installed Open Office and QuickTime, in that order.
QuickTime once again could play both mp4 video and m4a or mp3 audio.
I hoped that I had fixed the problem.
However, immediately after installing Safari 5.1 once again, Quicktime again could not play video or audio.
The time pointer moves in real time, but there is no audio, and video shows a new frame every 2 seconds (approx.), but no sound.
The QuickTime version is 7.6.7.
Is there an absolute need to install the "Safari + Quicktime" installer to avoid this type of issue? My main computer is a Mac, and I'm pretty sure
I've updated Safari on occasion w/o first installing the latest Quicktime. Perhaps the issue is more complex with Windows.
Thanks for reading

If you have Private Browsing enabled, that's why you aren't staying logged into websites. Same with Google maps.
Private Browsing doesn't "remember" AutoFill information.
Click History in the menu bar then click: Clear History

Have Acrobat XI Std, installation of Acrobat XI Pro fails, version incompatibility

Running Windows 7 Pro on work Thinkpad.
Trial version of Acrobat XI Pro as of Dec 4, 2014 is 11.0.07
Licensed version of installed Acrobat XI Std is 11.0.09
Installer downloads, but when the splash panel displays and I press Next, I get the message that a more functional version is available and it bails.
Obvious why the error occurred. Makes me wonder if Pro features are hidden inside Std, the way IBM used to take the DP Manager out to lunch while the CE flipped a switch for more MIPS upgrade. ;-)
I simply want to check out the multi-media features before committing to upgrade.
Will try using another computer, thought you would like to know about the problem.

Sadly you cannot run Acrobat Standard and Acrobat Pro at the same time. The message is rather the wrong way round but basically a hint in the right direction.
You would need to uninstall Acrobat Standard. Be sure you have EVERYTHING you need to reinstall including disks and serial numbers before considering this!

AD-Exchange Connector versions Incompatibility Issues : Extremely URGENT

Hi,
We have tested our code in dev environment (AD, Exchange versions 2003). But in production env, the root context for the two are different from those of dev environment.
In dev env: root context are: DC=company,DC=devxyz for ADITResource,Exchange
In prod env: root context are: DC=company,DC=devxyz for ADITResource ; DC=devxyz for Exchange.
Exchange being dependent on AD, when AD is provisioned, Exchange fetches the ObjectGUID of AD User, and searches in parent root context (DC=devxyz) which return some garbage value -50 corresponding to null value. SInce ObjectGUID is not fetched, Exchange cannot be provisioned.
Please give some pointers for this issue. It is very critical at this stage as we cannot do any changes in the existing configurations.
Regards,
Deepika

Exchange fetches the ObjectGUID of AD User, and searches in parent root context (DC=devxyz) which return some garbage value -50 corresponding to null value. SInce ObjectGUID is not fetched, Exchange cannot be provisioned.If it is facing issue only with objecrGUID then You can write your custom JNDI code to fetch this value and update in some field.
Just make a task in Exchange Process Definition which will do this thing.

Operating system VERSION incompatability while installing SAP ECC 6.0 SR3

<h3>what is the dump of M.S. SQL SERVER required for installing SAP ECC 6.0 SR3 ABAP system on WINDOWS SERVER 2008 R2 ENTERPRIZE 6.1 VERSION.</h3>
we installed the MS sql version: 10.50.1702 (dump number 51039339) on our Operating system version was Windows Server 2008 R2 enterprise (version 6.1) and while we are trying to install sap using SAP INST we got one high priority prerequisites analysis message saying
<h3> MESAGE "The following operating system versions is supported: windows server 2003(i.e version 5.2) and Windows server 2008(ie 6.0). current oprating version: version 6.1 service pack 0.0"
Can any one help me what is the problem, Is it the operating system or with the MS SQL server and please tell me what we should do in order to rectify this issue</h3>
Please also tell me how to check COMPATABILITY between OS, DATABASE and SAP. we have gone through PAM but not able to find. Can any one help me.

mahesh.boby63 wrote:
> Why we sholud go for modified kernel DVD procedure on windows server operaating system ?
It's not about 'windows' server, but for 'windows 2008 R2' server.
Kernel files included in the 'Installation Media' are by default the old/low patch level not released fully compatible with 'new platforms' like 2008 R2 - which may cause some problems 'during' installation as well.
So, using modified kernel DVD you get two advantages -
1. You are able to avoid 'those' problems during installation.
2. You don't have to go for an explicit kernel upgrade just after the installation.
Thanks

Version incompatibility JNDI error with Portal 4.0 and Server 9.0

We have a JSP portal application running on Portal 4.0/Server 6.1. The application invokes EJB's on a separate WebLogic 6.1 server. This works fine. We are looking to upgrade our back-end WebLogic 6.1 servers while maintaining our Portal 4.0 web application server. We ran some tests using portal 4.0 JSP's invoking EJB's on WebLogic server 9, but we are getting the following error...
javax.naming.CommunicationException [Root exception is weblogic.socket.UnrecoverableConnectException: [Login Failed: Incompatible version: this server '9.0.0' client '6.1.4']]
This does not make sense since, according to BEA 9.0 documentation, this configuration should work.

We have a JSP portal application running on Portal 4.0/Server 6.1. The application invokes EJB's on a separate WebLogic 6.1 server. This works fine. We are looking to upgrade our back-end WebLogic 6.1 servers while maintaining our Portal 4.0 web application server. We ran some tests using portal 4.0 JSP's invoking EJB's on WebLogic server 9, but we are getting the following error...
javax.naming.CommunicationException [Root exception is weblogic.socket.UnrecoverableConnectException: [Login Failed: Incompatible version: this server '9.0.0' client '6.1.4']]
This does not make sense since, according to BEA 9.0 documentation, this configuration should work.

Version incompatibility with UCM and WLS

Dear All,
I just have some confusion.
I have installed WLS 10.3.4 and houses the Webcenter 11G PS3 (11.1.14) also.
But when I download the UCM 11GR1, I notice that it says it is not compatible with my Weblogic.
I think I have downloaded the wrong version, I am looking for UCM 11G download to match my already
setup domain but when I check the older release at OTN, i only can find Oracle Universal Content Management 10gR3 Downloads.
Is this the same or is this copatible with my WLS?
Thanks

Hi Jose,
This is a known interoperability problem with MS SOAP toolkit, which send what is refered to as untyped request. You have an option to accept untyped request in oc4j - look at section 12.2 of the 10.1.2 Web services guide [http://download-west.oracle.com/docs/cd/B14099_04/web.1012/b14027/custom.htm#BABEJDEC]. The tag is <accept-untyped-request> .
Hope this helps,
Eric

Version incompatibility error in OWB while login to Design Center

Hi,
I have created a Warehouse Builder repository on database(Version 11.1.0.7) server and installed Standalone OWB 11.2 on the client machine. However while connection from client pc it is throughing error like:
API5036: client version 11.1.0.6.0 is not compatible with repository version 11.1.0.7.
Please help me on this issue.
Thanks.
vinod
Edited by: Vinod Ranjan on 27 Dec, 2011 11:32 PM

You need to access the repository version with a compatible client.
Which OWB version are you trying to use?
There is a section below on using the standalone install which will let you use OWB 11gR2 for example with a 10gR2, 11gR1 or 11gR2 database.
http://docs.oracle.com/cd/E11882_01/owb.112/e17130/setup_windows.htm#CHDGDCGD
Cheers
David

Wily Instrumentation version incompatibility

Similar Messages

Maybe you are looking for