Kernel patches application error

Hi all,
I was trying to upgrade my Solution manager 4.0.My system is 64 bit on windows with oracle.Current kernel is 7.00 with patch 75.Now i tried upgrading to 83.I stopped my SAP and database.I downloaded the kernel patches from SAP site and logged into solution manager as SIDadm,uncared those files.Took the backup of exe directory,removed all the files from the directory and copied the kernel patches.Now when i tried to up the SAP,it did got up but the kernel level is still 75.i dont know what to do.
Please help me,its very urgent
Thanks in advance
Regards
Praveen

Hi all,
I faced a new problem now.
After stopping the SAP and database,i took the backup of the kernel directory,removed all the files from the kernel directory and then copied the new kernel files in this directory.Then i started the database and then started SAP using MMC.It started and i checked the kernel version and it was updated but in MMC it showed strdbs.cmd could not be started ,can you please tell me wats the reason
also should i stop the database?shld i only SAP from MMC and then update kernel.
Please help i m in soup now.
Regards
Praveen

Similar Messages

Kernel Patch upgrade results into error

Recently, we upgraded our R/3 640 kernel from patch number 196 to 327. It went successful.
But now, the Sales and order team is having problem in saving the orders(VA02, VA01).
While saving Sales order, error pops up saying "dialog step number missing".
Kindly suggest.

Hi ppl,
The problem has been resolved.
As i said, problem wasnt with the upgrade, but came thereafter, functional team faced issues while switching between the windows.
Problem was with the Gui level, it needed to be upgraded too after the kernel patch upgrade.
Thanks a lot for putting your thoughts.
Thanks

DB13 Job running error after upgate kernel patch

Dear Gurus,
I update sap kernel patch from level 159 to level 236 on QAS and DEV
and then, all DB job on DB13 error occure.
 
21.02.2010 07:00:47 Job started 
21.02.2010 07:00:47 Step 001 started (program RSDBAJOB, variant &0000000000014, user ID SAP*) 
21.02.2010 07:00:47 Execute logical command BRCONNECT On host eccqas 
21.02.2010 07:00:47 Parameters: -u / -jid CLNUP20081026070000 -c -f cleanup 
21.02.2010 07:00:48 > Function: BtcXpgPanicCan't exec external program (No such file or directory) 
21.02.2010 07:00:48 External program terminated with exit code 1 
21.02.2010 07:00:48 BRCONNECT returned error status E 
21.02.2010 07:00:48 Job finished 
 
21.02.2010 20:00:48 Job started
21.02.2010 20:00:48 Step 001 started (program RSDBAJOB, variant &0000000000019, user ID SAP*)
21.02.2010 20:00:48 Execute logical command BRCONNECT On host eccqas
21.02.2010 20:00:48 Parameters: -u / -jid STATS20081026200000 -c -f stats -t ALL
21.02.2010 20:00:49 > Function: BtcXpgPanicCan't exec external program (No such file or directory)
21.02.2010 20:00:49 External program terminated with exit code 1
21.02.2010 20:00:49 BRCONNECT returned error status E
21.02.2010 20:00:49 Job finished
 
System : ECC 6.0 OS: Solaris DB Oracle 10g
Best regards,

