JSTL & JAXP Incompatibility Issue

Hi, I have been experiencing problems whilst attempting to use the JSTL Standard Tag Library with the Apache Crimson XML Parser in the classpath. I have tried running the JSTL JSP page without Crimson in the classpath and it works fine. However when included in the classpath and I attempt to view the page I get the error below. According to this page:
http://jakarta.apache.org/taglibs/doc/standard-1.0-doc/GettingStarted.html
the "Standard Taglib requires a JAXP 1.1 or 1.2 compliant parser". It goes on to list Crimson as an example of this. However the Crimson pages states that it supports "JAXP 1.1 minus the javax.xml.transform package."
I would simply use another XML parser, except that I am using the Google API Jar which uses Crimson, thus I cannot remove it from the classpath if I wish to continue using the Google API.
If anyone has any idea how I might solve this problem I'd be keen to hear them,
Thanks very much,
Ross Butler
org.apache.jasper.JasperException: <h3>Validation error messages from TagLibraryValidator for c</h3><p>null: java.lang.IllegalStateException: can't declare any more prefixes in this context</p>
     org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:50)
     org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
     org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:72)
     org.apache.jasper.compiler.Validator.validateXmlView(Validator.java:1549)
     org.apache.jasper.compiler.Validator.validate(Validator.java:1495)
     org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:157)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:267)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:255)
     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:556)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:296)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:245)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:362)

yes, you made a mistake somewhere. There is only one person who can figure out what: you. I suggest a good debugger like the one built into Eclipse to try and figure out where your mistake is.
I know, it is frustrating when something doesn't work the way you expect it to do. It is part of the programming job to suck it up and figure out where you did something wrong. That can take some time, effort and lots of coffee.

Similar Messages

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.

Incompatibility issue - WLC 5508 and ACS 5.4

Hi,
This is my scenario:
Cisco WLC 5508 firmware 7.4.110.20 and ACS 5.4, two WLAN eap/tls, many client can't connect to WLAN and on ACS i receive the following error:
Authentication failed : 11051 RADIUS packet contains invalid state attribute
workaround:
1 -Check the network device or AAA Client for hardware problems.
2-known RADIUS compatibility issues.
3-Check the network that connects the device to ACS for hardware problems
there are some incompatibility issue between WLC and ACS ? the compatibility matrix document for wireless imposes the 7.5 firmware for WLC.
What do you think is possibile ?

Are there any other errors shown in the details of the failed authentication?
We may need to look at service logs in debug mode, opening a TAC case would be the best way to go about this.
Javier Henderson
Cisco Systems

Incompatibility issues with the new flash pplayer

Ever since I installed the new version of flash 11.5 I have had major issues with watching video etc. I am also into astronomy. Myself and many others have paid a lot of money to use Sloohs robotic telescopes in their canary islands observatory.
I now cannot enjoy this because the flash player has compatibility issues with your browser. Me and quite a lot of others are getting rather annyoed this opportunity is being ruined because adobe have released a version of flash without checking it's compatibility with all browsers first.
May I suggest that you contact them and ask that you are notified about new versions and release dates to ensure that you can make necessary amendments to prevent incompatibility issues.
That way lots of angry people like me will not be complaning.

At work, symantec endpoint. At home, norton. Ever since firefox 15, no flash version works except for 11.2. Now that ff18 was pushed out, it "forces" the upgrade to 11.5, and absolutely will not accept anything less. But as with any version of flash that was not 11.2, it just causes firefox to freeze up completely.

Incompatibility issues when saving BW workbook in early excel versions

When saving a BW workbooks to my desktop for example so that I can then send it to a user to view the report I get incompatibility issues when saving workbook to earlier excel versions. I am currently using 2007 and when I save the workbook to Excel 97 - 2003 then I get incompatibility messages. If I ignore these and just save then no one is able to open the workbook. This means that I cannot also save workbooks on the reporting system as those users not using 2007 cannot view them. The message that I get is that 'the features of this workbook are not supported by the earlier features of Excel.'

Hi,
Please refer to this note,
Note 1152092 - Error opening MS Excel 2007 workbook in MS Excel 2003
Usually when you do any formatting feature available in Excel 2007 to the workbook it would throw you the error, not sure if you are formatting the workbook.
Regards,
Mani

