Re: Invalid branch target position offset for goto

Attention to all players software.groupbrowser.com, and those
people who
cannot without MMORPG. The new game portal PROMMORPG, soon
opens new
game servers: 1. Rising Force Online (RF Online);2. LineAge
II;3.
Perfect World;4. World of Warcraft;All games are absolutely
free, no
playing players from administration. The newest games and the
advanced
equipment for them. Fast communication channels and reliable
data
centers. All can be found it on a game portal
http://www.prommorpg.com

Attention to all players software.groupbrowser.com, and those
people who
cannot without MMORPG. The new game portal PROMMORPG, soon
opens new
game servers: 1. Rising Force Online (RF Online);2. LineAge
II;3.
Perfect World;4. World of Warcraft;All games are absolutely
free, no
playing players from administration. The newest games and the
advanced
equipment for them. Fast communication channels and reliable
data
centers. All can be found it on a game portal
http://www.prommorpg.com

Similar Messages

  • Branch target offset too large for short

    Error :
    I am getting the error "Branch target offset too large for
    short" in coldfusion.
    What we are trying to do?
    We are concatenating large numbers of text. We where building
    a lengthly string. We ended up using mutliple variables and
    appending them together at the end to get it to work.
    Appending the lengthy string and writing into a file.
    Just to breif you this is a survey questions and answers we
    are generating text file with tab seperated as delimeters.
    e.g.
    The string I am using is
    <cfset Questions =
    Number#TabChar#Q1#TabChar#Q2A#TabChar#Q2B#TabChar#Q2C#TabChar#Q3A#TabChar#Q3B#TabChar#Q3C #TabChar#Q3D#TabChar#Q3E#TabChar#Q3F#TabChar#Q3G#TabChar#Q4A1#TabChar#Q4A2#TabChar#Q4A3#Ta bChar#Q4A4#TabChar#Q4A5#TabChar#Q4A6#TabChar#Q4B1#TabChar#Q4B2#TabChar#Q4B#TabChar#Q4B4#Ta bChar#Q4B5#TabChar#Q4B6#TabChar#Q4C1#TabChar#Q4C2#TabChar#Q4C3#TabChar#Q4C4#TabChar#Q4C5#T abChar#Q4C6#TabChar#Q4D1#TabChar#Q4D2#TabChar#Q4D3#TabChar#Q4D4#TabChar#Q4D5#TabChar#Q4D6# TabChar#Q4E1#TabChar#Q4E2#TabChar#Q4E3#TabChar#Q4E4#TabChar#Q4E5#TabChar#Q4E6#TabChar#Q4F1 #TabChar#Q4F2#TabChar#Q4F3#TabChar#Q4F4#TabChar#Q4F5#TabChar#Q4F6#TabChar#Q4G1#TabChar#Q4G 2#TabChar#Q4G3#TabChar#Q4G4#TabChar#Q4G5#TabChar#Q4G6#TabChar#Q4H1#TabChar#Q4H2#TabChar#Q4 H3#TabChar#Q4H4#TabChar#Q4H5#TabChar#Q4H6#TabChar#Q4I#TabChar#Q4J#TabChar#Q4K#TabChar#Q5A1 #TabChar#Q5A2#TabChar#Q5A3#TabChar#Q5A4#TabChar#Q5A5#TabChar#Q5A6#TabChar#Q5B1#TabChar#Q5B 2#TabChar#Q5B3#TabChar#Q5B4#TabChar#Q5B5#TabChar#Q5B6#TabChar#Q5C1#TabChar#Q5C2#TabChar#Q5 C3#TabChar#Q5C4#TabChar#Q5C5#TabChar#Q5C6#TabChar#Q5D1#TabChar#Q5D2#TabChar#Q5D3#TabChar#Q 5D4#TabChar#Q5D5#TabChar#Q5D6#TabChar#Q5E#TabChar#Q5F#TabChar#Q5G#TabChar#Q6A#TabChar#Q6B# TabChar#Q6C#TabChar#Q6E#TabChar#Q6F#TabChar#Q6G#TabChar#Q6H#TabChar#Q6I#TabChar#Q6J#TabCha r#Q6K#TabChar#Q7A1#TabChar#Q7A2#TabChar#Q7B1#TabChar#Q7B2#TabChar#Q7C#TabChar#Q7D#TabChar# Q8A#TabChar#Q8B#TabChar#Q8C#TabChar#Q8D#TabChar#Q8E#TabChar#Q8F#TabChar#Q8G#TabChar#Q8H#Ta bChar#Q9A1#TabChar#Q9A2#TabChar#Q9B1#TabChar#Q9B2#TabChar#Q9C1#TabChar#Q9C2#TabChar#Q9D1#T abChar#Q9D2#TabChar#Q9E1#TabChar#Q9E2#TabChar#Q9H1#TabChar#Q9H2#TabChar#Q9I1#TabChar#Q9I2# TabChar#Q9J1#TabChar#Q9J2#TabChar#Q9K1#TabChar#Q9K2#TabChar#Q9L1#TabChar#Q9L2#TabChar#Q9M# TabChar#Q9N#TabChar#Q9O#TabChar#Q9P#TabChar#Q9Q#TabChar#Q9R#TabChar#Q9S#TabChar#Q10A#TabCh ar#Q10B#TabChar#Q10C#TabChar#Q10E#TabChar#Q10F#TabChar#Q10G#TabChar#Q10H#TabChar#Q10I#TabC har#Q10J#TabChar#Q10K#TabChar#Q11A#TabChar#Q11B#TabChar#Q11C#TabChar#Q11D#TabChar#Q11E#Tab Char#Q11F#TabChar#Q11G#TabChar#Q11H#TabChar#Q11I#TabChar#Q11J#TabChar#Q11K#TabChar#Q11L#Ta bChar#Q11M#TabChar#Q11O#TabChar#Q11P#TabChar#Q11Q#TabChar#Q11R#TabChar#Q12A1#TabChar#Q12A2 #TabChar#Q12B1#TabChar#Q12B2#TabChar#Q12C1#TabChar#Q12C2#TabChar#Q12D1#TabChar#Q12D2#TabCh ar#Q12E#TabChar#Q12F#TabChar#Q12G#TabChar#Q12H#TabChar#Q12I#TabChar#Q12J#TabChar#Q12K#TabC har#Q12L#TabChar#Q13A1#TabChar#Q13A2#TabChar#Q13B1#TabChar#Q13B2#TabChar#Q13C1#TabChar#Q13 C2#TabChar#Q13D1#TabChar#Q13D2#TabChar#Q13E1#TabChar#Q13E2#TabChar#Q13H1#TabChar#Q13H2#Tab Char#Q13I1#TabChar#Q13I2#TabChar#Q13J1#TabChar#Q13J2#TabChar#Q13K1#TabChar#Q13K2#TabChar#Q 13L#TabChar#Q13M#TabChar#Q13N#TabChar#Q14A1#TabChar#Q14A2#TabChar#Q14B1#TabChar#Q14B2#TabC har#Q14C1#TabChar#Q14C2#TabChar#Q14D#TabChar#Q14E#TabChar#Q14F#TabChar#Q14G#TabChar#Q14H#T abChar#Q15A#TabChar#Q15B#TabChar#Q15C#TabChar#Q15D#TabChar#Q15E#TabChar#Q15F#TabChar#Q15G# TabChar#Q15H#TabChar#Q16A#TabChar#Q16B#TabChar#Q16C#TabChar#Q16D#TabChar#Q16E#TabChar#Q16F #TabChar#Q17A1#TabChar#Q17A2#TabChar#Q17A3#TabChar#Q17B#TabChar#Q17C#TabChar#Q17D#TabChar# Q17E#TabChar#Q17F#TabChar#Q17G#TabChar#Q17H#TabChar#Q18A1#TabChar#Q18A2#TabChar#Q18B1#TabC har#Q18B2#TabChar#Q18C1#TabChar#Q18C2#TabChar#Q18D1#TabChar#Q18D2#TabChar#Q18E1#TabChar#Q1 8E2#TabChar#Q18H1#TabChar#Q18H2#TabChar#Q18I1#TabChar#Q18I2#TabChar#Q18J1#TabChar#Q18J2#Ta bChar#Q18K1#TabChar#Q18K2#TabChar#Q18L1#TabChar#Q18L2#TabChar#Q18M1#TabChar#Q18M2#TabChar# Q18N1#TabChar#Q18N2#TabChar#Q18O1#TabChar#Q18O2#TabChar#Q18P1#TabChar#Q18P2#TabChar#Q18Q1# TabChar#Q18Q2#TabChar#Q18R1#TabChar#Q18R2#TabChar#Q18S1#TabChar#Q18S2#TabChar#Q18T1#TabCha r#Q18T2#TabChar#Q18U1#TabChar#Q18U2#TabChar#Q18V1#TabChar#Q18V2#TabChar#Q18W1#TabChar#Q18W 2#TabChar#Q18X1#TabChar#Q18X2#TabChar#Q18Y1#TabChar#Q18Y2#TabChar#Q18Z1#TabChar#Q18Z2#TabC har#Q18A11#TabChar#Q18A12#TabChar#Q18B11#TabChar#Q18B12#TabChar#Q18C11#TabChar#Q18C12#TabC har#Q18D11#TabChar#Q18D12#TabChar#Q18E11#TabChar#Q18E12#TabChar#Q18H11#TabChar#Q18H12#TabC har#Q18I11#TabChar#Q18I12#TabChar#Q18J11#TabChar#Q18J12#TabChar#Q18K11#TabChar#Q18K12#TabC har#Q18L11#TabChar#Q18L1Z#TabChar#Q18M11#TabChar#Q18M12#TabChar#Q18N11#TabChar#Q18N12#TabC har#Q18O11#TabChar#Q18O12#TabChar#Q18P11#TabChar#Q18P12#TabChar#Q18Q11#TabChar#Q18Q12#TabC har#Q18R11#TabChar#Q18R12#TabChar#Q18S11#TabChar#Q18S12#TabChar#Q18T11#TabChar#Q18T12#TabC har#Q18U11#TabChar#Q18U12#TabChar#Q18V11#TabChar#Q18V12#TabChar#Q18W11#TabChar#Q18W12#TabC har#Q18X11#TabChar#Q18X12#TabChar#Q18Y11#TabChar#Q18Y12#TabChar#Q18Z11#TabChar#Q18Z12#TabC har#Q18A21#TabChar#Q19A#TabChar#Q19B#TabChar#Q19C>
    <cfset answers=#Q1#q2#....>
    Can anyone please help me out?

    Error :
    I am getting the error "Branch target offset too large for
    short" in coldfusion.
    What we are trying to do?
    We are concatenating large numbers of text. We where building
    a lengthly string. We ended up using mutliple variables and
    appending them together at the end to get it to work.
    Appending the lengthy string and writing into a file.
    Just to breif you this is a survey questions and answers we
    are generating text file with tab seperated as delimeters.
    e.g.
    The string I am using is
    <cfset Questions =
    Number#TabChar#Q1#TabChar#Q2A#TabChar#Q2B#TabChar#Q2C#TabChar#Q3A#TabChar#Q3B#TabChar#Q3C #TabChar#Q3D#TabChar#Q3E#TabChar#Q3F#TabChar#Q3G#TabChar#Q4A1#TabChar#Q4A2#TabChar#Q4A3#Ta bChar#Q4A4#TabChar#Q4A5#TabChar#Q4A6#TabChar#Q4B1#TabChar#Q4B2#TabChar#Q4B#TabChar#Q4B4#Ta bChar#Q4B5#TabChar#Q4B6#TabChar#Q4C1#TabChar#Q4C2#TabChar#Q4C3#TabChar#Q4C4#TabChar#Q4C5#T abChar#Q4C6#TabChar#Q4D1#TabChar#Q4D2#TabChar#Q4D3#TabChar#Q4D4#TabChar#Q4D5#TabChar#Q4D6# TabChar#Q4E1#TabChar#Q4E2#TabChar#Q4E3#TabChar#Q4E4#TabChar#Q4E5#TabChar#Q4E6#TabChar#Q4F1 #TabChar#Q4F2#TabChar#Q4F3#TabChar#Q4F4#TabChar#Q4F5#TabChar#Q4F6#TabChar#Q4G1#TabChar#Q4G 2#TabChar#Q4G3#TabChar#Q4G4#TabChar#Q4G5#TabChar#Q4G6#TabChar#Q4H1#TabChar#Q4H2#TabChar#Q4 H3#TabChar#Q4H4#TabChar#Q4H5#TabChar#Q4H6#TabChar#Q4I#TabChar#Q4J#TabChar#Q4K#TabChar#Q5A1 #TabChar#Q5A2#TabChar#Q5A3#TabChar#Q5A4#TabChar#Q5A5#TabChar#Q5A6#TabChar#Q5B1#TabChar#Q5B 2#TabChar#Q5B3#TabChar#Q5B4#TabChar#Q5B5#TabChar#Q5B6#TabChar#Q5C1#TabChar#Q5C2#TabChar#Q5 C3#TabChar#Q5C4#TabChar#Q5C5#TabChar#Q5C6#TabChar#Q5D1#TabChar#Q5D2#TabChar#Q5D3#TabChar#Q 5D4#TabChar#Q5D5#TabChar#Q5D6#TabChar#Q5E#TabChar#Q5F#TabChar#Q5G#TabChar#Q6A#TabChar#Q6B# TabChar#Q6C#TabChar#Q6E#TabChar#Q6F#TabChar#Q6G#TabChar#Q6H#TabChar#Q6I#TabChar#Q6J#TabCha r#Q6K#TabChar#Q7A1#TabChar#Q7A2#TabChar#Q7B1#TabChar#Q7B2#TabChar#Q7C#TabChar#Q7D#TabChar# Q8A#TabChar#Q8B#TabChar#Q8C#TabChar#Q8D#TabChar#Q8E#TabChar#Q8F#TabChar#Q8G#TabChar#Q8H#Ta bChar#Q9A1#TabChar#Q9A2#TabChar#Q9B1#TabChar#Q9B2#TabChar#Q9C1#TabChar#Q9C2#TabChar#Q9D1#T abChar#Q9D2#TabChar#Q9E1#TabChar#Q9E2#TabChar#Q9H1#TabChar#Q9H2#TabChar#Q9I1#TabChar#Q9I2# TabChar#Q9J1#TabChar#Q9J2#TabChar#Q9K1#TabChar#Q9K2#TabChar#Q9L1#TabChar#Q9L2#TabChar#Q9M# TabChar#Q9N#TabChar#Q9O#TabChar#Q9P#TabChar#Q9Q#TabChar#Q9R#TabChar#Q9S#TabChar#Q10A#TabCh ar#Q10B#TabChar#Q10C#TabChar#Q10E#TabChar#Q10F#TabChar#Q10G#TabChar#Q10H#TabChar#Q10I#TabC har#Q10J#TabChar#Q10K#TabChar#Q11A#TabChar#Q11B#TabChar#Q11C#TabChar#Q11D#TabChar#Q11E#Tab Char#Q11F#TabChar#Q11G#TabChar#Q11H#TabChar#Q11I#TabChar#Q11J#TabChar#Q11K#TabChar#Q11L#Ta bChar#Q11M#TabChar#Q11O#TabChar#Q11P#TabChar#Q11Q#TabChar#Q11R#TabChar#Q12A1#TabChar#Q12A2 #TabChar#Q12B1#TabChar#Q12B2#TabChar#Q12C1#TabChar#Q12C2#TabChar#Q12D1#TabChar#Q12D2#TabCh ar#Q12E#TabChar#Q12F#TabChar#Q12G#TabChar#Q12H#TabChar#Q12I#TabChar#Q12J#TabChar#Q12K#TabC har#Q12L#TabChar#Q13A1#TabChar#Q13A2#TabChar#Q13B1#TabChar#Q13B2#TabChar#Q13C1#TabChar#Q13 C2#TabChar#Q13D1#TabChar#Q13D2#TabChar#Q13E1#TabChar#Q13E2#TabChar#Q13H1#TabChar#Q13H2#Tab Char#Q13I1#TabChar#Q13I2#TabChar#Q13J1#TabChar#Q13J2#TabChar#Q13K1#TabChar#Q13K2#TabChar#Q 13L#TabChar#Q13M#TabChar#Q13N#TabChar#Q14A1#TabChar#Q14A2#TabChar#Q14B1#TabChar#Q14B2#TabC har#Q14C1#TabChar#Q14C2#TabChar#Q14D#TabChar#Q14E#TabChar#Q14F#TabChar#Q14G#TabChar#Q14H#T abChar#Q15A#TabChar#Q15B#TabChar#Q15C#TabChar#Q15D#TabChar#Q15E#TabChar#Q15F#TabChar#Q15G# TabChar#Q15H#TabChar#Q16A#TabChar#Q16B#TabChar#Q16C#TabChar#Q16D#TabChar#Q16E#TabChar#Q16F #TabChar#Q17A1#TabChar#Q17A2#TabChar#Q17A3#TabChar#Q17B#TabChar#Q17C#TabChar#Q17D#TabChar# Q17E#TabChar#Q17F#TabChar#Q17G#TabChar#Q17H#TabChar#Q18A1#TabChar#Q18A2#TabChar#Q18B1#TabC har#Q18B2#TabChar#Q18C1#TabChar#Q18C2#TabChar#Q18D1#TabChar#Q18D2#TabChar#Q18E1#TabChar#Q1 8E2#TabChar#Q18H1#TabChar#Q18H2#TabChar#Q18I1#TabChar#Q18I2#TabChar#Q18J1#TabChar#Q18J2#Ta bChar#Q18K1#TabChar#Q18K2#TabChar#Q18L1#TabChar#Q18L2#TabChar#Q18M1#TabChar#Q18M2#TabChar# Q18N1#TabChar#Q18N2#TabChar#Q18O1#TabChar#Q18O2#TabChar#Q18P1#TabChar#Q18P2#TabChar#Q18Q1# TabChar#Q18Q2#TabChar#Q18R1#TabChar#Q18R2#TabChar#Q18S1#TabChar#Q18S2#TabChar#Q18T1#TabCha r#Q18T2#TabChar#Q18U1#TabChar#Q18U2#TabChar#Q18V1#TabChar#Q18V2#TabChar#Q18W1#TabChar#Q18W 2#TabChar#Q18X1#TabChar#Q18X2#TabChar#Q18Y1#TabChar#Q18Y2#TabChar#Q18Z1#TabChar#Q18Z2#TabC har#Q18A11#TabChar#Q18A12#TabChar#Q18B11#TabChar#Q18B12#TabChar#Q18C11#TabChar#Q18C12#TabC har#Q18D11#TabChar#Q18D12#TabChar#Q18E11#TabChar#Q18E12#TabChar#Q18H11#TabChar#Q18H12#TabC har#Q18I11#TabChar#Q18I12#TabChar#Q18J11#TabChar#Q18J12#TabChar#Q18K11#TabChar#Q18K12#TabC har#Q18L11#TabChar#Q18L1Z#TabChar#Q18M11#TabChar#Q18M12#TabChar#Q18N11#TabChar#Q18N12#TabC har#Q18O11#TabChar#Q18O12#TabChar#Q18P11#TabChar#Q18P12#TabChar#Q18Q11#TabChar#Q18Q12#TabC har#Q18R11#TabChar#Q18R12#TabChar#Q18S11#TabChar#Q18S12#TabChar#Q18T11#TabChar#Q18T12#TabC har#Q18U11#TabChar#Q18U12#TabChar#Q18V11#TabChar#Q18V12#TabChar#Q18W11#TabChar#Q18W12#TabC har#Q18X11#TabChar#Q18X12#TabChar#Q18Y11#TabChar#Q18Y12#TabChar#Q18Z11#TabChar#Q18Z12#TabC har#Q18A21#TabChar#Q19A#TabChar#Q19B#TabChar#Q19C>
    <cfset answers=#Q1#q2#....>
    Can anyone please help me out?

  • Branch target offset too large for short - using CFThread

    I am just starting to get into using CFThread.  I have a process I am working on to allow clients to order background reports on multiple applicants simultaneously.  I am doing this using CFThread.  Through some trial and error I discovered that I needed to var scope the variables that are used in the CFC's that do the bulk of the report processing.  As soon as I did that I started getting the error "                                                                                                                                                      Branch target offset too large for short". Everything I have read on this error basically says I have too much code in the CFC which doesn't make sense as I am using this CFC in several other places in the site without error.  The problem only occured after var scoping my variables in the CFC and them sticking that CFC inside a CFTHread tag.
    Has only one seen anything like this before?
    Thanks

    Haven't seen it, no.
    Can you revert to your un-VARed code, and then re-VAR the variables one by one, retesting between each, and see if a specific one gives you the error?
    I don't know what this might tell you, but it might help focus where to look.
    NB: you should be VARing your variables within functions as a matter of course, not simply in situations in which the code is being called via <cfthread>.
    Adam

  • Nokia E6 Searching for position / Waiting for GPS ...

    I have a new nokia E6-00 with Symbian Anna (1 month old). I am very frustrated with the in-built GPS (Ovi Maps). It is working fine when it is connected to a Wi-Fi network, but when in OFFLINE mode it can not locate any satellites. It keeps displaying "searching for position" and "waiting for GPS". What should I do?
    Note: I have only checked Assisted GPS and Integrated GPS as positioning methods because I do NOT want any internet traffic caused by Ovi Maps.

    Hello there,
    I am writing because I am also having similar GPS difficulty with my E6-00.
    Here are the proper problem description and some background info:
    - for the past year, I had been using the C6-00. Its then Ovi Map was awesome, worked great in Asia, US, EU.
    - and before that, I also had the E71 for 2yrs. Again, Ovi Map served well.
    - Both phones only required their built-in GPS to navigate either walking or driving (with "offline" and "mobile data off")
    Now the problem with E6:
    - When "offline" or "mobile data" is off, the GPS simply wont function AT ALL. Like OP said, it gets disconnected soon afterwards. My question is, this is intended for E6? In comparison, the result in E6 seemed like a huge flaw.
    - Navigation / Positioning also seem "messed up". I am in Taiwan, Map version v0.2.43.11. I did a test: I launched both Nokia Map and Google Map on E6. Google map was accurate, showing exactly where I am, but Nokia Map was offset for 500 meters!! This made navigation IMPOSSIBLE!
    Map versions:
    - C6: 0.2.46.103
    - E6: 0.2.43.11 (cannot be further updated)
    Any advice is appreciated. Thank you.

  • Custom authentication scheme: Invalid Session Target

    Yesterday I spent a lot of time figuring out what was happening and I'm not sure if this is a bug or a feature...
    Create an application with some public pages (1,2,101) and some non-public pages (3,4).
    Created a list on page 0 listing all pages but only listing page 3 and 4 when user is logged in.
    Created a custom authentication scheme.
    Running the application showed me the page 1 and the list containing 1,2,101.
    I could navigate to 101 and then log in after which I was taken to page 1 showing only 1,2,101.
    I changed page 101 so that it would take me to page 3 after logging in and it did. The list showed me 1,2,101,3,4 and the username was also visible.
    I could visit all pages correctly except page 1. Whenever I navigated to page 1 I effectively got logged out.
    Finally I discovered that I had set "Invalid Session Target" to page 1 in my authentication scheme.
    Is this the intended effect ?

    Rene,
    When a page is selected in the authentication scheme's Invalid Session Page LOV, it gets designated as "the login page". Whenever this page is rendered, APP_USER is null and APP_SESSION is a new session ID. This accounts for what you saw. It's sort of a quirk more than a bug or feature and we ought to properly document this behavior. If, for some reason, you needed a login page that you could navigate back to (after login) in the current session and using the current APP_USER value, you can deselect the page from the Invalid Session Page LOV in the authentication scheme and instead code this in the Invalid Session URL:
    f?p=&APP_ID.:101:&APP_SESSION.
    ...using 101 as the login page, but it can be any page ID as long as it's a public page.
    Scott

  • Error:invalid xmd target : -1

    hi..
    Error:invalid xmd target : -1
    i am trying to download the executable.elf to xc3sd3400a fg 676 -4, using EDK10.1.. the message that i get on the xmd window is "invalid xmd target -1". use "targets" command to get current list of targets or change targets
    use "connect mb" command to connect to a microblaze target
    use "connect ppc" command to connect a PowerPc target.
    can anyone explain me what the problem is and how to solve it?? thank you..

    Open the xmd console and follow the commands below:
    1. fpga -f download.bit //configure the device with your bit file
    2. connect mb mdm //for microblaze processor
    or,
    connect ppc //for powerpc target
    3. dow application.elf //download your application elf
    4. run

  • Error while updating a custom Windows Azure Diagnostics configuration xml from powershell. "Invalid update to extension reference for role"

    I am attempting to upload a manually edited WADConfig xml to my VM. The WAD service is functioning correctly, I needed to add some custom WinEventLogs. The prescribed steps result in an error.
    What am I overlooking?
    I am following these instructions:
    Step 5: Remotely install Diagnostics on your Azure Virtual Machine
    azure.microsoft.com/en-in/documentation/articles/cloud-services-dotnet-diagnostics/#virtual-machine
    $storage_name = "wadexamplevm"
    $key = "<StorageAccountKey>"
    $config_path="c:\users\<user>\documents\visual studio 2013\Projects\WadExampleVM\WadExampleVM\WadExample.xml"
    $service_name="wadexamplevm"
    $vm_name="WadExample"
    $storageContext = New-AzureStorageContext
    -StorageAccountName $storage_name -StorageAccountKey $key
    $VM1 = Get-AzureVM
    -ServiceName $service_name -Name $vm_name
    $VM2 = Set-AzureVMDiagnosticsExtension
    -DiagnosticsConfigurationPath $config_path
    -Version "1.*"
    -VM $VM1 -StorageContext $storageContext
    $VM3 = Update-AzureVM
    -ServiceName $service_name -Name $vm_name
    -VM $VM2.VM
    Unfortunately, I am receiving this error:
    Update-AzureVM : BadRequest: Invalid update to extension reference for role: XXXXXX and reference: IaaSDiagnostics.
    What's missing from the above script?

    Hi,
    Since Azure SDK 2.5 uses the extension model the diagnostics extension, the configuration and the connection string to the diagnostic storage are no longer part of the deployment package and cscfg. All the diagnostics configuration is contained within the
    wadcfgx. The advantage with this approach is that diagnostics agent and settings are decoupled from the project and can be dynamically enabled and updated even after your application is deployed. 
    Due to this change some existing workflows need to be rethought – instead of configuring the diagnostics as part of the application that gets deployed to each environment you can first deploy the application to the environment and then apply the diagnostics
    configuration for it.  When you publish the application from Visual Studio this process is done automatically for you. However if you were deploying your application outside of VS using PowerShell then you have to install the extension separately through
    PowerShell.
    There PowerShell cmdlets for managing the diagnostics extensions on a Cloud Service are -
    Set-AzureServiceDiagnosticsExtension
    Get-AzureServiceDiagnosticsExtension
    Remove-AzureServiceDiagnosticsExtension
    You can use the Set-AzureServiceDiagnosticsExtension method to enable diagnostics extension on a cloud service. One of the parameters on this cmdlet is the XML configuration file. This file is slightly different from the diagnostics.wadcfgx file. You can
    create this file from scratch by either following the article that you are referring to or  you can modify the wadcfgx file and pass in the modified file as a parameter to the powershell cmdlet.
    To modify the wadcfgx file –
    Make a copy the .wadcfgx.
    Remove the following elements from the Copy:
    <DiagnosticsConfiguration xmlns="http://schemas.microsoft.com/ServiceHosting/2010/10/DiagnosticsConfiguration">
       <PrivateConfig xmlns="http://schemas.microsoft.com/ServiceHosting/2010/10/DiagnosticsConfiguration">
         <StorageAccount name=" " endpoint="https://core.windows.net/" />
       </PrivateConfig>
       <IsEnabled>false</IsEnabled>
    </DiagnosticsConfiguration>
    Make sure the top of the file still has xml version and encoding –
       <?xml version="1.0" encoding="utf-8"?>
    Effectively you are stripping down the Wadcfgx to only contain the <PublicConfig> section and the <?xml> header. You can then call the PowerShell cmdlet along with the appropriate parameters for the staging slots and roles:
    $storage_name = ‘
    <storagename>’
    $key= ‘<key>’
    $service_name = '<servicename>'
    $public_config = '<thepublicconfigfrom_diagnostics.wadcfgx>'
    $storageContext = New-AzureStorageContext –StorageAccountName $storage_name –StorageAccountKey $key
    Set-AzureServiceDiagnosticsExtension -StorageContext $storageContext -DiagnosticsConfigurationPath $public_config –ServiceName $service_name -Slot ‘Staging’ -Role ‘WebRole1’
    Hope this helps !
    Regards,
    Sowmya

  • Time evaluation error "Error while positioning ABWKONTI" for leave entitlem

    We are currently running on SAP ECC5. Time evaluation is run with schema TQTA everymonth to create leave quotas in info type 2006.
    I am experiencing a time evaluation error "Error while positioning ABWKONTI" for one employee when running TQTA.
    This employee was engaged on 14/08/2006. When I checked the logged changes per infotype, I found that a record for 14/07/2006 was deleted. I did check all the infotypes and all is reflecting the correct start date. I would really appreciate if someone can tell me how to fix this problem. Currently the leave entitlements are being processed manually. Please see below the error I am receiving:-
    Log: Time Evaluation
    4 General data
    Successful personnel numbers
    Personnel numbers with errors
    Personnel numbers ended early
    5 Personnel Numbers Rejected
    5 00408765 Van Wyk Werner
    U Error while positioning ABWKONTI
    13A200608 0002006081320060714###%##
    Quota could not be positioned:
    2006 08 2006.07.14 2006.08.13
    Relative day in period: 13 200706
    Quota used/quota entitlement to be accounted: 1.25000
    Person rejected: 00408765
    Messages
    5 Statistics
    Selected personnel numbers 1
    Successful runs for 0
    including with errors 0
    Processing not completed for 0
    Rejected 1
    Total number of messages and error messages 1

    Hi,
    Which Function Ur using for TQTR, Check That other wise P2006 Function Used.
    I think the error is in ur PCR.
    First u Understand the business process then write the PCR.
    Send ur pcr what u had written.
    also send ur Business senerio.like Conditions........

  • TPM_MIGRATION No position exists for the selected criteria Msg no. TRQ0020

    Hello Experts.
    I'm facing a error when execute the STEP B06 in TPM_MIGRATION Transaction, the message was:
    No position exists for the selected criteria
    Message no. TRQ0020
    Diagnosis
    This is the position that is characterized by the following details:
    CC=1020;PT=V4I;SA=DEPBCCR;SE=1000013
    When I look the Security ID number in the old system, the Document is obsolete, but the migration transaction seek the FLOW information for this ID number and not return any information.
    Thanks for you help.
    Regards.
    Edited by: k3n_rao on Mar 31, 2011 7:32 PM

    Hi Lorenz,
    Thank you very much for the answer, My colleague, the one who posted the threat is not longer available, he went on hollydays.
    We did check TPM12 & TPM13  and the reports said:
    TPM12 : "no positions selected"
    TPM13: "No flows found"
    Just to double check that we have understood, which "Migration date"  are you reffering to?
    thank you very much
    best regards,

  • Problem with variable offset for 0CALMONTH

    Hello Community,
    I have a problem with using variables offset for time characteristic 0CALMONTH
    Let's say my current query looks like this:
    ...................01.2006..........02.2006..........03.2006   (0CALMONTH)
    Sales ..............100..................125................200   (Keyfigure)
    What I want do now is to add a previous year comparison. So that it should look this way:
    ...................01.2006..........02.2006..........03.2006   (0CALMONTH)
    Sales ..............100..................125................200   (selected months)
    LY_Sales...........50..................100................100   (selected months - 12)
    (LY_Sales should show figures of 01.2005, 02.2005 and 03.2006 in this example)
    I used new selection for LY_Sales with variable offset for 0CALMONTH -12 but that didn't work. Figures in second line are zero. The desired figures would show up (if I expand the selected time intervall wide enough) in 01.2005, 02.2005 and 03.2005 but that's of course not what I want.
    Please help if you can!
    Regards,
    Ulrich

    Hi,
    We can get an an other way by using CELL editor caoncept.
    First create teh query like this:
    ...................01.2006..........02.2006........12.2006.....01.2005...02.20005...12.2005  Sales ..............100................125..............200.............50...........100.........100 
    Sales ..............100................125..............200.............50...........100.........100
    Then hide the 2005 years' kf:
    ...................01.2006..........02.2006........12.2006
      Sales ..............100................125..............200 
    Sales ..............100................125..............200
    Though the call editor concept overwrite the second rows(selection) content with hidden columns of second row(selection) one by one .i.e first cell of 2nd row will be overwritten by 13 th cell of second column.similarly second cell of 2nd row will be overwritten by 14 th cell of second column........
    First row(selection) : Cal year Charactertic with restriction 2006.
    second row(selection) : Cal year Charactertic with restriction 2005.
    With rgds,
    Anil Kumar Sharma .P

  • Hello. I began with the DPS. Is it possible to publish a magazine for a limited, specific target group? For example, in one department of a large company? Or to the responsible for various services? If so, how should I do? Thank you for your help.

    Hello.
    I began with the DPS. Is it possible to publish a magazine for a limited, specific target group? For example, in one department of a large company?
    Or to the responsible for various services? If so, how should I do? Thank you for your help.

    Short answer is yes.
    Click the request for consultation link in Digital Publishing Suite Help | DPS pricing options to receive a price estimate for the DPS license your project.

  • Error 404: No target servlet configured for uri: +websphere 6.0

    My server is running properly, but I got Error 404: No target servlet configured for uri: error while launching my project on web sphere 6.0
    see my web.xml and strut-config.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    id="WebApp_ID"
    version="2.4"
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
    <display-name>supportPortalWeb</display-name>
    <servlet>
    <servlet-name>action</servlet-name>
    <servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
    <init-param>
    <param-name>config</param-name>
    <param-value>/WEB-INF/struts-config/struts-config.xml</param-value>
    </init-param>
    <init-param>
    <param-name>debug</param-name>
    <param-value>2</param-value>
    </init-param>
    <init-param>
    <param-name>detail</param-name>
    <param-value>2</param-value>
    </init-param>
    <init-param>
    <param-name>validate</param-name>
    <param-value>true</param-value>
    </init-param>
    <load-on-startup>2</load-on-startup>
    </servlet>
    <servlet>
    <servlet-name>OrganizationDataServlet</servlet-name>
    <servlet-class>com.harcourt.supportportal.web.OrganizationDataServlet</servlet-class>
    </servlet>
    <servlet>
    <servlet-name>OrderProcessingServlet</servlet-name>
    <servlet-class>com.harcourt.supportportal.web.ordermgmt.OrderProcessingServlet</servlet-class>
    </servlet>
    <servlet>
    <servlet-name>OrganizationValidationServlet</servlet-name>
    <servlet-class>com.harcourt.supportportal.web.OrganizationValidationServlet</servlet-class>
    </servlet>
    <servlet>
    <servlet-name>ProductValidationServlet</servlet-name>
    <servlet-class>com.harcourt.supportportal.web.ProductValidationServlet</servlet-class>
    </servlet>
    <servlet>
    <servlet-name>ProductGradeServlet</servlet-name>
    <servlet-class>com.harcourt.supportportal.web.ProductGradeServlet</servlet-class>
    </servlet>
    <servlet>
    <servlet-name>action_tmp</servlet-name>
    <servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
    <init-param>
    <param-name>config</param-name>
    <param-value>/WEB-INF/struts-config/struts-config.xml</param-value>
    </init-param>
    <init-param>
    <param-name>debug</param-name>
    <param-value>3</param-value>
    </init-param>
    <init-param>
    <param-name>detail</param-name>
    <param-value>3</param-value>
    </init-param>
    <load-on-startup>0</load-on-startup>
    </servlet>
    <servlet-mapping>
    <servlet-name>action</servlet-name>
    <url-pattern>*.do</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>OrganizationDataServlet</servlet-name>
    <url-pattern>/servlet/OrganizationDataServlet</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>OrderProcessingServlet</servlet-name>
    <url-pattern>/servlet/OrderProcessingServlet</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>OrganizationValidationServlet</servlet-name>
    <url-pattern>/servlet/OrganizationValidationServlet</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>ProductValidationServlet</servlet-name>
    <url-pattern>/servlet/ProductValidationServlet</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>ProductGradeServlet</servlet-name>
    <url-pattern>/servlet/ProductGradeServlet</url-pattern>
    </servlet-mapping>
    <context-param>
    <param-name>contextConfigLocation</param-name>
    <param-value>/WEB-INF/spring-config/spring-config.xml</param-value>
    </context-param>
    <listener>
    <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
    </listener>
    <jsp-config>
    <taglib>
    <taglib-uri>/WEB-INF/struts-bean.tld</taglib-uri>
    <taglib-location>/WEB-INF/struts-bean.tld</taglib-location>
    </taglib>
    <taglib>
    <taglib-uri>/WEB-INF/struts-html.tld</taglib-uri>
    <taglib-location>/WEB-INF/struts-html.tld</taglib-location>
    </taglib>
    <taglib>
    <taglib-uri>/WEB-INF/struts-logic.tld</taglib-uri>
    <taglib-location>/WEB-INF/struts-logic.tld</taglib-location>
    </taglib>
    <taglib>
    <taglib-uri>/WEB-INF/struts-nested.tld</taglib-uri>
    <taglib-location>/WEB-INF/struts-nested.tld</taglib-location>
    </taglib>
    <taglib>
    <taglib-uri>/WEB-INF/struts-template.tld</taglib-uri>
    <taglib-location>/WEB-INF/struts-template.tld</taglib-location>
    </taglib>
    <taglib>
    <taglib-uri>/WEB-INF/struts-tiles.tld</taglib-uri>
    <taglib-location>/WEB-INF/struts-tiles.tld</taglib-location>
    </taglib>
    <taglib>
    <taglib-uri>/WEB-INF/epc.tld</taglib-uri>
    <taglib-location>/WEB-INF/supportportal.tld</taglib-location>
    </taglib>
    </jsp-config>
    <resource-ref>
    <res-ref-name>jdbc/SupportPortalDataSource</res-ref-name>
    <res-type>java.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </web-app>
    <!DOCTYPE struts-config PUBLIC "-//Apache Software Foundation//DTD Struts Configuration 1.1//EN" "http://jakarta.apache.org/struts/dtds/struts-config_1_1.dtd">
    <struts-config>
         <!-- Data Sources -->
         <data-sources />
         <!-- Form Beans -->
         <form-beans>
              <form-bean name="signOnHandlerForm" type="com.harcourt.supportportal.struts.signon.actionform.SignOnHandlerForm" />
              <form-bean name="signOffHandlerForm" type="com.harcourt.supportportal.struts.signon.actionform.SignOffHandlerForm" />
              <form-bean name="updatePersonForm" type="com.harcourt.supportportal.struts.sample.actionform.UpdatePersonForm" />
              <form-bean name="searchPersonsForm" type="com.harcourt.supportportal.struts.sample.actionform.SearchPersonsForm" />
              <form-bean name="updateProductForm" type="com.harcourt.supportportal.struts.product.actionform.UpdateProductForm"/>
              <form-bean name="searchProductsForm" type="com.harcourt.supportportal.struts.product.actionform.SearchProductsForm"/>
              <form-bean name="searchOrganizationForm" type="com.harcourt.supportportal.struts.mdr.actionform.SearchOrganizationForm"/>
              <form-bean name="updateOrganizationForm" type="com.harcourt.supportportal.struts.mdr.actionform.UpdateOrganizationForm"/>
              <form-bean name="exportOrganizationForm" type="com.harcourt.supportportal.struts.mdr.actionform.ExportOrganizationForm"/>
              <form-bean name="exportProductForm" type="com.harcourt.supportportal.struts.product.actionform.ExportProductForm"/>           
         </form-beans>
         <!-- Global Exceptions -->
         <global-exceptions />
         <!-- Global Forwards -->
         <!-- Action Mappings -->
         <action-mappings type="org.apache.struts.config.SecureActionConfig">
              <action
                   path="/start"
                   type="org.apache.struts.actions.ForwardAction"
                   parameter="loginRendererDef"/>
    <!--          <action -->
    <!--               path="/product"-->
    <!--               type="org.apache.struts.actions.ForwardAction"-->
    <!--               parameter="productInputDef"/>-->
              <action path="/product" type="org.springframework.web.struts.DelegatingActionProxy"
                        name="updateProductForm" parameter="method" scope="request" validate="false">
                   <forward name="success" path="productInputDef"/>
                   <forward name="failure" path="productInputDef"/>
              </action>
    <!--          <action -->
    <!--               path="/organization"-->
    <!--               type="org.apache.struts.actions.ForwardAction"-->
    <!--               parameter="organizationIndexDef"/>-->
              <action
                   path="/report"
                   type="org.apache.struts.actions.ForwardAction"
                   parameter="reportIndexDef"/>
              <action
                   path="/user"
                   type="org.apache.struts.actions.ForwardAction"
                   parameter="userIndexDef"/>
              <action path="/login" type="org.springframework.web.struts.DelegatingActionProxy" name="signOnHandlerForm" scope="request" input="loginRendererDef" validate="true">
         <set-property property="secure" value="false"/>
              <forward name="success" path="loginLandingDef" />
              <forward name="failure" path="loginRendererDef" />
    </action>
    <!-- sample -->
         <action path="/updatePerson" type="org.springframework.web.struts.DelegatingActionProxy" name="updatePersonForm" scope="request" input="productInputDef" validate="true">
         <set-property property="secure" value="false"/>
              <forward name="success" path="personIndexDef" />
              <forward name="failure" path="personInputDef" />
    </action>
         <action path="/searchPersons"
                   type="org.springframework.web.struts.DelegatingActionProxy"
                   name="searchPersonsForm"
                   scope="request"
                   parameter="method"
                   validate="true">
         <set-property property="secure" value="false"/>
              <forward name="success" path="personIndexDef" />          
              <forward name="failure" path="loginRendererDef" />
    </action>
         <!-- end sample -->
         <action path="/updateProduct" type="org.springframework.web.struts.DelegatingActionProxy"
                   name="updateProductForm" parameter="method" scope="request" input="productInputDef" validate="true">
         <set-property property="secure" value="false"/>
              <forward name="success" path="loginLandingDef" />          
              <forward name="failure" path="/product.do?method=createOrUpdateProduct" />
    </action>
    <action path="/deleteProduct" type="org.springframework.web.struts.DelegatingActionProxy"
                   name="updateProductForm" parameter="method" scope="request" validate="false">
         <set-property property="secure" value="false"/>
              <forward name="success" path="loginLandingDef" />          
              <forward name="failure" path="/product.do?method=createOrUpdateProduct" />
    </action>
    <action path="/searchProducts"
                   type="org.springframework.web.struts.DelegatingActionProxy"
                   name="searchProductsForm"
                   scope="request"
                   parameter="method"
                   validate="true">
         <set-property property="secure" value="false"/>
              <forward name="success" path="productSearchDef" />
              <forward name="failure" path="loginLandingDef"/>
    </action>
    <action path="/loadProducts" type="org.springframework.web.struts.DelegatingActionProxy"
              name="searchProductsForm" parameter="method" scope="request" validate="true">
         <forward name="success" path="productIndexDef"/>
         <forward name="failure" path="userIndexDef"/>
    </action>
    <action path="/exportProduct" type="org.springframework.web.struts.DelegatingActionProxy"
              name="exportProductForm" parameter="method" scope="request" validate="true">
              <forward name="failure" path="loginLandingDef" />
    </action>
    <!-- Organization Actions -->
    <action path="/searchOrganization" type="org.springframework.web.struts.DelegatingActionProxy"
              name="searchOrganizationForm" parameter="method" scope="request" validate="true">
         <forward name="success" path="orgSearchDef"></forward>
         <forward name="failure" path="loginLandingDef"/>
         </action>
    <action path="/organization" type="org.springframework.web.struts.DelegatingActionProxy"
              name="updateOrganizationForm" parameter="method" scope="request" validate="false">
         <set-property property="secure" value="false"/>
              <forward name="success" path="orgInputDef" />          
              <forward name="failure" path="loginLandingDef" />
    </action>
    <action path="/loadOrganizations" type="org.springframework.web.struts.DelegatingActionProxy"
              name="searchOrganizationForm" parameter="method" scope="request" validate="true">
         <forward name="success" path="orgIndexDef" />          
              <forward name="failure" path="loginLandingDef" />
    </action>
    <action path="/updateOrganization" type="org.springframework.web.struts.DelegatingActionProxy"
              name="updateOrganizationForm" parameter="method" scope="request" input="orgInputDef" validate="true">
                   <forward name="success" path="/loadOrganizations.do?method=loadOrganizations"></forward>
                   <forward name="failure" path="/organization.do?method=createOrUpdateOrganization"/>               
              </action>
              <action path="/exportOrganization" type="org.springframework.web.struts.DelegatingActionProxy"
              name="exportOrganizationForm" parameter="method" scope="request" >
              <forward name="failure" path="loginLandingDef" />
    </action>
         </action-mappings>
         <!-- Register Support Portal RequestProcessor -->
         <controller>
              <set-property property="processorClass" value="com.harcourt.supportportal.struts.common.action.SupportPortalRequestProcessor" />
         </controller>
         <!-- Message Resources -->
         <message-resources parameter="com.harcourt.supportportal.resources.ApplicationResources" />
         <!-- tiles plugin -->
    <plug-in className="com.harcourt.supportportal.tiles.SupportPortalSecureTilesPlugin">
         <set-property property="definitions-config" value="/WEB-INF/tiles-def/tiles-defs.xml" />
         <set-property property="httpPort" value="80"/>
    <set-property property="httpsPort" value="80"/>      
    <set-property property="enable" value="false"/>      
    <set-property property="addSession" value="false"/>      
    </plug-in>
         <!-- spring plugin -->
         <plug-in className="org.springframework.web.struts.ContextLoaderPlugIn">
         <set-property property="contextConfigLocation" value="/WEB-INF/spring-config/spring-config.xml"/>
         </plug-in>
    </struts-config>

    If your EAR has actually started, try this:
    http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/xrun_jvm_sendredirect.html
    If you are not on z/OS, the link is actually under server->server infrastructure->Java and process management->environment entries
    for setting the property

  • Source port type for BPELProcess does not match target port type for EJB

    Hi gurus,
    I have a problem with calling EJBs from a 11.1.1.3 composite. The following summarizes the issue:
    - there are several EJBs within the same package deployed on a WLS server.
    - these beans have method names that are the same, for example create(), delete() etc.
    - using the EJB Service Adapter I have created 3 References, one for each of the 3 beans I need to invoke in a BPEL process.
    - each bean is imported into the project with their own *.wsdl *Ref.wsdl files.
    - each wsdl imports a namespace based on the java package name
    - now i have 3 wsdls, importing the same namespace and namespace conflicts arise.
    At this point I'm thinking, 'no problem, just change the namespaces manually'
    - whenever i try to change the namespace that JDev gives the Reference components I end up with the compilation error:
    Source port type for "BPELProcess" does not match target port type for "EJBRef"
    It seems that the namespace must be the same as the package name, even though I resolved all the references to the new namespaces and ensure they all match.
    The problem appears to be in the BPELProcess.componentType file.
    <reference name="HelloEJBRef" ui:wsdlLocation="HelloEJBRef.wsdl">
    <interface.wsdl interface="http://package.workspace.com/HelloEJB#wsdl.interface(HelloEJB)"/>
    </reference>
    If the namespace (text before the #) is changed at all from the default, even if it matches the wsdl, results in the port type mismatch error above.
    Any ideas?
    btw, running SOA 11.1.1.3, JDev 10.1.1.3, EJB 3.0

    Hi gurus,
    I have a problem with calling EJBs from a 11.1.1.3 composite. The following summarizes the issue:
    - there are several EJBs within the same package deployed on a WLS server.
    - these beans have method names that are the same, for example create(), delete() etc.
    - using the EJB Service Adapter I have created 3 References, one for each of the 3 beans I need to invoke in a BPEL process.
    - each bean is imported into the project with their own *.wsdl *Ref.wsdl files.
    - each wsdl imports a namespace based on the java package name
    - now i have 3 wsdls, importing the same namespace and namespace conflicts arise.
    At this point I'm thinking, 'no problem, just change the namespaces manually'
    - whenever i try to change the namespace that JDev gives the Reference components I end up with the compilation error:
    Source port type for "BPELProcess" does not match target port type for "EJBRef"
    It seems that the namespace must be the same as the package name, even though I resolved all the references to the new namespaces and ensure they all match.
    The problem appears to be in the BPELProcess.componentType file.
    <reference name="HelloEJBRef" ui:wsdlLocation="HelloEJBRef.wsdl">
    <interface.wsdl interface="http://package.workspace.com/HelloEJB#wsdl.interface(HelloEJB)"/>
    </reference>
    If the namespace (text before the #) is changed at all from the default, even if it matches the wsdl, results in the port type mismatch error above.
    Any ideas?
    btw, running SOA 11.1.1.3, JDev 10.1.1.3, EJB 3.0

  • How to create offset for calendar year/month in BEx Reporting

    HI ALL,
        i have a requirement of creating offset for calendar year/month.Basically i have a characteristic in Rows and volume key figure in Column and i have to put that volume under the calender year /month which is shown below ..
                             Previous Volume           Present Volume
                                     01.2010                             01.2011
    material                    10000                               20000
    how can i create a report for this . by using volume key figure i am creating previous volume and present volume,. how can i put them in key figure do i have to create any structure, selections  for that.... and "" how can i get the present year volume and previous year volume. If i use cal year/month how can i create offset for that.....
    please do let me know in brief...
    Thank you.

    Hi ,
    I think you need data year wise .
    Instead of creating a variable for calmonth and using it in the RKF , you can just drag calyear in columns and keep the Volume keyfigure below it . Keep only one keyfigure Volume and do not restrict it with calmonth or any other variable .
    In this case calyear should not be present in rows or free characteristics .
    You would be able to see the data year wise ..
    Try this and check whether it is according to your requirement
    If You need to show the data as Volume (01.2011)  and Volume(01.2010)
    It means you are only showing data for Jan 2011 and Jan 2010 in the report
    In this case you can retrict Volume keyfigure with a variable and create a customer exit variable
    for 0calmonth as an offset of -1 will bring the data of 12.2010 for Previous Volume(01.2010) key figure which is incorrect .
    For your output you can create 2 customer exit variables :
    One will restrict 0calmonth to current year and another to previous year .
    Check whether this works .
    Also , if you want to show current calendar months data , you can either use a mandatory variable on 0calmonth
    and restrict the same in volume keyfigure or there are std customer exit variable provided by SAP to give current cal month .
    You can restrict the char 0calmonth with this std exit variable if you do not want 0calmonth variable to be mandatory.

  • Variable Offset for Customer Exit??

    Hi,
    is it possible to have a variable offset for customer exit time variables?
    E.g. I have a variable current month but can I also create a one-year offset of that?
    In our system that doesn't work (but also the current month variable doesn't work...)
    thanks
    Sabine

    Hi,
    As it is mentioned by Mr.Voodi,it definately works.
    You only has given the answer for your problem .i.e you need to make sure the Customer exit variable is working proper.So take a look on the code used for it.
    With rgds,
    Anil Kumar Sharma .P

Maybe you are looking for