Movie DVD auto ejects with "error code -43" message

This issue first came up about 3 years ago but I was never able to find an answer to. This is a Combo drive (HL-DT-ST; RW/DVD GCC-4120B; revision 2.13) which still reads/writes CDs and reads DVD-ROMs without any problem. Is there any way to fix this error?

There may be system logs, reports and other evidence of
this issue in the Console or perhaps in System Profiler logs.
Some other noted error code -43 messages seen elsewhere
related to software and plugins for third party applications or
disc burn applications; but troubleshooting could include a
look to see if the cables to the optical drive are OK, and a
fix may include a replacement drive. There was an included
Apple Hardware Test with the original system software packet
so that may be something to try and hope it tells you more.
The error code may have several different causes, it would
seem; at least according to the results of some searches.
In my limited experience, my Macs have never shown that.
The code is not limited to the model of the computer; so a
repost elsewhere is not really necessary. And a similar error
code appears in later OS X versions.
Good luck & happy computing!

Similar Messages

CD Ejects with Error Code 9 - Repair Disk Permissions Greyed Out

History:
Superdrive 815CA Ejects Blank CD's to be burned w/ Error Code 9
Exact Text:
The Operation Could not be completed an unexpected error occured(error Code 9)
The CD Ejects, but the Ghost Icon of the CD image would stay
Plays previously burnt CD's/DVD's as well as market CD's/DVD's fine
Went to Disk Utility
Repair Disk Permissions(RDP) & Verify Disk Permissions(VDP) greyed out so you can'tclick them when I click on first aid
The only time they weren't greyed was when I clicked to repair the Ghost Icon CD, of which the actual CD was ejected in the first place
I cleaned the lens umteen million times - same problem
I did the Hardware repair check w/the startup CD, same problem
I bought a NEW frickin' Superdrive and installed it successfully- same problem
I went to system preferences and selected the option to open the blank CD in I tunes.
This worked for burning MP3's no problem
HOWEVER it will not open in the finder, so I can't save any data from my desktop on to a CD/DVD, so my hard Drive is getting clogged
Got a Hammer?

I loaded at least 20 different BLANK CD's to experiment with.
The same CD's which get spat out when I open it in finder, burn fine when i open them up in I tunes
I've already bought a new drive and the same problem occurs as when i had the old drive (can't open in finder), so i believe the bad drive and bad CD premise has been troubleshot.
It seems like it won't recognize the Drive or CD when i try to launch a CD from the finder
The blank CD's burn music fine when I open it up in I tunes, but not when I try to open it up in the finder when i try to put data on the CD's.

Transport control program tp ended with error code 0211

Dear Experts,
I have a problem in doing the import after the client export was successfully done.
I am actaully tring to do a client import/export from the PRD server to DEV server.
On PRD the client is 900 and on the DEV the client is 240.
I have manually copied the transport requests created into the
/usr/sap/trans/cofiles and /usr/sap/trans/data folders to the same on the DEV server.
After coping them,
I have tried to add these transport requests to the DEV server queue, i get the following error message
Transport control program tp ended with error code 0211
Message no. XT200
Diagnosis
An error occurred when executing a tp command.
Command: ADDTOBUFFER RT2KT00014 RT1 pf=/usr/sap/trans/bin/T
Return code: 0211
Error text: no info about transport request found
Request: RT2KT00014
System Response
The function terminates.
Procedure
Correct the error and execute the command again if necessary.
After this I have tried to add the transports to the buffer at the OS level using the command
./tp pf=TPPARAM addtobuffer "RT2KT00014" RT1 U18 by going to the folder
/usr/sap/trans/bin
But it says that the tp is not found.
I have also checked the permissions for the TRANS folder, it has full access i.e 777
This is where i am struck, and the client has to be imported asap as the requirement for the SUPPORT TEAM is very urgent.
We are on AIX, Oracle 10G and ECC6
Thanks and regards
Harry

Dear Imtiaz,
Thanks for your quick fire reply...
The link helped me but it could not resolve my issue..
Infact i found it my self that the transport requests had to be given full FILE PERMISSIONS at the OS level
I logged in as ROOT
and changed directory to /usr/sap/trans/cofile and gave the command
chmod 777 RT00014.RT2 and
chmod 777 RX00014.RT2
and then went to STMS>SYSTEMS>Import View>Extras>Other requests--> Add ..
Here i added the request nos and then it added up in the queue and then i started the import.
Anyway thank you very for your reply..
Awareded points to you.
Thanks and regards
Harry...