AEBS hard drive incompatibility issues

Is there an updated list of incompatible hard drives for the AEBS? I have an external 300GB Seagate that is formatted FAT32 and does not mount. It shows up partially under the DISKS menu in Airport Utility, meaning it shows that there is storage connected but doesn't show a volume. I thought the new 5.2.1 update was going to do the trick since it dealt with incompatibility issues but not so. I have tried everything except reformatting because I cannot lose all the info that's on the drive currently. Any help would be appreciated.

I've checked out your list and posted my experiences.
From the tests that I've run over the last week or so, the Macally PHR-100AC 3.5" HDD enclosure should work. Failures 'seems' to point specifically to the hard drive used.
I have now used 4 different drives (different sizes, manufacturers etc..) in 2 Macally cases (both with updated firmware) and the only failure - via USB but not FireWire - was the Western Digital Caviar SE WD1600. Reformatting it with WD's utility is Windows XP via Bootcamp cleared up the issue with the drive and is now fully functional and consistent under Mac OS X and through the AEBS. I still have one more WD1600 to look at.
Aug 23 09:43:06 Patricks-iMac-Core-Duo-2 kernel[0]: USBF: 459.963 AppleUSBUHCI[0x39ce000]::DoControlTransfer sync request on workloop thread. Use async!
Aug 23 09:43:06 Patricks-iMac-Core-Duo-2 kernel[0]: USBF: 460.271 AppleUSBUHCI[0x39ce000]::DeviceRequest - buffer dmaCommand (0x3b76900) already had memory descriptor (0x39a6100) - clearing

JSTL 1.1 issue with Weblogic 9.2

I am having tough time to make JSTL 1.1 work with Weblogic 9.2.Here the issue goes
When i user JSTL core tags like out,forEach weblogic is unable to understand the EL and throwing a compile time exception saying can't read request time values.
However the same page worked fine when i rolled back to JSTL 1.0 and weblogic 8.1.
I couldnt able to understand why JSTL 1.1 is not working in Weblogic 9.2.I assume weblogic 9.2 comes with servlet 2.4 and JSP 1.2.So JSTL 1.2 should work fine.
Am i ignoring anything involved with new JSP specs and JSTL
OR
Is this a bug with Weblogic 9.2 ?
Any comments highly appreciated.
Thanks,
Mallik

hey check the servlet spec version you're using in your web.xml. I think you want 2.3 not 2.4.

Has the recent Itunes upgrade caused incompatibility issue with APPLE TV 1st gen?

after recent upgrade to itunes, itunes no longer recognizes data on my apple tv 1st gen....but the Apple TV still has them loaded. additonally this new itunes does not let me resync new songs or movies, etc. thoughts? thanks!

I'm having the exact same issue. Nothing in the "Music" menu except "My Music". I Noticed it this afternoon when I woke my Apple TV from standby. The disappearance, in my case, was not related to a reset. My Apple TV has not been reset since the power went out here several weeks ago. Though I obviously don't know for sure, I'm guessing that it's some kind of store problem and we most likely won't be able to correct it from our end.

Macbook pro mid 2009 incompatibility issues