Hi,
Please ensure that sapxpg executable is located in your SAP Kernel directory where you have applied new kernel.
Whats the permission of sapxpg executable ? Check them.
Also check SM21 , dev_sapxpg and the required Work Process traces along with the testing of SAPXPG_DBDEST_<hostname> RFC. This will be helpful in finding the possible causes for the same.
Please refer this[ useful thread|DB 13 (CHECKDB) Can't exec external program (No such file or directory)] which is describing the same symptoms along with this [informative link|http://help.sap.com/saphelp_47x200/helpdata/en/c4/3a80c4505211d189550000e829fbbd/content.htm].
Regards,
Bhavik G. Shroff

Backup error after kernel patch upgrade

Hi.
I have a backup problem after the kernel patch upgrade. I have SAP R3 4.6C on HPUX11.0 with an Oracle 8.17 database.
I have upgraded kernel patch from 1655 to 2337.
Afterward, I am getting following backup error:
BR280I Time stamp 2007-11-06 09.29.01
BR279E Return code from '/usr/sap/HAD/SYS/exe/run/backint -u HAD -f backup -i /oracle/HAD/sapbackup/.bdwnpztp.lst -t file_online -c': 2
BR232E 0 of 115 files saved by backup utility
BR280I Time stamp 2007-11-06 09.29.01
BR231E Backup utility call failed
Does anyone know how to correct this?
Thank you.

Hi Jun,
backint is a link file that is in SAP kernel directory which links to the backup client on the server.
eg:
lrwxrwxrwx 1 root other 32 Aug 13 2004 backint -> /usr/openv/netbackup/bin/backint
As part of kernel upgrade process, the kernel is backed up, mostly on the disk before upgrading. Check if this link exists and recreate it in the kernel directory, if no backup was done, compare it with other systems to get the details of the backint link.
Cheers,
Nisch

Acrobat application error after 8.2.2 patch

I pushed out the Acrobat 8.2.2 patch this week to our users and have gotten a handful of people respond that they're getting an error when they're launching Acrobat afterwards.
Background:
Workstations were running Acrobat 8.2.0 before the patch and all patched previously (from at least 8.1.6) without any issues. Adobe Reader is not installed on these systems.
Workstations are all running Windows XP SP3.
Problem:
User gets a warning message when launching Acrobat that reads "A serious error has been detected and Adobe Acrobat 8.1.2 Professional cannot continue. Please reinstall the application and try again." When the click the OK button on that dialog they are then prompted with an Application Error dialog for Acrobat.exe "The instruction at '0x05bb1243' referenced memory at '0x03db9bec'. The memory could not be 'written'"
Workaround:
A simple reboot resolves the issue sometimes, other times a repair is needed and others need to be reinstalled.
Anyone got any ideas why these errors are occurring and what I should be looking out for so that this doesn't repeat in the future?

Just noticed this post was a bit old......My version with the same issue was 8.2.6.
This seems to be a recurring issue if you seach the forums.
I was able to fix mine with a repair instead of an uninstall reinstall.
I accessed the repair option via the control panel ----->add/remove software----->adobe acrobat pro

SAPCAR error when extracting kernel patches

Hi gurus
I am having the following error when extracting so kernel patches:
SAPCAR could not open for writing sapcar.exe <error 28>.The process cannot acces the file becaues it is being used by another process.
Maybe its saying that because sapcar is the on that is extracting this patch an now it cant open it.i have followed not 211077 but still not winning.
on Windows2k3 64bit
Any ideas welcome

you can rename the sapcar.exe to oldsapcar.exe and execute oldsapcar.exe
or you can move to a different directory and execute from there.

Problem of SIGPOLL(SI_NOINFO) in latest Solaris9 kernel patch

Hi,
We are facing a rather strange problem with the latest kernel patch on Solaris 9. (Generic_112233-08). We had not faced this problem with any of the other kernel patches of Solaris 9.
Our application has a main thread and a single child thread (pthread). The main thread schedules aio_writes() on the raw disk interface and lets the child thread block on sigwaitinfo() to listen to the signal completion notification. This is communicated to it via the SI_ASYNCIO code of SIGPOLL. The child thread then informs the main thread by writing to a bi-directional pipe. Since the main thread has registered for read interest on the bi-directional pipe (via /dev/poll) it is informed of the completion of the aio_write() without having to block itself. Under normal circumstances, the child thread receives SIGPOLL with SI_ASYNCIO code.
This application has been running fine on all the previous builds of Solaris (Generic, Generic_112233-04, Generic_112233-06) on sparc platform expect with the latest kernel patch. The child thread now keeps receiving SIGPOLL with SI_NOINFO code. There has been no change in our application and we are perplexed to the reason of this behaviour. Since it is SI_NOINFO there is not much debugging information we can get.
We have been able to replicate this behaviour using a small stand-alone program. We are attaching it at the end of the email. We tried this program on a couple of different Sparc systems and were able to reproduce this behaviour on one of them but not on the other.
Has anybody faced problems with regard to SIGPOLL in the latest kernel patch of Solaris 9 for sparc systems ?
Thanks
Regards
Raj Pagaku
proxy-24:~ >uname -a
SunOS proxy-24 5.9 Generic_112233-08 sun4u sparc SUNW,Ultra-5_10
proxy-24:~ >gcc -v
Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.9/3.2/specs
Configured with: ../configure with-as=/usr/ccs/bin/as with-ld=/usr/ccs/bin/ld --disable-nls
Thread model: posix
gcc version 3.2
Compiled this program using the following command : gcc -g kernel_bug.c -lrt -lpthread
#include <stdio.h>
#include <aio.h>
#include <errno.h>
#include <fcntl.h>
#include <pthread.h>
#include <signal.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
#include <sys/resource.h>
#include <sys/stat.h>
#include <sys/types.h>
#define min(x,y) (((x)<=(y))?(x):(y))
#define DISPLAY_COUNT 10000
typedef struct DiskInfoCallOut {
void (*func_ptr)(void *);
void *data_ptr;
} DiskInfoCallOut;
typedef struct DiskInfo {
struct aiocb di_aiocb;
DiskInfoCallOut di_callout;
off_t di_currOffset;
int di_scheduled;
} DiskInfo;
typedef struct Disk {
int fd;
char *buffer;
int bufferLen;
} Disk;
static sigset_t aioSignalSet;
int aioSigFD[2];
int glob_scheduled = 1;
int glob_respond = 1;
Disk disk;
static void LaunchDiskOperation(DiskInfo *di);
char BUFDATA[4096] = {'a'};
char rawDeviceName[256] = "/dev/rdsk/";
static void
InitializeDisk()
int fd;
if ((fd = open(rawDeviceName, O_RDWR, 0)) == -1) {
fprintf(stderr, "Unable to open raw device \n");
exit(-1);
disk.fd = fd;
disk.buffer = BUFDATA;
disk.bufferLen = sizeof(BUFDATA);
static void
AIOSignalHandler(int sigNum, siginfo_t* si, void* context)
fprintf(stderr, "WARN: got signal %d in AIOSignalHandler!\n", sigNum);
/* Function implementing the slave thread */
static void*
AIOSignalThread(void *arg)
struct sigaction sa;
siginfo_t info;
sigset_t ss;
int sig_num;
int retVal;
/* Initialize the signal set*/
sigemptyset(&ss);
sigaddset(&ss, SIGPOLL);
if ((retVal = pthread_sigmask(SIG_SETMASK, &ss, NULL))) {
fprintf(stderr, "pthread_sigmask failed in AIOSignalThread \n");
exit(-1);
sa.sa_handler = NULL;
sa.sa_sigaction = AIOSignalHandler;
sa.sa_mask = aioSignalSet;
sa.sa_flags = SA_SIGINFO;
if (sigaction(SIGPOLL, &sa, NULL)) {
fprintf(stderr, "sigaction in AIOSignalThread \n");
exit(-1);
/* Wait infinitely for the signals and respond to the main thread */
while (1) {
sig_num = sigwaitinfo(&aioSignalSet, &info);
if (sig_num != SIGPOLL) {
fprintf(stderr, "caught unexpected signal %d in AIOSignalThread \n",
sig_num);
exit(-1);
if (info.si_code != SI_ASYNCIO){
fprintf(stderr, "ERROR: siginfo_t had si_code != SI_ASYNCIO, si_code = %d \n", info.si_code);
continue;
/* Write the stored pointer value in the pipe so that the main thread can process it */
if (write(aioSigFD[1], &(info.si_value.sival_ptr), sizeof(info.si_value.sival_ptr)) !=
sizeof(info.si_value.sival_ptr)) {
perror("Couldn't write the whole pointer");
exit(-1);
return (NULL);
static void
Init()
pthread_attr_t aioAttr;
pthread_t aioThread;
int retVal = 0;
/* Create a bidirectional pipe */
if (pipe(aioSigFD)) {
perror("pipe failed");
exit(-1);
/* Initialize to prevent other threads from being interrupted by
SIGPOLL */
sigemptyset(&aioSignalSet);
sigaddset(&aioSignalSet, SIGPOLL);
if ((retVal = pthread_sigmask(SIG_BLOCK, &aioSignalSet, NULL))) {
fprintf(stderr, "pthread_sigmask failed in Init\n");
exit(-1);
InitializeDisk();
if ((retVal = pthread_attr_init(&aioAttr)))
fprintf(stderr, "pthread_attr_init failed \n");
if ((retVal = pthread_attr_setdetachstate(&aioAttr, PTHREAD_CREATE_DETACHED)))
fprintf(stderr, "pthread_attr_setdetachstate failed \n");
if ((retVal = pthread_attr_setscope(&aioAttr, PTHREAD_SCOPE_SYSTEM)))
fprintf(stderr, "pthread_attr_setscope failed in \n");
if ((retVal = pthread_attr_setstacksize(&aioAttr, 2*1024*1024)))
fprintf(stderr, "pthread_attr_setstacksize failed \n");
if ((retVal = pthread_create(&aioThread, &aioAttr,
AIOSignalThread, NULL)))
fprintf(stderr, "pthread_create failed \n");
static void
UpdateDiskWriteInformation(DiskInfo *di)
di->di_currOffset += disk.bufferLen;
di->di_scheduled = 0;
static void
DiskOpCompleted(void *ptr)
DiskInfo di = (DiskInfo )ptr;
if (aio_error(&di->di_aiocb))
perror("aio_error");
if (aio_return(&di->di_aiocb) < 0)
perror("aio_return ");
UpdateDiskWriteInformation(di);
glob_respond++;
static void
LaunchDiskOperation(DiskInfo *di)
int res;
di->di_callout.func_ptr = DiskOpCompleted;
di->di_callout.data_ptr = di;
memset(&di->di_aiocb, 0, sizeof(di->di_aiocb));
di->di_aiocb.aio_fildes = disk.fd;
di->di_aiocb.aio_buf = disk.buffer;
di->di_aiocb.aio_nbytes = disk.bufferLen;
di->di_aiocb.aio_offset = di->di_currOffset;
di->di_scheduled = 1;
di->di_aiocb.aio_sigevent.sigev_notify = SIGEV_SIGNAL;
di->di_aiocb.aio_sigevent.sigev_signo = SIGPOLL;
di->di_aiocb.aio_sigevent.sigev_value.sival_ptr = &di->di_callout;
res = aio_write(&di->di_aiocb);
if (res == -1) {
perror("aio op error");
static void
HandleSignalResponses()
int fd;
#define DISKINFO_CALLOUT_MAX 64
DiskInfoCallOut* callout[DISKINFO_CALLOUT_MAX];
struct stat pipeStat;
int numCompleted;
int bytesToRead;
int sz;
int i;
fd = aioSigFD[0];
while (1) {
/* Find whether there is any data in the pipe */
if(-1 == fstat(fd, &pipeStat)) {
perror("fstat");
exit(-1);
if (pipeStat.st_size < sizeof(DiskInfoCallOut *))
break;
numCompleted = min((pipeStat.st_size/sizeof(DiskInfoCallOut *)),DISKINFO_CALLOUT_MAX);
bytesToRead = numCompleted * sizeof(DiskInfoCallOut *);
if ((sz = read(fd, callout, bytesToRead)) != bytesToRead) {
perror("Error reading from pipe");
exit(-1);
for (i = 0; i < numCompleted; i++)
(*callout[i]->func_ptr)(callout[i]->data_ptr);
int main(int argc, char *argv[])
DiskInfo *di;
FILE *logPtr1 = NULL;
FILE *logPtr2 = NULL;
FILE *logPtr3 = NULL;
struct rusage ru;
struct timeval t1, t2;
long timeTaken = 0;
int writeCount = 0;
int i;
char logFileName1[1024];
char logFileName2[1024];
char logFileName3[1024];
if (argc < 2) {
fprintf(stderr, "Usage : %s <partition_name> \n", argv[0]);
exit(-1);
strcat(rawDeviceName, argv[1]);
writeCount = 1;
printf("Partition selected = %s \n", rawDeviceName);
di = calloc(writeCount, sizeof(DiskInfo));
sprintf(logFileName1, "%s.log1", argv[0]);
if ((logPtr1 = fopen(logFileName1, "w+")) == NULL) {
fprintf(stderr, "Unable to create file test_pgm \n");
exit(-1);
sprintf(logFileName2, "%s.log2", argv[0]);
if ((logPtr2 = fopen(logFileName2, "w+")) == NULL) {
fprintf(stderr, "Unable to create file test_pgm \n");
exit(-1);
sprintf(logFileName3, "%s.log3", argv[0]);
if ((logPtr3 = fopen(logFileName3, "w+")) == NULL) {
fprintf(stderr, "Unable to create file test_pgm \n");
exit(-1);
Init();
for (i = 0; i < writeCount; i++) {
di.di_currOffset = (1 << 18) * (i + 1);
di[i].di_scheduled = 0;
gettimeofday(&t1, NULL);
while (1) {
int curScheduled = 0;
/* Schedule the disk operations */
for (i = 0; i < writeCount; i++) {
if (di[i].di_scheduled == 0) {
LaunchDiskOperation(&di[i]);
glob_scheduled++;
curScheduled++;
/* Handle the responses */
HandleSignalResponses();
if ((curScheduled) && (glob_respond % DISPLAY_COUNT == 0)) {
gettimeofday(&t2, NULL);
timeTaken = ((t2.tv_sec * 1000000 + t2.tv_usec) -
(t1.tv_sec * 1000000 + t1.tv_usec))/1000;
printf("Scheduled = %d, Responded = %d, Time Taken = %ld ms \n",
glob_scheduled, glob_respond, timeTaken);
fprintf(logPtr1, "Scheduled = %d, Responded = %d, Time Taken = %ld ms \n",
glob_scheduled, glob_respond, timeTaken);
fprintf(stderr,"wrote to logPtr1 ..\n");
fprintf(logPtr2, "Scheduled = %d, Responded = %d, Time Taken = %ld ms \n",
glob_scheduled, glob_respond, timeTaken);
fprintf(stderr,"wrote to logPtr2 ..\n");
fprintf(logPtr3, "Scheduled = %d, Responded = %d, Time Taken = %ld ms \n",
glob_scheduled, glob_respond, timeTaken);
fprintf(stderr,"wrote to logPtr3 ..\n");
t1 = t2;

Hi @cooldog ,
I hit this same LVM2 snapshot kernel oops on several Oracle Linux 6.5 servers running UEK R3 kernel version 3.8.13-16.3.1. I have Linux Premier Support so I opened a Service Request. Oracle Support got back to me with the following notes.
Hello Matt,
Bug 17487738 : EXT4: STRESS TESTING WITH SUSPEND/RESUME FS ACCESS CAUSES FS ERRORS This bug is fixed in kernel version: 3.8.13-18. This kernel will be available quite soon for download.
You may upgrade the kernel once its available. ~Siju
Update
Dear Matt, Latest available UEK3 kernel version 'kernel-uek-3.8.13-26.el6uek.x86_64' incorporates the required bugfix. [root@server1 tmp]# rpm -q --changelog -p kernel-uek-3.8.13-26.el6uek.x86_64.rpm | grep -i 17487738
warning: kernel-uek-3.8.13-26.el6uek.x86_64.rpm: Header V3 RSA/SHA256 signature: NOKEY, key ID ec551f03
- fs: protect write with sb_start/end_write in generic_file_write_iter (Guangyu Sun) [Orabug: 17487738] <<<<<<======================================== You can download the UEK3 kernel from ULN or from public-yum repo.
http://public-yum.oracle.com/repo/OracleLinux/OL6/UEKR3/latest/x86_64/getPackage/kernel-uek-firmware-3.8.13-26.el6uek.noarch.rpm
http://public-yum.oracle.com/repo/OracleLinux/OL6/UEKR3/latest/x86_64/getPackage/kernel-uek-3.8.13-26.el6uek.x86_64.rpm Hope this helps! ~Siju
Subscribe to the Oracle Linux el-errata mailing list .
The latest kernel-uek-3.8.13-26.el6uek.x86_64 version fixed the problem.
- Matt

Internal application error in scheduling a dis file.

Hi friends , i am finding a problem in scheduling a dis file . discoverer says internal application error. some other files are getting scheduled. the query for this particaular report is long. any suggestions , its urgent.................. discoverer version is 4.1 .

Hi,
Not really enough informatoin to debug via a forum, you may need a Service Request with Oracle Support. If staying on 4.1 (recommend 10.1.2.0.2), I suggest you are patched to 4.1.48.08
Additionally, ensure the worksheet runs to completion without scheduling... since you mentioned it is long you may need to increase the data cache, etc.
Regards,
Steve

Rwrun.exe - Application Error while running Concurrent Requests in R12(Win)

Hi Gurus,
I am getting the Rwrun.exe Application error, whenever i am running a concurrent request. The thing, that i feel is: Probably, The concurrent requests that has the output file associated with them are the one that are running into error.
The following is the description of the error popup:
rwrun.exe - Application Error
The instruction at "0x663ed168" referenced memory at "0x00000004". The memory could not be "read".
Click OK to terminate the program.
Click CANCEL to debug the program.
Due to this, am not able to submit any of the Reports.
Details of My installation:
Apps Version: Release 12
Platform: Windows XP SP2
Installed on: External HDD of 250GB
Addon Patches after install: None.
Has anybody faced this problem earlier?
Please help me out gurus..
Thanks in advance.
Regards,
Ajit

Check the Event Viewer to see if there is more information about the error that can help.

Using LabVIEW 6.0.1 in Win2K, I get the Application Error: The instruction at "0x004be060" referenced memory at "0x00000001". The memory could not be "read".

I have several VIs that use the same typedef. This "super" typedef consists of of a cluster containing 6 arrays. Each array has elements that are themselves typedefs. The array element typedefs consist of a cluster of strings, a string array, and yet another cluster typedef of instrument handles. The total number of unique typedefs is 13 (1 super, 1 as the array element in the 6 arrays, and 1 in each array element).
When I make any changes to any of these typedefs and I try to open a VI that uses the "super" typedef, LabVIEW stops loading subVIs and crashes with the Application Error: Application Error: The inst
ruction at "0x004be060" referenced memory at "0x00000001". The memory could not be "read". Also note that this VI contains several subVIs that use this "super" typedef for terminal inputs and outputs.
What is causing this problem? My only solution to this is to rename the "super" typedef, open the VI, ignoring the load of the "super" typedef, and once the VI opens (with a broken arrow) relinking the VI to the typdef after renaming the typedef back to the original name. This becomes quite painful when you have to do this for each and every VI that uses this typedef on every revision of the typedef.

You might want to first install the 6.0.2 patch before digging too far into this. You can download it from the ftp site:
ftp://ftp.ni.com/support/labview/windows/updates/6.0.2/
If the problem remains, then it is likely related to a few known issues with strict type defs. Unfortunately, there is not much that can be done about it at the present time. You might try having the *.ctl file open in the editor when you open the VIs to see if that helps.

BUG! Not system locale Filenames support for 32-bit applications error in Windows 8.1 x64 and other microssoft x64 OS-s.

BUG! Not system locale Filenames support for 32-bit applications error in Windows 8.1 x64.
All Windows x64 (XP,2003,2007,Vista,7,8) have no support for not system locale filenames|foldernames for all 32-bit applications. I think it is BUG!
For example, it is possible to read files|folders with French or Chinese in English locale windows installed, rename it, but it is not possible open it, edit or delete. (ERRORS: File not found OR Unknown format)
With using 64-bit programs no such problems. How does it works and how can I fix this? Is it problem with encoding in translating kernel instructions for 32-bit apps in x64 Windows OS's? Whether there are
solutions to this problem OR some hacks|fixes?

Hi,
Have you installed the language package for French or Chinese?
If no, please download the language package and install them.
To download language package, please click the link below,
http://windows.microsoft.com/en-US/windows/language-packs#lptabs=win7
Best Regards.
Steven Lee
TechNet Community Support

ABAP and Kernel Patches for Upgrade and Conversion in 4.6C

Hi,
We are in a process of upgrade and unicode conversion for the source release 4.6C (Kernel 46D_EXT Patch 2225).
"Combined Upgrade&Unicode Conversion Guide" for "SAP Basis 4.6C u2192 SAP NetWeaver 7.0 application Server ABAP Unicode Including Enhancement Package 1 Support Package 01 - 06" , In Software Requirements step, it says
"3. Import 4.6D Kernel patch 2326 from SAP Service Marketplace according to SAP Note 19466"
We wanted to know whether "IT IS ABSOLUTELY NECCESSARY TO GO FOR THE KERNEL PATCH 2326". We dont have "EBCIDIC code pages" in our MDMP system.
We need to know becauase we are also doing OS migration from AIX to Sun and this step will add to our production downtime.
Please advice what are the other causes we should go for the kernel 2326.
Regards

Hello Mr. Nils Buerckel,
Thanks for the reply.
We wanted to be very sure whether we should used Kernel 46D Kernel patch 2326 (As it is specifically mentioned in the SAP CU&UC guide and in SAP Note 867193, It is mentioned that "This patch contains enhancements that are required to execute the "INDX Analysis" scan)
OR
Can we go for the latest kernel patch avaialable at market place? And Will the latest kernel patch also contains the "enhancements that are required to execute the "INDX Analysis" ?
Please reply
Thanks

10.4.9 Upgrade: Fails. Reboot results in Kernel Panic ACPI error

I am upgrading 11 MacBook Pros 10.4.6 to 10.4.9. Becasue they are all on a slow Wifi I am using the manual updates via a thumb drive.
So far 2 out of 6 have failed the install process. One gave me a general error. I tried to re-run the program but when I did the font for the drop down menu turned into all boxes with capital As inside them. In both cases when I have rebooted I have gotten a Kernel Panic ACPI error. I have tried all the Kernel Panic tricks mentioned in the 10.4.9 threads. I am now reinstalling on the two machines.
1 of 6 did the install just fine but is now stopped on the "Starting Mac OS X..." screen with a full blue bar.
Does anyone have any idea what is wrong?

You may find the following useful:
From a recent article at MacFixit:
Mac OS X 10.4.9 Special Report: Update procedure recommendation
First, make a full backup of your current Mac OS X installation -- preferably a clone ( try SuperDuper! or Carbon Copy Cloner). If something goes wrong, or you experience a major incompatibility after updating, the backup will prove invaluable.
Next, if you are the cautious type, run a disk repair on the volume targeted for installation. You can use an n alternative startup drive or your Mac OS X installation disc. If you are starting up from your Mac OS X install disc, put the disc in your optical drive and restart holding down the "C" key. After your system starts up and you've selected your language, go to the "Utilties" menu and select "Disk Utility." Use the "Repair Disk" function. After disk repairs are complete, restart from your normal startup drive and continue.
Avoid performing any other operations (in Mac OS X or third-party applications) while the update process is occurring.
Performing other tasks during the update process potentiates various issues, including problems with prebinding (which is happening during the "Optimizing the system" phase of the update process) and others that can occur when files are being replaced by the update are also being read/written by the currently logged in user. You should not only refrain from launching applications or working with files during the update process, but also from putting the system to sleep, disconnecting/connecting devices, and other potentially interruptive actions.
In addition, before installing the update, make sure all Apple-installed applications and utilities are in their original locations. Moving one of these applications to a different location on your hard drive can lead to an incomplete update. Also, disconnect any FireWire/USB devices before applying Mac OS X 10.4.9 (except for your startup drive, if it is FireWire or USB, and your keyboard/mouse), then re-connect the devices one by one (checking for issues created by any particular device) after the update process is complete and the system has restarted. Also, note that the first restart after applying Mac OS X 10.4.9 may be abnormally long. Subsequent restarts should take place at normal speed.
And this further article from MacFixit is also very important:
When a Mac OS X update won't install with "Volume does not meet requirements for this update" message
The error message "Volume does not meet requirements for this update" may appear when attempting to install a Mac OS X updater or a full release from disc. Generally the problem falls into one of the following categories:
Make sure you are using the right updater (Server vs. client) There are usually a few varieties of the same Mac OS X update version. Make sure that you are not trying to install the Intel client build on a PowerPC-based Mac, or the Server build on a Mac OS X client system.
Although we generally recommend using the standalone Mac OS X updaters rather than Software Update, the latter method will generally correctly identify the copy of Mac OS X applicable to your current system state.
Retail vs. shipped-with-system (build numbers) Different Macs ship with different builds of Mac OS X, and one build may not be compatible with a different system. The build that ships with a MacBook Core 2 Duo, for instance, may not properly install on a Mac Pro. Hence you may receive the "Volume does not meet requirements for this update" message when mixing and matching systems and discs.
Some retail copies of Mac OS X 10.4.x may also be unable to install on some systems that require newer builds.
In addition, it appears that while some builds will install on specific systems, those systems will then refuse to accept subsequent updates. To ensure compatibility, inspect the following matrices:
• Mac OS: Versions, builds included with Intel-based Macs
http://docs.info.apple.com/article.html?artnum=303315
• Mac OS: Versions, builds included with PowerPC Macs (since 1998)
http://docs.info.apple.com/article.html?artnum=25517
and note that you should not use a Mac OS version earlier than the one included with the computer.
Combo vs. Delta Remember that delta Mac OS X updaters can only update systems version-to-version, e.g. Mac OS X 10.4.8 to Mac OS X 10.4.9. Combo updaters can bring any version within the scope of a major release (Panther, Tiger, etc.) up-to-date, e.g. Mac OS X 10.4.3 to Mac OS X 10.4.9.
Attempting to run a delta update on anything other than the directly precedent version may result in the "Volume does not meet requirements for this update" message.

Firefox.exe +application error +the application failed to initialize properly (0x0150004) +click on OK to terminate the application.

Win XP Home SP2
Installed Firefox, but receive the following error message:
firefox.exe +application error +the application failed to initialize properly (0x0150004) +click on OK to terminate the application.
Have uninstalled and reinstalled several times, but same message. Firefox won't even open.

Usually someone has been down the track before and occasionally they post some useful details which may help others to investigate and/or eliminate factors in their particular case.
This AccessibleMarshal.dll error seems to have a long history --- posts from 2006 with early Firefox versions had issues similar to yours.
There is a link and an excerpt below which could be worth checking in your case,
particularly since it mentions the problem would occur on a clean install (no previous instance of Firefox on the system and Windows before Vista --??)
Have a look here:
https://bugzilla.mozilla.org/show_bug.cgi?id=712960
and the post to read:
'''Mark Banner (:standard8) 2011-12-22 12:55:21 PST'''
"Created attachment 583905 [details] [diff] [review]
Add the Win32 redistributable directory to the mozconfigs"
"Somehow we missed shipping the Win32 Redistributables from Visual C++. We didn't detect this as it would only show on Windows versions less than Vista, and you'd probably only see it if you had a completely clean install, and you didn't have the dlls installed elsewhere (as it appears my XP system does)."
"If you're seeing this then you want to copy the following files from a Firefox installation:
Microsoft.VC80.CRT.manifest
msvcm80.dll
msvcp80.dll
msvcr80.dll
The patch I'm attaching updates our configuration files to specify the Win32 redistribution directory, which will then cause the build system to include the files in the build."
.... ends....
The earlier 2006 instances also had the same issue in some cases:
forums.frontmotion.com/viewtopic.php?f=10&t=393
Hope this progresses the search and resolution.
Cheers

Custom JCA Adapter / Application Error - Message.setErrorInfo() ??

Hi All,
I was looking for how to create a sensible Application Error in a custom JCA adapter and was excited to find the following page in the PCK info on Adapter Development:
http://help.sap.com/saphelp_nw04/helpdata/en/3c/53d6409ff68631e10000000a1550b0/frameset.htm
The part of interest being:

The following methods are available to enable you to read error information in the form of an ErrorInfo object from the message, or to set the error information in a message.
Message.getErrorInfo()
Message.setErrorInfo()
If the synchronous response message is an application-error message instead of an application response, it must call setErrorInfo(myErrorInfo) for receiver adapters.
However, I can't find these methods, or indeed the "ErrorInfo" object anywhere in the AF classes - does anyone know it's whereabouts? Or is the above page just out of date? If so, what is the new approach for creating Application Level Errors in a custom JCA Resource adapter (not Exceptions - I can do that)
Many thanks,
Chris

Well, you can get the latest jars from the SMP (Service Marketplace) directly. These jars are in the XI ADAPTER FRAMEWORK CORE 3.0 component. Basically, http://service.sap.com/swdc then Support Packages and Patches->SAP NetWeaver->SAP NETWEAVER->SAP NETWEAVER 04->Entry by Component->J2EE Adapter Engine (PI/XI). There you'll see the XI ADAPTER FRAMEWORK CORE 3.0 link.
OR here is the direct link for the SP19 (latest) of <a href="https://smpdl.sap-ag.de/~swdc/012002523100009492712006D/SAPXIAFC19P_4-20000272.sca?_ACTION=DL_DIRECT">SAPXIAFC19P_4-20000272.sca</a>
Within this is aii_af_lib.sda which has the jars. You can use winzip or winrar to open .sca, .sda files.
Regards,
Jin

Kernel patches application error

Similar Messages

Maybe you are looking for