Transport control program tp ended with error code 0249

Hello guys,
I am facing an when importing transport. After I click import to the transport in STMS, before it runs, a message window is displayed immediately. This was working find until last week, any kind of transport is followed by the same error.
Transport control program tp ended with error code 0249
Message no. XT200
Diagnosis
An error occurred when executing a tp command.
Command: IMPORT BWDK903312 BIW client200 U0 pf=
sapbiw1a\s
Return code: 0249
Error text: connect failed due to DbSL load lib failure
Has anyone faced this error while trying to import a transport? I have not found the same error in sdn (0249)
help will be appreciated.
thanks
DGF

Your are right, but which is the Basis forum?
Business Process Expert
Database & OS Platforms ABAP Development
Enterprise SOA Portal
Emerging Technologies
SAP Solutions
Business Intelligence
Scripting Languages
SAP Business One Industries
Community Discussions
SAP NetWeaver Application Server Integration and Certification Center (ICC)

Transport control program tp ended with error code 0203

when i import queue and transport queue from dev to prd ,error show:
Transport control program tp ended with error code 0203
Message no. XT200
Diagnosis
An error occurred when executing a tp command.
Command: IMPORT DEVK900298 P01 clientP01 U0 pf=/usr/sap/tra
Return code: 0203
Error text: wrong syntax in tp call
Request: DEVK900298
System Response
The function terminates.
Procedure
Correct the error and execute the command again if necessary.

Dear Allen,
The transport control program tp collects all return codes that occur when a tp command is executed. From all of these single return codes, a combined return code is calculated that tp outputs as a result at the end the command. During an import, for example, all return codes for individual import steps are handled. If a special return code does not occur, then the combined return code at the end is the maximum of individual return codes that occur. In addition to the value of the return code, tp also gives a short description of this return code. You can display this short description using the command explainrc.
Normally, all return codes that occur originate from individual transport steps. Since these individual return codes can only have the following values 0, 4, 6, 8, 12, 13, 14, 16, the combined return code also has one of these values. However, if a general error occurs, a single return code over 200 is generated. For example, this could arise if tp cannot establish a connection to the database. The maximum return code for all single transport steps is output in a separate message before specifying the combined returned code. In this case, the combined return code is always the return code of the general error message.
tp Commands:
tp addtobuffer <request> <sapsid>
As of Release 4.6A, an explicit addtobuffer command leaves the position of the entry unchanged, if the relevant transport request is already in the buffer. Only the status of the entry is changed:
Unconditional modes appearing in the command line are added to the unconditional modes in the buffer.
All the steps of the entry are re-initialized.
If the entry found is not an initial entry, the import step for the command file is set to *4000 .
Before you call this command and its options, consider the effects of changing the import sequence.
tp cleanbuffer <sapsid>
This deletes successfully imported change requests from the list of requests that are marked for import into the SAP System <SAPSID>. This function is contained in the commands tp import all <sapsid> and tp put <sapsid> .
tp delfrombuffer <request> <sapsid>
If the specified request is marked for import into the specified SAP System, this flag is deleted from the import list.
Before you call this command, consider the effects of changing the import sequence.
As of Release 4.6A: If a transport request was only partially imported, you can delete this type of transport request from the buffer. However, if a deleted transport request is placed in the buffer (without having been initially or completely imported), the attributes of the old entry are reactivated. This means the return codes, the unconditional modes and tags of the deleted entry appear in the new entry.
tp delstopmark <sapsid>
If the list of requests marked for import into the specified SAP System contains a STOP mark, the mark is deleted.
tp export <request>
This exports the complete request from the source system. This command starts the export of a request from the operating system level. Only use this command in exceptional cases. The SAP System uses the command expwbo to release requests from CTS transactions.
tp reformatbuffer <sapsid> [options]
This automatically reformats the entire buffer.
As of Release 4.5A, there are 2 different formats for buffer entries. (As of Release 4.5A, tp can work with both formats, and with a puffer containing heterogeneous entries. As of Release 4.6A, tp can work with 3 formats.)
However, in certain cases entries with the old formatting have to be reformatted during the normal run of tp . In this case, the entire buffer is automatically reformatted.
If you use the options downtorelease and Iagree for command reformatbuffer , you can format the buffer so that its formatting is compatible with an older release:
Option downtorelease <Release>
The command reformatbuffer with this option formats the buffer so that the formatting corresponds to the one used in an old release. This is necessary if tp writes buffer entries to the buffer of another system, but uses a buffer format that the transport control programs does not understand in this system.
Since older formats cannot store the same amount of information as the newer ones, some information contained in the original buffer may not be stored in the unformatted buffer. This may lead to data loss.
To avoid data loss, the original buffer is stored. In addition, you have the following functions:
Displaying the unformatted buffer (using showbuffer <SID> )
Displaying the original buffer (using showbuffer buffer=<SID>SAV )
Accepting the unformatted buffer (using reformatbuffer and the option Iagree yes )
Resetting the changes (using reformatpuffer and the option Iagree no )
If you call reformatpuffer using downtorelease , tp displays in detail if information was lost by reformatting, and what that information was. tp also names the commands that is has to execute to accept or reject the changes.
If you use the option downtorelease , you must also specify the option Iagree with yes or no . You cannot use the transport system until you decide to accept or reject the changes.
Option Iagree
Here are the following values for this option:
yes ( true )
Accept the change made by tp reformatbuffer <SID> downtorelease <rel>
In this case, tp deleted the buffer semaphore file that was lifted for security reasons at the first call of reformatbuffer
no ( false )
Reject the change made by tp reformatbuffer <SID> downtorelease <rel> In this case, tp copies the backup of the original buffer back and deletes the buffer semaphore file that was lifted for security reasons at the first call of reformatbuffer
tp setstopmark <sapsid>
A special STOP mark is added to the list of requests registered for import into the specified SAP System. The commands tp import all <sapsid> and tp put <sapsid> only process the requests in front of this stop mark.
If there is no stop mark, it is automatically generated by the commands
tp import all <sapsid> and tp put <sapsid> .
When all the requests in front of the stop mark have been imported successfully, at the end of all the calls the related marks and the mark itself are deleted.
A STOP mark can only be placed at the end of the change requests that have already been marked. In addition, it can only be set if no other mark of the same kind already exists.
tp showparams <sapsid>
This tp function displays which values the individual parameters of the transport profile have for the current SAP System.
tp verse <request>
This creates versions of the objects in the specified request. This transport step is contained in command export .
As of Release 4.5A, more actions that prepare the export are performed in this step.
Thanks and Regards,
Naveen.