k i got a macbook pro 17inch mid 2009 the only os that seem to work with this mac is mac os x lion version 10.7 (11A511) i tried mountain lion, maverick and yosemite and the only way that i could use this other os is if i boot in safe mode last time i installed yosemite i uploaded a kernel panic result and a very generous gentlemen told me it was a problem with my GPU and or memory now my question is and i might sound like a noob and apologize for that in advance is why does it work in lion 10.7 and not on the other os did apple change something on this updates? also when i update lion to the last lion update the same thing happens
here's my kernel panic for when i had yosemite on the same mac maybe this will also help
Anonymous UUID:       9C833C45-DC0A-CF26-7029-AD4C373CFD8A
Fri Feb 6 01:33:17 2015
*** Panic Report ***
panic(cpu 1 caller 0xffffff801541e80a): Kernel trap at 0xffffff7f96e9b483, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000010, CR3: 0x000000007c64a000, CR4: 0x0000000000002660
RAX: 0x674c25fc9cce0001, RBX: 0xffffff8045b2d000, RCX: 0xffffff80699c5000, RDX: 0xffffff806ee0b908
RSP: 0xffffff806ee0bac0, RBP: 0xffffff806ee0bac0, RSI: 0x0000000000000000, RDI: 0x0000000000000000
R8: 0x000000000000002b, R9: 0xffffff801dd4804f, R10: 0x0000000000000010, R11: 0x000000000000002b
R12: 0x0000000000000000, R13: 0xffffff801de27800, R14: 0xffffff8045b2d000, R15: 0xffffff8045b2d000
RFL: 0x0000000000010293, RIP: 0xffffff7f96e9b483, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000010, Error code: 0x0000000000000000, Fault CPU: 0x1
Backtrace (CPU 1), Frame : Return Address
0xffffff806ee0b770 : 0xffffff801533a811
0xffffff806ee0b7f0 : 0xffffff801541e80a
0xffffff806ee0b9b0 : 0xffffff801543a443
0xffffff806ee0b9d0 : 0xffffff7f96e9b483
0xffffff806ee0bac0 : 0xffffff7f96e8492a
0xffffff806ee0bb10 : 0xffffff7f96e84878
0xffffff806ee0bb30 : 0xffffff7f96e60116
0xffffff806ee0bb70 : 0xffffff7f95e396df
0xffffff806ee0bbc0 : 0xffffff7f95e395f2
0xffffff806ee0bbe0 : 0xffffff7f95e3d90a
0xffffff806ee0bc70 : 0xffffff7f95e358ac
0xffffff806ee0bcb0 : 0xffffff7f95e85fe8
0xffffff806ee0bd00 : 0xffffff80158b85b1
0xffffff806ee0bd50 : 0xffffff80158ff0b5
0xffffff806ee0bdc0 : 0xffffff80153ea95e
0xffffff806ee0be10 : 0xffffff801533e91c
0xffffff806ee0be40 : 0xffffff80153235a3
0xffffff806ee0be90 : 0xffffff8015333e8d
0xffffff806ee0bf10 : 0xffffff801540a142
0xffffff806ee0bfb0 : 0xffffff801543ac66
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(2.4.1)[6D99A3BE-D531-3780-880B-13F2FC894A4A]@0 xffffff7f95e2b000->0xffffff7f95e65fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[87711C74-47D5-3545-8A62-035E1C7C4198]@0xffffff 7f95b24000
         com.apple.nvidia.classic.NVDAResmanTesla(10.0)[796AE430-39FB-3255-8161-D52AFA28 EE2B]@0xffffff7f95e82000->0xffffff7f960ebfff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[87711C74-47D5-3545-8A62-035E1C7C4198]@0xffffff 7f95b24000
            dependency: com.apple.iokit.IONDRVSupport(2.4.1)[F4738C55-B507-3627-A9CA-3D29A5230A03]@0xff ffff7f95e72000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[6D99A3BE-D531-3780-880B-13F2FC894A4A]@0 xffffff7f95e2b000
         com.apple.GeForceTesla(10.0)[97A18479-CC43-3073-AEB2-C5C92195067A]@0xffffff7f96 e5c000->0xffffff7f96f29fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[87711C74-47D5-3545-8A62-035E1C7C4198]@0xffffff 7f95b24000
            dependency: com.apple.iokit.IONDRVSupport(2.4.1)[F4738C55-B507-3627-A9CA-3D29A5230A03]@0xff ffff7f95e72000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[6D99A3BE-D531-3780-880B-13F2FC894A4A]@0 xffffff7f95e2b000
            dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.0)[796AE430-39FB-3255-8161-D52AFA 28EE2B]@0xffffff7f95e82000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
