Upgrade issue of transaction FVZA in ECC 6.0
Hi ,
When I execute the transaction FVZA, it is displaying the error "This program is old and is not part of the standard system."
Any suggestion on this.
Regards,
Sree
Hi,
Best way to sort these kind of issue is to write to SAP.
Write an OSS message to SAP along with the screen shots.
Hope this helps!
Regards,
Lalit Kabra
Similar Messages
-
Issues during technical upgrade from version 4.6C to ECC 6.0
Dear All,
We have done a technical upgrade from version 4.6C to ECC 6.0 and encountered following issues -
In the t-code ABZE (acquisition with in house production) there is a check-box for reversal posting on screen with version 4.6C. However, this field is missing in ECC 6.0. Why so?
In the report s_alr_87012327, there is a field "only with creation block" in version 4.6C. However, this field is missing in ECC 6.0. Why so?
Request to kindly suggest the alternative to carry out the same in ECC 6.0.
Thanks in advance.
Regards,
DhawalHi Akshya,
Please find answers below.
1) 4.6c is NON-UNICODE system, Can I upgrade it into ECC 6.0 UNICODE system?
Yes you can.
If you are on a single code page system then you can give a gap between your uprade and unicode conversion. There is no problem with the singlecode upgrade and conversion.
But if your system is MDMP then you will have to do the CUUC method that is both upgrade and unicode conversion together. Though you can give a gap and sign an disclaimer with SAP it is still not recomended way.
2) 4.6c does not have any ITS system installed. If we upgrade it to ECC6.0 ABAP only, then Can I activate WAS internal ITS?
Yes you can activate it.
3) 4.6c does not have any JAVA stack. When I upgrade it to ECC 6.0, can I upgrade it to dual stack (ABAP+JAVA)? If yes, then how?
After the upgrade and unicode conversion you can install the java stack.
Regards,
Ravi. -
ECC 6.0 EHP-4 upgrade Issue in phase MAIN SHDRUN/ALTNTAB FILL were negative
Hi Basis Expert,
while doing ECC 6.0 EHP-4 Upgrade in MAIN_SHDRUN/ALTNTAB_FILL phase we are getting the following issue please help us.
Checks after phase MAIN_SHDRUN/ALTNTAB_FILL were negative!
Last error code set: BATCH JOB RDDNT2MT FAILED: Error(s) found in the log(s), accumulated in "ALTNTFI.ELG".
We check the shadow instance is up and we can log in to the system. Check ST22 and SM21 notice no error.
Check the JOB RDDNT2MT (SM37) successfully running and all the job finish without any error.
Hope anybody can share a bit your experience on this issue. we try search the note and find the forum but no luck.
ThanksHi,
> 2EETG011 "No shadow system""(environment parameter)""auth_shadow_upgrade"
> 2EETG011 "No shadow system""DB-connect not against shadow tables !"
>
It looks from your log that shadow system is not able to connect to database. Please check your shadow system. Check below link as well:
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/ecc-6-upgrade-issue-in-phase-altntab_fill-1556272
Thanks
Sunny
Edited by: Sunny Pahuja on Oct 15, 2010 1:27 PM -
BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0
Background:
I am relatively new to BW team and will be going through my 1st source system upgrade.
We currently have BI 7.0 SPS 17 connected to source system R/3 Enterprise EP1.
We are upgrading to the source system to ECC 6.0.
In Development and QA Environments:
we will have access to both old (R/3 Enterpirse) and the new (ECC 6.0) source systems.
We have a opportunity to compare the BW Objects, data flow and data loading from
both source systems.
In Production, however, we will just upgrade over 3 days downtime.
One Question that comes to mind in this regard...
What sort of things, we should be checking for before and after upgrade in Dev/QA and in Prod environments and what tools are available that can help the analysis and validation process ?
Some of the suggestions that were given to me include following points.
Before Upgrade:
1 Check data, taking pre images of it for testing with post upgrade.
2. Perform proper analysis of Source system related BW objects.
- A complete listing of actively used Datasources,.. etc.
3. Make delta queues empty,
Make sure that all existing deltas are loaded into BW.The last request delta must not deliver any data and must be green in the monitor.
4. Stop Process chains from BI (remove from schedule) and collection runs from R/3 side
After Upgrade:
1 After the OLTP upgrade, refer to note 458305 and other notes that are relevant to the actual upgrade
(depending on the R/3 system release / R/3 plug-in to BI plug-in compatibility).
2. Check logical system connections. Transactions SMQS, RSMO and SM59, If no access, then we can use Program RSRFCPIN_NEW for RFC Test.
3. Check and/or Activate control parameters for data transfer. SBIW ---> General Settings --->
Maintain Control Parameters for Data Transfer
http://help.sap.com/saphelp_nw70/helpdata/EN/51/85d6cf842825469a51b9a666442339/frameset.htm
4. Check for Changes to extract structures in LBWE Customizing Cockpit
- OSS Notes 328181, 396647, 380078 and 762951
5. Check if all the required transfer structures are active. See OSS Note 324520 for mass activation.
7. Check if all Source system related BW Objects are active - Transfer rules, Communication rules, update rules,DTPs,..etc.
Below is a link for some useful programs in this regard.
https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action&pageid=35458
6. Test all important datasources using RSA3 and check for OLTP Datasources changes .
As soon as BW notices that the time stamp at the DataSource in the OLTP is newer than the one in the transfer structure, it requests replication of the DataSource and activation of the transfer structure. Transfer the relevant DataSources only if required, and transfer only the ones that have changed (RSA5 -> Delta).
7. Create Data flow objects (trnasfer rules, infopackages, trnasformations, DTPs) for the Replicate
new/changed datasources,if needed.
8. Check all CMOD enhancements.
If we are using a customer exit with the extractor in the OLTP, see Note 393492.
7. Check for unicode (all custom programs or Function Modules for DataSources)
5. Check all the queues in RSA7, start delta runs and test data consistency.
For delta problems:In the BW system, start the 'RSSM_OLTP_INIT_DELTA_UPDATE' program for the DataSource and the source (OLTP) system for which the init selections are then transferred from BW into the ROOSPRMSC and ROOSPRMSF tables in the source system so that the delta can continue.
9. Take back up of data posted during upgrade for contingency planing.
10. Run the entire set of process chains once if possible and let it pick up no data or the usual master data.
Since we have lot of experts in this forum, who have probably gone through such scenario many times, i wanted to request you to Please Please advise if i have stated anything incorrectly or if i am missing additional steps, OSS Notes, important details...Thanks Rav for your detailed post and very helpful contribution by posting all the information you had regarding the upgrade.
We have similar scenario -
We are upgrading our source system from 4.7 to ECC 6.0. We have our BI system with BI 7.0 at support pack 19 (SAPKW70019).
Our strategy in ECC deployment ->
In development we copied our old DEV 4.7 system DXX to new ECC system DXY (new system ID).
In production we are going to use same system PRXX upgraded from 4.7 to ECC.
Now we are in testing phase of ECC with all interfaces like BI in Dev.
My questions are below ->
How can we change/transfer mapping of all our datasources in Dev BW system BID to new ECC dev system DXY (Eg. Logical system LOGDXY0040) from Old dev system DXX (Eg. Logical system LOGDXX0040). We donot want to create new datasources or change all transfer rules/Infosources for old BW3.x solutions on our BI.
Also in new ECC sourcesystem copy we see all datasources in Red in RSA7 transaction. Do we need to initialize again all the datasources from our BW BID system.
Is there any easy way for above scenario ?
Please let me know if you have any further helpful information during your ECC 6.0 upgrade connecting to BI 7.0 system.
I have found some other links which have some pieces of information regarding the topic -
Upgrade R/3 4.6C to ECC 6.0 already in BI 7.0
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/sap-r3-migration-and-sap-bw-version-1744205
BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0
Re: ECC 6.0 Upgrade
Re: Impact of ECC 6.0 upgrade on BI/BW Environment.
ECC 5.0 to ECC 6.0 upgrade
Thanks
Prasanth -
We are facing an issue in our COE SAP ECC 6.0 instance
Hi,
We are facing an issue in our COE SAP ECC 6.0 instance. The sequence of steps performed is as given below
1. Start Vendor Creation using Create Vendor: Initial Screen
2. Create Vendor : Address
3. Create Vendor : Control
4. Create Vendor: Payment Transactions
5. Create Vendor: Accounting Information Accounting
6. Create Vendor: Payment Transactions Accounting
7. Create Vendor: Correspondence Accounting
After the above steps are performed the system displays a message Vendor <V No.> was created in company code 1000
If we try to use the above created Vendor in F-90 or FK02 ( Change Vendor details TCode) it throws an error as "Vendor has not been created".
The table LFB1 doesnt have the Vendor associated with the Company Id 1000.
Query: But does anyone WHY the Table is not being updated and WHAT needs to be done to make sure Updation happens in future.
A quick response on this will be greatly appreciated!HI,
Please chk in the config....
SPRO>MM->Partner Deter->Partner setting in Rebate Arrangement->Define partner schemas for Rebate..
Here please check the partner function "PI" is made mandatory...
You can main the Partner function "PI" in the agreement itself...
Goto-- txn.MEB2-- enter the agreement no... inside click the icon "Agreement Partner" or (Ctrl+F2) and maintain the partner function PI..
Regards
GK. -
Hi Experts,
When we run the Asset Acquisitions Report through transaction S_ALR_87012050 we are able to see the output list, but when we use the transaction ART0 (i.e. Transaction ART0-> Day-to-day activities -> Acquisitions -> Asset Acquisitions -> SAP Standard Variant), we get the message 'No records were selected'.
This is happening only after the system Upgrade, before the upgrade both the transaction S_ALR_87012050 and ART0 were giving same results.
I have given below the programs associated with these transactions and their version details:
S_ALR_87012050 - RAZUGA_ALV01 (latest version date is in July 2010 and it is working fine)
ART0 - RAZUGA01 (only one version available and that too is in the year 2002 and it not giving output)
I doubt the program RAZUGA01is not upgraded, I am not able to find a suitable SAP Note for updating the program RAZUGA01,
kindly help me in fixing this issue.
Thanks,
RyanHi,
u cant provide directly a 300 char in the message info box. (its no way possible)
Instaed u can provide any no. of characters for the INFO pop up button.
In that message pop up box, u have to provide the message as "PRESS ?/F1 for DETAIL INFORMATION".
In the message class say for MESSAGE 000 -- "PRESS ?/F1 for DETAIL INFORMATION".
now select the MESSAGE 000 and Select LONG TEXT push button, the u can find the editor where u can eneter any number of charcters.
EX:
Parameters: p_nav type matnr.
if p_nav is initial.
message i000.
endif.
Now u will see a popup message "PRESS ?/F1 for DETAIL INFORMATION".
when user selects F1/? then ur info message graeter than 300 char will be executed.
Revert back if any issues,
Reward with points if helpful.
Regards,
Naveen. -
Upgrade issues OBIEE 10g to 11g along with OBIA upgrade
Hi,
I have to upgrade OBIEE 10.1.3.4.1 to OBIEE 11.1.1.5 along with OBIA 7.9.6.1 to 7.9.6.5(Informatica 8.6.1 to 9.0.1) at my client location and I have very little knowledge on it. and want to know/have help documents for upgrade.
And if anyone in the forums involved in upgrade please list the errors/issues occured during upgrade and after upgrade.
1. OBIEE 10g to 11g upgrade issues??
2. OBIA OBIA 7.9.6.1 to 7.9.6.5 upgrade issues along with 10g to 11g??
3. Informatica 8.6.1 to 9.0.1 upgrade issues??
4. DAC upgrade issues??
any response for my questions is appreciated.
Thanks
Jay.
Edited by: Jay on Apr 11, 2012 9:11 AMHI Jay,
We cannot explained thread list here, If you get any errors plz post me,will try to help out.
This is oracle document link - This document has given step by step with screen shots upgration for 10g to 11g ,Please refer the below link.
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm
http://obieemanu.blogspot.in/2011/05/rpd-upgration-from-10g-to-11g.html
http://docs.oracle.com/cd/E21764_01/upgrade.1111/e10125/ua_command_line.htm#ASMAS149
Award points it is useful.
Thanks,
satya -
Report generation toolkit upgrade issues
I have created multiple vi's in that utilize the previous report generation toolkits specifically using the Generate Report Get Data to Modify.vi and the Generate Report Set Modified Data.vi. Obviously the report reference has now changed in 8.6's version of the report generation toolkit and these vi's do not exist in the 8.6 library anymore. What vi's do I need to replace these functions with to make this code work. Can anyone tell me what the work around is to solving this problem. This is a picture of the code.
BJD1613
Lead Test Tools Development Engineer
Philips Respironics
Certified LV Architect / Instructor
Attachments:
code.JPG 92 KBHi BJD1613,
The Report Generation VIs on the LabVIEW Palettes mutate properly. However, you may run into upgrade issues if VIs distributed with LabVIEW, but not available in the Palettes are used in the code. Hence, I would caution against using them for the same reason.
In this case, the specific references do exist in the report generation classes; however, since they are private, they cannot be accessed by VIs outside the respective classes. A temporary workaround for now is mentioned in the following KB 4OOCSJ4M Getting References in Report Generation Toolkit 1.1.3 with LabVIEW 8.6.
This was reported to R&D (CAR# 123064) for further investigation -
Hello experts,
Currenctly my customer has the following systems:
BW 3.5 with software component SEM 4.0
R/3 4.6C without software component SEM
ECC 6.0 with software component SEM 6.0 (Development system, I cannot connect the BW system to this one!)
Next week my customer is going to upgrade R/3 4.6C to ECC 6.0 (Test system).
I have to investigate if this upgrade does not influence the communication between SEM 4.0 and BW 3.5, if I connect BW 3.5 to ECC 6.0.
According to the blog: /people/karen.comer/blog/2006/12/19/confused-about-business-planning-releases-between-sap-sem-and-sap-netweaver-bi
SAP SEM is an add-On on top of SAP BW / SAP NetWeaver BI.
This blog also states that:
SEM 4.0 should work with BW 3.5
SEM 6.0 should work with Netweaver 2004s (BW 7.0)
Now I have the situation that software component SEM 4.0 is installed in BW 3.5, and SEM 6.0 is integrated in ECC 6.0 because it is part of Netweaver 2004s.
Does anyone know if the upgrade to ECC 6.0 has influence to the connection between BW 3.5 and SEM 4.0??
Tnx for your help!
G.>
Markus Taxacher wrote:
>Is the only possible way to migrate the BW 3.5 to ERP/ECC 6.0?
> Whats the easiest way for upgrading to 6.0?
>
> Best regards,
> Markus
Hi, you cannot use BW3.5 you must have BI7 (not ECC6!) to install BCS 6 - BCS sits on BI (formerly known as BW).
It doesn't matter what version of source system you have, you can still collect data from ERP 4.6, you don't necessarily need ECC6. -
EHP Upgrade Issue - Java Stack
Hi,
Our Source System at NW 7.0 SP13 and we are upgrading the system to EHP1 SP03.
Upgrade failed at Downtime > DEPLOY_ONLINE_DEPL phase.
Error log:
Sep 9, 2009 10:11:51 PM [Error]: com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.
Sep 9, 2009 10:11:51 PM [Error]: com.sap.sdt.jspm.unattended.RequestController.addContextInfo(RequestController.java:178) [Thread[main,5,main]]: Deployment of queue sapjup-queue completed with error
JSPM version is 7.01.3.0.15. Current JSPM log directory is /usr/sap/XPD/JC00/j2ee/JSPM/log/log_2009_09_09_16_09_42.
Sep 9, 2009 10:11:51 PM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:698) [Thread[main,5,main]]: The deployment of the queue failed.
Sep 9, 2009 10:11:51 PM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.deploy.SAPJupJSPMDeployer.deployList(SAPJupJSPMDeployer.java:68) [Thread[main,5,main]]: Could not execute deployment of stack file /usr/sap/trans/EPS/in/XPD.xml.
Sep 9, 2009 10:11:51 PM [Error]: com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.execute(PhaseTypeDeploymentManager.java:519) [Thread[main,5,main]]: Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action.
Sep 9, 2009 10:11:51 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase UPGRADE/DEPLOYMENT_BASED_UPGRADE/DEPLOY_ONLINE_DEPL has been completed.
Sep 9, 2009 10:11:51 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2009/09/09 22:09:42.
Sep 9, 2009 10:11:51 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2009/09/09 22:11:51.
Sep 9, 2009 10:11:51 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:02:08.248.
Sep 9, 2009 10:11:51 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error.
I went through the following link , proceeded with option 2, But still getting same error.
Portal Upgrade Issue
Please advise the resolution for the issue I have.
Thanks in advance
Regards
Srinivas
Edited by: Srinivas Dasari on Sep 10, 2009 5:48 AM
Edited by: Srinivas Dasari on Sep 10, 2009 5:48 AMIssue resolved
-
Hi,
We're currently on 4.6b and going to upgrade to ECC6 with unicode I'm trying to compile a list point taken care converting to unicode from ABAP technical point of view. Does anyone have such a list?
Some points i shortlisted are :
1) Use GUI_UPLOAD and GUI_DOWNLOAD rather than WS_UPLOAD and WS_DOWNLOAD.
2) Structures or table headers that contain non-character data need to be identical when moving, comparing, selecting into, updating from, etc.
3) OPEN DATASET filename IN TEXT MODE FOR INPUT ENCODING DEFAULT.
I know there are others. Any help would be appreciated.
aRsCheck the below links
http://www.sapfans.com/forums/viewtopic.php?t=268386&highlight=upgrade+issues
http://www.sapfans.com/forums/viewtopic.php?t=263434&highlight=upgrade+issues
http://www.sapfans.com/forums/viewtopic.php?t=261051&highlight=upgrade+issues
http://www.sapfans.com/forums/viewtopic.php?t=253316&highlight=upgrade+issues -
Issue in Vendor Rebate Settlement (ECC 6.0)
Hello All,
We recently upgraded from SAP 4.7 to ECC 6.0. In the new system, the vendor rebate settlement (MEB4) is giving the following errors:
1. Error messages generated during billing document check run
Message no. MN236
Diagnosis
Settlement accounting for rebate arrangement 85 is carried out using the general billing interface in the system (credit-side settlement type) or the general billing interface for customer billing documents (debit-side settlement type).
It is also possible that credit memos (invoice verification, credit- side settlement type) are involved.
The documents cannot be created without errors.
2. For vendor 1885 no partner exists for partner function PI
Message no. WS723
The process used to work in the 4.7 version and no changes have been made to the configuration in the new system. Can someone please suggest the reason for these errors and how they can be resolved?
Thanks,
RugmaniHI,
Please chk in the config....
SPRO>MM->Partner Deter->Partner setting in Rebate Arrangement->Define partner schemas for Rebate..
Here please check the partner function "PI" is made mandatory...
You can main the Partner function "PI" in the agreement itself...
Goto-- txn.MEB2-- enter the agreement no... inside click the icon "Agreement Partner" or (Ctrl+F2) and maintain the partner function PI..
Regards
GK. -
Problem with Sproxy transaction in SAP ECC 6.0
Hi,
I executed SPROXY transaction in SAP ECC 6.0 system, some objects of XI/PI repository are listed, some are not listed.
Why?
How can i achieve to be listed all XI/PI objects?
Thanks.Objects are listed belonging to the Software component ECC 6.0 only as you are viewing from ECC server ( makes sense?)
This link exist in SLD where Product and software components are listed.
Now if you have created a third party software component ABC and wants the objects from here also to be listed in ECC then you can go to ECC in SLD and make the Software component ECC 6.0 dependent on ABC.
regards -
Errors in Forte 3.5 -Upgrade issue
hello ,
We are having a frequent disruption in the communication SO which has an
externalConnection Class. Did anything change in 3.5? We did not have
these errors in 3L!
After these erros, we have a mutex locking problem which leaves our
application hanging.
Any help will be greatly appreciated!
thanks
suma
Here is an Excerpt of the log file
Task 9: extConn4030a808.Write: 194 bytes written to 10
INFORMATION: Network partner closed connection. This usually means the
process at the other end of the wire failed. Please go look there and
find
out why.
Class: qqsp_DistAccessException
Error #: [501, 152]
Detected at: qqcm_HoseFSM::ReceivedClose at 2
Error Time: Thu May 24 09:16:29
Exception occurred (locally) on partition "MerlinWindows_cl41_Part8",
(partitionId = F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105, taskId =
[F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105.7]) in application
"MerlinWindows_cl41", pid 23406 on node laxrc2 in environment laxrc2.
INFORMATION: Error parameters for Set:0 Msg:0:
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 1
Error Time: Thu May 24 09:16:29
Exception occurred (locally) on partition "MerlinWindows_cl41_Part8",
(partitionId = F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105, taskId =
[F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105.7]) in application
24-May-2001 09:16:47: VH.G.G..GUIT/GUI0/PLAXRC172.23.4.401/../..;PGYX;
Task 9: extConn4030a808.Write: 233 bytes written to 10
INFORMATION: Network partner closed connection. This usually means the
process at the other end of the wire failed. Please go look there and
find
out why.
Class: qqsp_DistAccessException
Error #: [501, 152]
Detected at: qqcm_HoseFSM::ReceivedClose at 2
Error Time: Thu May 24 09:16:47
Exception occurred (locally) on partition "MerlinWindows_cl41_Part8",
(partitionId = F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105, taskId =
[F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105.7]) in application
"MerlinWindows_cl41", pid 23406 on node laxrc2 in environment laxrc2.
INFORMATION: Error parameters for Set:0 Msg:0:
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 1
Error Time: Thu May 24 09:16:47
regards,
Suma Venkatesh-----Original Message-----
From: Venkatesh, Suma
Sent: Thursday, May 24, 2001 2:39 PM
To: '[email protected]'
Subject: Errors in Forte 3.5 -Upgrade issue
hello ,
We are having a frequent disruption in the communication SO which has an
externalConnection Class. Did anything change in 3.5? We did not have
these errors in 3L!
After these erros, we have a mutex locking problem which leaves our
application hanging.
Any help will be greatly appreciated!
thanks
suma
Here is an Excerpt of the log file
Task 9: extConn4030a808.Write: 194 bytes written to 10
INFORMATION: Network partner closed connection. This usually means the
process at the other end of the wire failed. Please go look there and
find
out why.
Class: qqsp_DistAccessException
Error #: [501, 152]
Detected at: qqcm_HoseFSM::ReceivedClose at 2
Error Time: Thu May 24 09:16:29
Exception occurred (locally) on partition "MerlinWindows_cl41_Part8",
(partitionId = F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105, taskId =
[F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105.7]) in application
"MerlinWindows_cl41", pid 23406 on node laxrc2 in environment
laxrc2.
INFORMATION: Error parameters for Set:0 Msg:0:
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 1
Error Time: Thu May 24 09:16:29
Exception occurred (locally) on partition "MerlinWindows_cl41_Part8",
(partitionId = F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105, taskId =
[F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105.7]) in application
24-May-2001 09:16:47: VH.G.G..GUIT/GUI0/PLAXRC172.23.4.401/../..;PGYX;
Task 9: extConn4030a808.Write: 233 bytes written to 10
INFORMATION: Network partner closed connection. This usually means the
process at the other end of the wire failed. Please go look there and
find
out why.
Class: qqsp_DistAccessException
Error #: [501, 152]
Detected at: qqcm_HoseFSM::ReceivedClose at 2
Error Time: Thu May 24 09:16:47
Exception occurred (locally) on partition "MerlinWindows_cl41_Part8",
(partitionId = F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105, taskId =
[F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105.7]) in application
"MerlinWindows_cl41", pid 23406 on node laxrc2 in environment
laxrc2.
INFORMATION: Error parameters for Set:0 Msg:0:
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 1
Error Time: Thu May 24 09:16:47
regards,
Suma Venkatesh -
R12 upgrade issue:Not able to login using forms:Please help****urgent
We have recently upgraded our instance from 11.5.9 to 12.0.4 in Windows 2003 server.
We are unable to login to forms after upgrade, however we are able access self service responsibilities without any issues.
We are getting APP-FND-01496 when we access any forms responsibility. We have tried all possible metalink notes with no luck.
Any help to resolve this issue will be appreciated.Duplicate thread ...
R12 upgrade issue:Not able to login to forms**please help
Re: R12 upgrade issue:Not able to login to forms**please help
Maybe you are looking for
-
Problem in metadata.getColumns...pl help me
Hello This is my program Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); Connection conn = DriverManager.getConnection(url+dataSource,Uname,Pwd); out = new FileOutputStream("myfile.sql"); p = new PrintStream(out); DatabaseMetaData metadata = conn.getM
-
Why my cutomize role mapper throws java.lang.ClassCastException: $Proxy67
Hello all, I customize the role mapper as follows is my MDF content <MBeanType Name = "TestRoleMapper" DisplayName = "TestRoleMapper" Package = "test.pkg.roles" Extends = "weblogic.management.security.authorization.RoleMapper" Implements = "weblogic.
-
Can i know why application store not getting downloaded
cn i know y the applications selected in the store cannot getting downloaded.....can i know wats the problem behind dat??????
-
Is BPC 7.0 compatible with Windows Terminal Server 2008?
Is BPC 7.0 compatible with Windows Terminal Server 2008? We are having printing issues when on WTS 2003.
-
guyz im pretty sure im just a victim of technology that your company and marketing advertise it and i think all people here who posting the problem in forum is the victim U better think about that!!