Tp ended with error code 0247 - addtobuffer has problems with data- and/or

Hello Experts,
If you give some idea, it will be greatly appreciated.
This transported issue started coming after power outage, sap system went hard shutdown.
Then we brought up the system. Before that , we do not have this transport issue.
our TMS landscape is
DEV QA-PRD
SED-SEQSEP
DEV is having the TMS domain controller.
FYI:
*At OS level, when we do scp command using root user, it is fine for any TR.
In STMS, while adding TR in SEQ(QA system), we are getting error like this.
Error:
Transport control program tp ended with error code 0247
     Message no. XT200
Diagnosis
     An error occurred when executing a tp command.
       Command:        ADDTOBUFFER SEDK906339 SEQ client010 pf=/us
       Return code:    0247
       Error text:     addtobuffer has problems with data- and/or
       Request:        SEDK906339
System Response
     The function terminates.
Procedure
     Correct the error and execute the command again if necessary.
This is tp version 372.04.71 (release 700, unicode enabled)
Addtobuffer failed for SEDK906339.
Neither datafile nor cofile exist (cofile may also be corrupted).
standard output from tp and from tools called by tp:
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0247

when we do scp using sm69,
SEDADM@DEVSYS:/usr/sap/trans/cofiles/K906339.SED SEQADM@QASYS:/usr/sap/trans/cofiles/.
it throws the error like below,
Host key verification failed.
                                                                                External program terminated with exit code 1
Thanks
Praba

Help with Transport control program tp ended with error code 0203

when i import queue and transport queue from dev to prd ,error show:
Transport control program tp ended with error code 0203
Message no. XT200
Diagnosis
An error occurred when executing a tp command.
Command: IMPORT DEVK900298 P01 clientP01 U0 pf=/usr/sap/tra
Return code: 0203
Error text: wrong syntax in tp call
Request: DEVK900298
System Response
The function terminates.
Procedure
Correct the error and execute the command again if necessary.