14A379b
Kernel version:
Darwin Kernel Version 14.0.0: Sat Sep 27 03:58:47 PDT 2014; root:xnu-2782.1.97~11/RELEASE_X86_64
Kernel UUID: D1F807E1-A660-3126-96DF-6A9E65444DA3
Kernel slide:     0x0000000015000000
Kernel text base: 0xffffff8015200000
__HIB text base: 0xffffff8015100000
System model name: MacBookPro5,2 (Mac-F2268EC8)
System uptime in nanoseconds: 77869146695
last loaded kext at 77595893148: com.apple.driver.AppleHWSensor 1.9.5d0 (addr 0xffffff7f974c1000, size 36864)
loaded kexts:
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.driver.AppleHDAHardwareConfigDriver 266.5
com.apple.driver.AppleTyMCEDriver 1.0.2d2
com.apple.driver.AGPM 100.14.32
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleHDA 266.5
com.apple.filesystems.autofs 3.0
com.apple.iokit.IOBluetoothSerialManager 4.3.0f9
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.AppleMikeyDriver 266.5
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleHV 1
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleLPC 1.7.3
com.apple.GeForceTesla 10.0.0
com.apple.driver.AppleSMCLMU 2.0.4d1
com.apple.driver.AppleUpstreamUserClient 3.6.1
com.apple.nvidia.NVDAStartup 10.0.0
com.apple.iokit.IOBluetoothUSBDFU 4.3.0f9
com.apple.driver.AppleMuxControl 3.7.19
com.apple.driver.AppleBacklight 170.4.12
com.apple.driver.AppleMCCSControl 1.2.10
com.apple.driver.SMCMotionSensor 3.0.4d1
com.apple.driver.AppleUSBTCButtons 240.2
com.apple.driver.AppleUSBTCKeyEventDriver 240.2
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.driver.AppleIRController 327.5
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.iokit.SCSITaskUserClient 3.7.0
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.6.5
com.apple.driver.AppleFWOHCI 5.5.2
com.apple.driver.AppleUSBHub 705.4.1
com.apple.driver.AppleAHCIPort 3.0.7
com.apple.nvenet 2.0.22
com.apple.driver.AppleUSBEHCI 705.4.14
com.apple.driver.AppleUSBOHCI 656.4.1
com.apple.driver.AirPort.Brcm4331 800.20.24
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleACPIButtons 3.1
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 3.1
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 218.0.0
com.apple.nke.applicationfirewall 161
com.apple.security.quarantine 3
com.apple.security.TMSafetyNet 8
com.apple.driver.AppleIntelCPUPowerManagement 218.0.0
com.apple.AppleGraphicsDeviceControl 3.7.19
com.apple.driver.DspFuncLib 266.5
com.apple.kext.OSvKernDSPLib 1.15
com.apple.iokit.IOAudioFamily 200.6
com.apple.vecLib.kext 1.2.0
com.apple.kext.triggers 1.0
com.apple.iokit.IOSerialFamily 11
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.iokit.IOSurface 97
com.apple.iokit.IOBluetoothFamily 4.3.0f9
com.apple.driver.AppleHDAController 266.5
com.apple.iokit.IOHDAFamily 266.5
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.IOPlatformPluginFamily 5.8.0d49
com.apple.nvidia.classic.NVDANV50HalTesla 10.0.0
com.apple.nvidia.classic.NVDAResmanTesla 10.0.0
com.apple.iokit.IOUSBUserClient 705.4.0
com.apple.iokit.IOFireWireIP 2.2.6
com.apple.driver.AppleGraphicsControl 3.7.19
com.apple.driver.AppleBacklightExpert 1.1.0
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.driver.AppleSMBusController 1.0.13d1
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.driver.AppleSMC 3.1.9
com.apple.iokit.IOSCSIBlockCommandsDevice 3.7.0
com.apple.iokit.IOUSBMassStorageClass 3.7.0
com.apple.driver.AppleUSBMultitouch 245.2
com.apple.iokit.IOUSBHIDDriver 705.4.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.7.0
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.iokit.IOAHCISerialATAPI 2.6.1
com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.0
com.apple.driver.AppleUSBMergeNub 705.4.0
com.apple.driver.AppleUSBComposite 705.4.9
com.apple.iokit.IOFireWireFamily 4.5.6
com.apple.iokit.IOAHCIFamily 2.7.0
com.apple.driver.NVSMU 2.2.9
com.apple.iokit.IOUSBFamily 705.4.14
com.apple.iokit.IO80211Family 700.52
com.apple.iokit.IONetworkingFamily 3.2
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.DiskImages 389.1
com.apple.iokit.IOStorageFamily 2.0
com.apple.iokit.IOReportFamily 31
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 3.1
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
com.apple.kec.Libm 1
com.apple.kec.pthread 1
Unable to gather system configuration information.Model: MacBookPro5,2, BootROM MBP52.008E.B05, 2 processors, Intel Core 2 Duo, 2.8 GHz, 2 GB, SMC 1.42f4
Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB
Graphics: NVIDIA GeForce 9600M GT, NVIDIA GeForce 9600M GT, PCIe, 512 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353637334548312D4346382020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.106.98.100.24)
Bluetooth: Version 4.3.0f9 14854, 3 services, 27 devices, 0 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: WDC WD1600BEVS-00UST0, 160.04 GB
Serial ATA Device: HL-DT-ST DVDRW GS21N, 3.92 GB
USB Device: Built-in iSight
USB Device: USB 2.0 SATA BRIDGE
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Apple Internal Keyboard / Trackpad
USB Device: IR Receiver
Thunderbolt Bus:

It would appear there has been a hardware issue with the GPU. I recommend you make a copy of this panic report and take it along with the computer to your local Apple shop for repai

What incompatability issues exist with Photoshop Elements 4.0 and windows 7?

I have been notifiied about an incombatability issue with windows 7 and Photoshop Elements 4.0. What do I lose if I use it? Because there are no help suggestions on the Adobe site does any one have any information?

Moving this discussion to the Photoshop Elements forum.

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.

BI 4.1 SP03 Patch 01 incompatibility issue with DS 4.2 SP01

Hello,
this message it's only to advise that the error "Unable to locate BOE platform components. Install or reinstall BOE platform and retry" when you try to open "Data Services Designer" with the following software can be solved uninstalling Patch 01 of BI 4.1 SP03
Windows 7 SP01
SAP BO BI Platform v4.1 SP03 Patch 01 (client components)
SAP BO Data Services v4.2 SP01 Patch 04 (client components)
Hope this helps
Regards

Hello Ilias,
yes, we opened it and they told me this:
Hello Rubén,
Thanks for the confirmation that without the patch the installation
works - this is as we expected it. Your observations on the
combinations you were trying have been noted.
Once the patch level hass been approved (post-QA etc) then the KNBA
will be adjusted appropriately to reflect any issues and/or bugs that
might be discovered in QA and fixes applied.
Regards
Rubén

Flex incompatibility issue with SDK 3.5.0.12683 and IE6

Anyone have experience with issues for IE6 and Flex SDK 3.5.0.12683?
As a secondary issue, does anyone know of a way to force a browser cache refresh?
thanks
Simon

Add a random number as a parameter to the url.
Something like:
url = url + "?t=" + new Date().time;

Jstl resource bundle issue

Hi, I am using JSTL resource bundle. It is defined in
web.xml:
<context-param>
<param-name>
javax.servlet.jsp.jstl.fmt.localizationContext
</param-name>
<param-value>
package.ApplicationResources
</param-value>
</context-param>
My question is that if I have two or more resource
bundle properties such as
ApplicationResourcesBase.properties,
ApplicationResourcesApp.properties, how do I regiester
them in web.xml, and how do I call it in my JSP using
fmt tag?
Thanks,
Hong

Same problem...
It looks like a bug

Incompatability Issues MAC OS 10.4.10 With USB headphones

I bought iListen so I could type more quickly as I have some disability issues and type very slowly. I had a lot of trouble training iListen. I bought a package which included a Platronics USB headset and USB Mic fromthe Apple online store. After many issues I was able to find out from Plantronics that MAC OS 10.4.10 has some compatability issues with USB Microphones. After making sure the System Preferences are correctly chosen in Sound and Speech Panes you can follow the steps below, I hope this helps some others to avoid this frustration.
The following applies only to Macintosh computers running Mac OS X 10.4.10.
If you experience no transmit (i.e. the mic doesn't seem to work), please try the following:
1) Make sure your Plantronics microphone is plugged into an open USB port on your computer.
2) Launch "Audio MIDI Setup.app." (You will find this application in Applications> Utilities.)
3). In System Settings, select "Plantronics Headset" as the default input.
4). In "Properties For:" select "Plantronics Headset."
5). In the bottom right area of the window, uncheck "Mute."

I have had communication from MacSpeech which indicated they actually gave the solution to Plantronics and were aware of the issues. I did not realize that there was an issue that was not with me because it only happened some of the time that my computer muted the microphone and resorted to the built in mic! Hope this helps someone else

JSTL & JAXP Incompatibility Issue

Similar Messages

Maybe you are looking for