Thank you !
My DEV system TP profile parameters is :
TRANSDIR            = /usr/sap/trans
DEV/CTC             = 0
DEV/DBHOST          = P550A
DEV/DBLIBPATH       = /usr/sap/DEV/DVEBMGS01/exe
DEV/DBNAME          = DEV
DEV/DBTYPE          = ora
DEV/NBUFFORM        = 1
DEV/TP_VERSION      = 266
#System from Transport Domain DOMAIN_P01
#TMS:0002:DOMAIN_P01
P01/DUMMY           = 1
P01/NBUFFORM        = 1
P01/TP_VERSION      = 266
P01/CTC             = 1
My PRD system TP profile parameters is :
P01/CTC             = 0
P01/DBHOST          = XCPRD01
P01/DBLIBPATH       = /usr/sap/P01/DVEBMGS01/exe
P01/DBNAME          = P01
P01/DBTYPE          = ora
P01/NBUFFORM        = 1
P01/TP_VERSION      = 266
#System from Transport Domain DOMAIN_DEV
#TMS:0009:DOMAIN_DEV
DEV/DUMMY           = 1
DEV/NBUFFORM        = 1
DEV/TP_VERSION      = 266
DEV/CTC             = 1

Launch failed with error code -2857

I've been running an app (EPSON Scan) for awhile without any significant problems. Today I check the Epson web site and they had an update for the app. So, I downloaded it, installed it, and tried to run it. Unfortunately, all I got was a couple of bounces in the Dock and nothing. I then went to the console and found the "launch failed with error code -2857" message. I've researched that as best I could and found that it is probably a problem with the application bundle. So, I opened the package, drilled down to the Mac OS folder, and double clicked on the EPSON Scan terminal command located there. Bing, a terminal window opened and the application launched and runs fine. So, the questions is, how do I resolve the CFM not finding the application correctly? I've run a pre-bind on everything but that didn't work. Seems to me like there is some config file that is not set up properly. I looked at the Info.plist file and I don't see any glaring problems. Any ideas? Epson also go a copy of this note...

First I want to say thanks for the feedback. I appreciate the support and helpful suggestions.
Second, Epson sent me an answer of sorts...they provided detailed instructions on uninstalling the application and then told me to reinstall using the disk image from their web site (in other words, don't use their web package to "update" and existing installation). I did this and things seem to be running fine now. It's unfortunate that their update instructions don't say to do this in the first place (maybe I missed it ).
So at one level this issue is solved. Unfortunately I'm too curious and wanted to know why the error happend in the first place. As a software developer myself (mainframe and midrange server based) I hate the "delete and reinstall" answer as it does nothing to really identify and solve the real problem. But I do also appreciate the idea of "just get it fixed fast" so that's what I did.
Anyway, I will now spend some time learning about Launch Services to see if I can get a more specific understanding of what happened.
Thanks again for the help.
24" iMac, 2GB Memory, etc Mac OS X (10.4.8) 20" iMac, two MacBooks, one Dual Core Mac Mini

TS1539 How do we deal with Error 50 when downloading a movie rental then stopped with error 50 and when I try to resume the downld, it doesn't do it?

How do we deal with Error 50 when downloading a movie rental then stopped with error 50 and when I try to resume the downld, it doesn't do it?

Yeah this "fix" is bunk. The movie is downloading just fine, but the extra features is the one giving me this error code. It is NOT my firewall. If it was, then both files wouldn't download. Plus, I already have the firewall "issue" tacked down and fixed. Have had it fixed for months now. No, this is due to the "new" itunes version 11 software. The only conclusion to fix this issue is UPgrading from 11 back to 10.7 which is what I am going to do. This is completely ridiculous! Come on, Apple, get itunes working once and for all, and fire the people responsible for itunes 11, just like you did to the guy who was responsible for apple maps. Thankfully Google came back to the rescue with google maps app.

OPatch failed with error code 74

- What can I do to fix this error when applying an Oracle patch for 10.2.0..2 on HP-UX B11.11 64 Bits.
- I get this error when applying all patches.
This is the screen shot.
dr3dvqa:orau3d 103> cd /oracle/stage/102_64/patches/5063279; opatch apply -force
Invoking OPatch 10.2.0.2.5
Oracle Interim Patch Installer version 10.2.0.2.5
Copyright (c) 2007, Oracle Corporation. All rights reserved.
Oracle Home       : /oracle/U3D/102_64
Central Inventory : /oracle/oraInventoryU3D
   from           : /var/opt/oracle/oraInst.loc
OPatch version    : 10.2.0.2.5
OUI version       : 10.2.0.2.0
OUI location      : /oracle/U3D/102_64/oui
Log file location : /oracle/U3D/102_64/cfgtoollogs/opatch/opatch2008-03-04_16-08-50PM.log
ApplySession applying interim patch '5063279' to OH '/oracle/U3D/102_64'
Interim patch 5063279 is a superset of the patch(es) [ 5063279 ] in OH /oracle/U3D/102_64
OPatch will rollback the subset patches and apply the given patch.
Running prerequisite checks...
Prerequisite check "CheckRollbackable" on auto-rollback patches failed.
The details are:
Patch 5063279:
Archive Action: Source file "/oracle/U3D/102_64/.patch_storage/5063279_Nov_28_2006_04_15_32/files/lib/libserver10.a/kdibl.o" does not exist.
'oracle.rdbms, 10.2.0.2.0': Cannot update file '/oracle/U3D/102_64/lib/libserver10.a' with '/kdibl.o'
ApplySession failed during prerequisite checks: Prerequisite check "CheckRollbackable" on auto-rollback patches failed.
System intact, OPatch will not attempt to restore the system
The following warnings have occurred during OPatch execution:
1) OUI-67078:Interim patch 5063279 is a superset of the patch(es) [ 5063279 ] in OH /oracle/U3D/102_64
OPatch failed with error code 74

The log file
/oracle/U3D/102_64/cfgtoollogs/opatch/opatch2008-03-04_16-08-50PM.log
has this ...
SEVERE:OPatch invoked as follows: 'apply -force '
INFO:
Oracle Home       : /oracle/U3D/102_64
Central Inventory : /oracle/oraInventoryU3D
   from           : /var/opt/oracle/oraInst.loc
OPatch version    : 10.2.0.2.5
OUI version       : 10.2.0.2.0
OUI location      : /oracle/U3D/102_64/oui
Log file location : /oracle/U3D/102_64/cfgtoollogs/opatch/opatch2008-03-04_16-08-50PM.log
INFO:Starting ApplySession at Tue Mar 04 16:08:51 GMT-07:00 2008
INFO:Starting Apply Session at Tue Mar 04 16:08:51 GMT-07:00 2008
INFO:ApplySession applying interim patch '5063279' to OH '/oracle/U3D/102_64'
INFO:Starting to apply patch to local system at Tue Mar 04 16:08:51 GMT-07:00 2008
INFO:Start the Apply initScript at Tue Mar 04 16:08:51 GMT-07:00 2008
INFO:Finish the Apply initScript at Tue Mar 04 16:08:51 GMT-07:00 2008
INFO:Patch 5063279 is superset of 5063279
INFO:Patch 5063279 has no conflicts/superset wiht any other patch processed till now
INFO:Checking conflicts for patch: 5063279
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5063279
INFO:Checking conflicts/supersets for patch: 5063279 with patch:4518443
INFO:Checking conflicts/supersets for patch: 5063279 with patch:4271217
INFO:Checking conflicts/supersets for patch: 5063279 with patch:3748430
INFO:Checking conflicts/supersets for patch: 5063279 with patch:6771608
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5746835
INFO:Checking conflicts/supersets for patch: 5063279 with patch:6740811
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5632264
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5499655
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5390946
INFO:Checking conflicts/supersets for patch: 5063279 with patch:4704890
INFO:Checking conflicts/supersets for patch: 5063279 with patch:6729801
INFO:Checking conflicts/supersets for patch: 5063279 with patch:6663258
INFO:Checking conflicts/supersets for patch: 5063279 with patch:6455795
INFO:Checking conflicts/supersets for patch: 5063279 with patch:6447320
INFO:Checking conflicts/supersets for patch: 5063279 with patch:6435823
INFO:Checking conflicts/supersets for patch: 5063279 with patch:6340979
INFO:Checking conflicts/supersets for patch: 5063279 with patch:6153847
INFO:Checking conflicts/supersets for patch: 5063279 with patch:6046043
INFO:Checking conflicts/supersets for patch: 5063279 with patch:6005996
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5495639
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5099992
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5941030
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5308692
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5762514
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5636728
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5635254
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5618049
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5581518
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5530958
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5442919
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5377099
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5369855
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5103126
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5063279
INFO:Patch 5063279 is Superset of 5063279
INFO:Checking conflicts/supersets for patch: 5063279 with patch:5052029
INFO:Checking conflicts/supersets for patch: 5063279 with patch:4952782
INFO:Checking conflicts/supersets for patch: 5063279 with patch:4883635
INFO:Checking conflicts/supersets for patch: 5063279 with patch:4864648
INFO:Checking conflicts/supersets for patch: 5063279 with patch:4773931
INFO:Checking conflicts/supersets for patch: 5063279 with patch:4668719
WARNING:OUI-67078:Interim patch 5063279 is a superset of the patch(es) [ 5063279 ] in OH /oracle/U3D/102_64
INFO:OPatch will rollback the subset patches and apply the given patch.
INFO:
Running prerequisite checks...
INFO:Space Needed : 657540
INFO:Prereq checkPatchApplicableOnCurrentPlatform Passed for patch : 5063279
INFO:Start fuser command /usr/sbin/fuser /oracle/U3D/102_64/bin/oracle at Tue Mar 04 16:08:55 GMT-07:00 2008
INFO:Finish fuser command /usr/sbin/fuser /oracle/U3D/102_64/bin/oracle at Tue Mar 04 16:08:55 GMT-07:00 2008
INFO:
Patch 5063279:
Archive Action: Source file "/oracle/U3D/102_64/.patch_storage/5063279_Nov_28_2006_04_15_32/files/lib/libserver10.a/kdibl.o" does not exist.
'oracle.rdbms, 10.2.0.2.0': Cannot update file '/oracle/U3D/102_64/lib/libserver10.a' with '/kdibl.o'
INFO:Prerequisite check "CheckRollbackable" on auto-rollback patches failed.
The details are:
Patch 5063279:
Archive Action: Source file "/oracle/U3D/102_64/.patch_storage/5063279_Nov_28_2006_04_15_32/files/lib/libserver10.a/kdibl.o" does not exist.
'oracle.rdbms, 10.2.0.2.0': Cannot update file '/oracle/U3D/102_64/lib/libserver10.a' with '/kdibl.o'
SEVERE:OUI-67074:ApplySession failed during prerequisite checks: Prerequisite check "CheckRollbackable" on auto-rollback patches failed.
INFO:System intact, OPatch will not attempt to restore the system
INFO:----
INFO:The following warnings have occurred during OPatch execution:
INFO:1) OUI-67078:Interim patch 5063279 is a superset of the patch(es) [ 5063279 ] in OH /oracle/U3D/102_64
INFO:----
INFO:Finishing ApplySession at Tue Mar 04 16:08:55 GMT-07:00 2008
INFO:Total time spent waiting for user-input is 0 seconds. Finish at Tue Mar 04 16:08:55 GMT-07:00 2008
INFO:Stack Description: oracle.opatch.PrereqFailedException: Prerequisite check "CheckRollbackable" on auto-rollback patches failed.
INFO:StackTrace: oracle.opatch.OPatchSessionHelper.runApplyPrereqs(OPatchSessionHelper.java:3635)
INFO:StackTrace: oracle.opatch.ApplySession.processLocal(ApplySession.java:3529)
INFO:StackTrace: oracle.opatch.ApplySession.process(ApplySession.java:5238)
INFO:StackTrace: oracle.opatch.OPatchSession.main(OPatchSession.java:1544)
INFO:StackTrace: oracle.opatch.OPatch.main(OPatch.java:570)
INFO:File "/oracle/U3D/102_64/.patch_storage/patch_unzip" cannot be deleted as it does not exist

Satellite A80 - in device manager ODD listed with with error code 39

Hello,
I have a Satellite A80 127. I have an issue with my CD drive.
When I was trying to upgrade my XP home edition to XP Pro SP2, display said on rebooting that it couldn't read from my CD drive. On inspection I found that my CD/DVD drive is unable to read CDs though it can read DVDs. From what I remember, it was working fine couple of days before.
I was trying to locate the source of problem and through the Troubleshoot option I found that I have a yellow exclamation mark against my SCSI/RAID host controller in my Device Manager (with error code 39). I haven't been able to update the driver it will give me error message. Also, there was a Nero SCSI/RAID controller. I tried removing it to check whether the main one works, but still no success.
Any suggestion would be great and in the meantime I will try to find similar threads.
Thanks
karthik

Hi,
Thanks for the link.
I tried using the 'guided registry' and it showed that all upper and lower filters were cleared in registry. But the CD read problem is still unsolved.
Anyone has any further suggestion?
Thanks a lot !
karthik

Transport control program tp ended with error code 0212

Hi all,
I have created a two system landscape of development & production server. But while I am releasing any request from develpoment server a error is showing: " Transport control program tp ended with error code 0212 Errors: could not access file as supposed (see dev_tp or S".I have chosen development server as domain controller. TMS alert viewer error message also contains the following information------>command: TMS_MGR_READ_TRANSPORT_QUEUE
 service: transport service
 start : online
 Function: TMS_TP_SHOW_BUFFER
 message: TP_REPORTED_ERROR
In import monitor it's showing : "tp finished: could not access file as supposed (see dev_tp or SLOG1113.K"
Can you tell me how to resolve this issue?

dev_tp contains:
This is R3trans.exe version 6.14 (release 700 - 09.04.10 - 11:26:00).
unicode enabled version
usage: R3trans.exe [<options>] <control_file>
The control_file describes what R3trans has to do.
The following options are possible:
-c f1 f2 : Copy file f1 to f2 with character set conversion.
-d : DB connect. Test if SAP database is available.
-i file : Import from file without using a control file.
-l file : List the contents of file to the log file.
-m file : List the contents of file to allow tp to create a cofile.
-t : Test. All database changes are rolled back.
-t4 : Trace level 4. Switch on developer trace.
-u <int> : Unconditional modes. See below.
-v : Verbose. Write more details to the log file.
-w file : Log file. The default log file is 'trans.log'.
-x : DB connect without access on any SAP table.
R3trans.exe finished (0012).
& the slog file is not there in the trans/log directory

Installation of Photoshop update 13.1.2 for creative cloud fails with error code U44M1P7 I need help

I need help installing update 13.1.2 for Photoshop creative cloud, installation fails with error code: U44M1P7. Could someone please help?

Sorry to bother you.
I could find the answer after searching previous posts about this language problem.
Had to change my language in AAM profile and then download PS CS6 again ( english version ).
Then open the actual Photoshop and in preferences > interface you can besides the Dutch also option for English.
restart application and Voila.
Greetz, Jeroen

SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

SAP ECC error:'Migration Monitor' exits with error code 103.

Hi All,
I am doing SAP ECC installation for windows 32 bit with MAXDB as backend.
I am stuck at the import ABAP.Getting error
ERROR 2008-08-08 16:10:53
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
1) imort_monitor.java.log-->contains
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 0, completed 18, failed 0, total 19.
Loading of 'SAPVIEW' import package: ERROR
Import Monitor jobs: running 0, waiting 0, completed 18, failed 1, total 19.
2)import_monitor.log
ERROR: 2008-08-08 16:10:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPVIEW' import package is interrupted with R3load error.
Process 'D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -nolog -c 0' exited with return code 2.
For mode details see 'SAPVIEW.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
INFO: 2008-08-08 16:10:52
All import packages are processed.
WARNING: 2008-08-08 16:10:52
1 error(s) during processing of packages.
INFO: 2008-08-08 16:10:52
Import Monitor is stopped.
3)SAPVIEW.log
error message returned by DbSl:
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE VIEW "Z_T_CO_BW" ( "KOKRS" , "KOSTL" , "VERSN" , "KSTAR" , "WOG001" , "MEG001" ) AS SELECT T0002."KOKRS", T0002."KOSTL", T0001."VERSN", T0001."KSTAR", T0001."WOG001", T0001."MEG001" FROM "COSS" T0001, "CSKS" T0002 WHERE T0002."MANDT" = T0001."MANDT")
DbSlExecute: rc = 103
(SQL error -942)
error message returned by DbSl:
(DB) INFO: disconnected from DB
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: job finished with 3108 error(s)
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20080808174211
Only SAPDB: SAPSID srvice of SAP DB is only up.
No other services of database are up.And i am not able to up the other services also.
Is it required to up the other services?
If not?
Why this error is occuring?
Any help will be appreciated.
Thanks&Regards
Manisha das

Hello Manisha,
The one of the possible reasons for this is due to lack of H/W.
Increase your RAM size to atleast 2GB and utilise the same while you are installing ECC in database parameters step..
If the issue is with H/W, then this should fix the issue.
Hope it helps,
Regards,
Satish.

Movie DVD auto ejects with "error code -43" message

Similar Messages

Maybe you are looking for