Xa_open - failed

145010.STINGRAY-32!TMS_QM.1608.1604.0: Q_CAT:1350: ERROR: xa_open - failed to open table QSPACE.00 on config C:\samplesTuxedo\qsample\QUE
What can be the reason for this error?

Peter,
the errno value is 22
thanks
Vipul.
Peter Holditch <[email protected]> wrote:
vipul,
What errno value did you get when you saw this message?
Regards,
Peter.
vipul wrote:
Hi,
I am getting the following error when I try to create a Q Space withnumber of
messages in it as 5,00,000. But if I try the same for 4,00,000 messages,it is
successful.
I checked the Shared memory in the machine and it is much more thanit is required
for 5,00,000 messages Q Space.
Do I need to tune any other operating system parameter ?
1494 ERROR: xa_open() - failed to get shared memory, key = key, errno= errno
Description
While opening the queue space, xa_open() was unable to get the necessaryshared
memory. The error number, errno, is printed in the message.
Action
This failure can be caused by a number of reasons but the most likelyis that
either the amount of shared memory requested would cause an operatingsystem tunable
to be exceeded (shared memory for the system or shared memory identifiers),or
another application is using the same key. Determine and correct theproblem.
Thanks
Vipul

Similar Messages

1494 ERROR: xa_open() - failed to get shared memory

Hi,
I am getting the following error when I try to create a Q Space with number of
messages in it as 5,00,000. But if I try the same for 4,00,000 messages, it is
successful.
I checked the Shared memory in the machine and it is much more than it is required
for 5,00,000 messages Q Space.
Do I need to tune any other operating system parameter ?
1494 ERROR: xa_open() - failed to get shared memory, key = key, errno = errno
Description
While opening the queue space, xa_open() was unable to get the necessary shared
memory. The error number, errno, is printed in the message.
Action
This failure can be caused by a number of reasons but the most likely is that
either the amount of shared memory requested would cause an operating system tunable
to be exceeded (shared memory for the system or shared memory identifiers), or
another application is using the same key. Determine and correct the problem.
Thanks
Vipul

Peter,
the errno value is 22
thanks
Vipul.
Peter Holditch <[email protected]> wrote:
vipul,
What errno value did you get when you saw this message?
Regards,
Peter.
vipul wrote:
Hi,
I am getting the following error when I try to create a Q Space withnumber of
messages in it as 5,00,000. But if I try the same for 4,00,000 messages,it is
successful.
I checked the Shared memory in the machine and it is much more thanit is required
for 5,00,000 messages Q Space.
Do I need to tune any other operating system parameter ?
1494 ERROR: xa_open() - failed to get shared memory, key = key, errno= errno
Description
While opening the queue space, xa_open() was unable to get the necessaryshared
memory. The error number, errno, is printed in the message.
Action
This failure can be caused by a number of reasons but the most likelyis that
either the amount of shared memory requested would cause an operatingsystem tunable
to be exceeded (shared memory for the system or shared memory identifiers),or
another application is using the same key. Determine and correct theproblem.
Thanks
Vipul

Q_CAT:1494: ERROR: xa_open() - failed to get shared memory

I am getting this error while booting tuxedo.
My question is how do I calculate shared memory on solaris and then which parameter to increase in /etc/system file.
Thanks

Vaibhav,
You need to make sure that the product of SHMMAX and SHMSEG is at least
equal to the total amount of shared memory needed by Tuxedo and any other
applications running on your machine.
"tmboot -c" will tell you the amount of shared memory required for the
Tuxedo bulletin board, but this does not include any space required by /Q.
To get /Q shared memory requirements, you can use the qmadmin subcommand
"qspacelist". If you have more than one queuespace on your system, you must
do this for each queuespace on your system, and add this total to the
bulletin board requirements. If any other applications on your machine use
shared memory, add their requirements as well. In case requirements change
in the future, it is good to add a comfortable amount of padding to this
sum.
Ed
<Vaibhav Gaur> wrote in message news:[email protected]..
I am getting this error while booting tuxedo.
My question is how do I calculate shared memory on solaris and then which
parameter to increase in /etc/system file.
Thanks

Qsample example failing with Q_CAT:1495: ERROR: xa_open()

I'm trying to run qsample example coming with evaluation tuxedo 8.0 for solaris
8.
It fails in the qmadmin tool when trying to call "qopen QSPACE".
The user log file has recorded error line "Q_CAT:1495: ERROR: xa_open() - failed
to attach to shared memory, key = 62839, errno = 22".
Truss utility shows this:
<<<<<<<<<<<<<<<<<<<<<<<<<
semget(62839, 1, 0) = 786432
semop(786432, 0xFFBEE0BC, 1) = 0
shmget(62839, 0, 0) = 24576
shmctl(24576, 12, 0xFFBEE058) = 0
shmat(24576, 0, 0) = 0xFD800000
shmdt(0xFD800000) = 0
shmget(62839, 94417, 0) = 24576
open("/dev/zero", O_RDONLY) = 4
mmap(0x00000000, 1048576, PROT_READ, MAP_PRIVATE, 4, 0) = 0xFE280000
close(4) = 0
munmap(0xFE280000, 1048576) = 0
shmat(24576, 0xFE280000, 0) Err#22 EINVAL
.and /etc/system has:
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmin=1
set shmsys:share_page_table=1
set msgsys:msginfo_msgmap = 1026
set msgsys:msginfo_msgmax = 4096
set msgsys:msginfo_msgmnb = 4096
set msgsys:msginfo_msgmni = 50
set msgsys:msginfo_msgssz = 8
set msgsys:msginfo_msgtql = 1024
set msgsys:msginfo_msgseg = 2048
** IPC-semsys
set semsys:seminfo_semmap = 1026
set semsys:seminfo_semmni = 3072
set semsys:seminfo_semmns = 32768
set semsys:seminfo_semmnu = 2048
set semsys:seminfo_semmsl = 128
set semsys:seminfo_semopm = 128
set semsys:seminfo_semume = 256
set semsys:seminfo_semvmx = 32767
set semsys:seminfo_semaem = 16384
** IPC-shmsys
set shmsys:shminfo_shmmni = 3072
set shmsys:shminfo_shmseg = 1024
The box we are tryimg it on is a big SunFire 6800 server
with 16 GB RAM and 8 CPUs and also has Oracle installed on it
so all shared memory setting are quite high.
Could anyone tell me where we are doing wrong. Thanking you in advance.

Thank you, Scott
Actually I've found the problem already. It was in the /etc/system file we had
settings shmsys:share_page_table=1, and that caused ISM to function differently
so, particularly calls to shmat() with supplying your own map address (and what
Tuxedo does) would fail. Removing this setting fixed the problem.
Scott Orshan <[email protected]> wrote:
George,
I tried qsample on Tux 8/Solaris 8, and it worked for me. I think that
Support should take a look at it. You can have them check with me, and
I'll show them where in the code this error comes from.
Scott Orshan
George wrote:
I'm trying to run qsample example coming with evaluation tuxedo 8.0for solaris
8.
It fails in the qmadmin tool when trying to call "qopen QSPACE".
The user log file has recorded error line "Q_CAT:1495: ERROR: xa_open()- failed
to attach to shared memory, key = 62839, errno = 22".
Truss utility shows this:
<<<<<<<<<<<<<<<<<<<<<<<<<
semget(62839, 1, 0) = 786432
semop(786432, 0xFFBEE0BC, 1) = 0
shmget(62839, 0, 0) = 24576
shmctl(24576, 12, 0xFFBEE058) = 0
shmat(24576, 0, 0) = 0xFD800000
shmdt(0xFD800000) = 0
shmget(62839, 94417, 0) = 24576
open("/dev/zero", O_RDONLY) = 4
mmap(0x00000000, 1048576, PROT_READ, MAP_PRIVATE, 4, 0) = 0xFE280000
close(4) = 0
munmap(0xFE280000, 1048576) = 0
shmat(24576, 0xFE280000, 0) Err#22 EINVAL

HELP: qspacecreate ERROR

APPDIR=/usr/server/bin
qmadmin ${APPDIR}/QUE <<!
crdl ${APPDIR}/QUE 0 2000
echo
qspacecreate
QSPACE
62839
1000
300
5
5
30000
errque
n
16
qopen QSPACE
ERROR INFO?Q_CAT:1241: ERROR: Failed to open queue space QSPACE on config
ulog:
07-05-2007: Tuxedo Version 8.0
Q_CAT:1495: ERROR: xa_open() - failed to attach to shared memory, key = 62839, errno = 22
Edited by twxy123 at 07/05/2007 2:18 AM

This appears to be an IPC sizing problem. The values reported by
"tmboot -c" are only for the transaction monitor portion of Tuxedo and do
not include any IPC resources needed by resource managers such as /Q,
Oracle, MQSeries, DB2, Informix, etc. The resource manager IPC
requirements must be added to the transaction monitor IPC requirements and
the requirements of any other applications on the system.
One way to determine the IPC requirements for /Q is to set QMCONFIG and open
the queue space using qmadmin without booting Tuxedo. The qmadmin "ipcs"
command will list the IPC resources used by the queue. 'ipcs -a|egrep
"KEY|$LOGNAME"' is also very useful in pinpointing IPC resources used by the
Tuxedo login ID.
Hopefully this will help you in determining the total IPC resources needed
for your system.
Ed
<qiu jh> wrote in message news:[email protected]..
sysctl -p
net.ipv4.ip_forward = 1
net.ipv4.conf.all.rp_filter = 1
kernel.sysrq = 0
kernel.shmmax = 3865470566
kernel.shmmni = 4096
kernel.shmall = 2097152
kernel.msgmax = 8192
kernel.msgmnb = 16384
kernel.msgmni = 1024
kernel.sem = 500 64000 64 512
fs.file-max = 32768
vm.bdflush = 60 64 64 256 500 3000 60 0 0
tmboot -cy
Ipc sizing (minimum /T values only) ...
Fixed Minimums Per Processor
SHMMIN: 1
SHMALL: 1
SEMMAP: SEMMNI
Variable Minimums Per Processor
SEMUME, A
SHMMAX
SEMMNU, * *
Node SEMMNS SEMMSL SEMMSL SEMMNI MSGMNI MSGMAP
SHMSEG
qgzx 325 40 320 A + 1 231 462
1231K
where 1 <= A <= 8.
The number of expected application clients per processor should
be added to each MSGMNI value.
if the 'messages' set 20000 OK

Oracle RM failing to connect: ORA-12545

Hi,
I am trying to run my application which uses Oracle client 8.0.6 on NCR MPRAS.
I am connecting to DB version. 8.1.7 running on Solaris box
Following are working fine for me which means there is no problem with TNSNAMES.ORA:
1) TNSPING
2) SQLPLUS
3) Applications using embedded SQL calls
But my recent application which uses the Resource Manager ORACLE_XA is failing at xa_open call. It give the error ora-12545.
Am I missing something here? Please help.
Vikram

I don't know Crystal Reports and what it sends to and requests from the database, but that's the formal description of this error:
Error: ORA 8001
Text: maximum number of sequences per session exceeded
Cause: An operation requested a resource that was unavailable.
The maximum number of user sequences per session is specified by the
initialization parameter DC_SEQUENCES.
When this maximum is reached, no more requests are processed.
Action: Try the operation again in a few minutes.
If this error occurs often, shut down Oracle, increase the
DC_SEQUENCES parameter in the initialization parameter file, and
restart Oracle.

Tpopen TPERMERR xa_open returned XAER_RMERR

Trouble during tmboot phase of servers...
Resource management of the database extensions are failing even though the correct
settings (ie. database name, user name/password, and TMS resource/TMSUDB2) are
stated in the tuxedo configuration file. Receive a "CMDTUX_CAT:825" notifying
that the resource did not activate but nothing more (how can the level of debug
information be increased? major problem with tmadmin and debugging).
Also, just prior to tmboot running through the list of groups/servers to boot
an error message related to TMSUDB2 is logged: "LIBTUX_CAT:466: ERROR: tpopen
TPERMERR xa_open returned XAER_RMERR." And the tpsvrinit() fails.
Attached is the ULOG log. I would love some help in learning how to debug resource
errors. I am not educated as a tuxedo sys admin. only a developer.
mvh - Matthew Young
[ULOG.081502]

Matthew,
are you sure the entries in the udataobj/RM file
are correct ?
Peter Holditch <[email protected]> wrote:
Matthew,
You don't need a Tuxedo administrator, you need a database administrator!
Your Tuxedo server calls tpopen() or tx_open(). This in turn calls xa_open()
passing the OPENINFO string you configured for the server group. The
xa_open
function itself is implemented by the database.
XAER_RMERR is the mechanism prescribed by the xa specification for the
RM to
report "I have failed" Tuxedo is passing that information back to you.
You need to use whatever database debugging facilities you have available
to
determine why the database's xa_open routine failed. With Oracle,
you can
enable xa tracing with the OPENINFO. WIth UDB, I have no idea what diagnostics
are available.
I hope that helps!
Peter.
Matthew Young wrote:
Trouble during tmboot phase of servers...
Resource management of the database extensions are failing even thoughthe correct
settings (ie. database name, user name/password, and TMS resource/TMSUDB2)are
stated in the tuxedo configuration file. Receive a "CMDTUX_CAT:825"notifying
that the resource did not activate but nothing more (how can the levelof debug
information be increased? major problem with tmadmin and debugging).
Also, just prior to tmboot running through the list of groups/serversto boot
an error message related to TMSUDB2 is logged: "LIBTUX_CAT:466: ERROR:tpopen
TPERMERR xa_open returned XAER_RMERR." And the tpsvrinit() fails.
Attached is the ULOG log. I would love some help in learning how todebug resource
errors. I am not educated as a tuxedo sys admin. only a developer.
mvh - Matthew Young
143625.W40006071!BBL.645: 081502: TUXEDO Version 6.4 32-bit Windows.
143625.W40006071!BBL.645: LIBTUX_CAT:262: INFO: Standard main starting
143629.W40006071!TMS.616: 081502: TUXEDO Version 6.4 32-bit Windows.
143629.W40006071!TMS.616: LIBTUX_CAT:262: INFO: Standard main starting
143629.W40006071!TMS.639: 081502: TUXEDO Version 6.4 32-bit Windows.
143629.W40006071!TMS.639: LIBTUX_CAT:262: INFO: Standard main starting
143629.W40006071!TMS.471: 081502: TUXEDO Version 6.4 32-bit Windows.
143629.W40006071!TMS.471: LIBTUX_CAT:262: INFO: Standard main starting
143629.W40006071!TMS.630: 081502: TUXEDO Version 6.4 32-bit Windows.
143629.W40006071!TMS.630: LIBTUX_CAT:262: INFO: Standard main starting
143629.W40006071!TMS.515: 081502: TUXEDO Version 6.4 32-bit Windows.
143629.W40006071!TMS.515: LIBTUX_CAT:262: INFO: Standard main starting
143629.W40006071!TMS.359: 081502: TUXEDO Version 6.4 32-bit Windows.
143629.W40006071!TMS.359: LIBTUX_CAT:262: INFO: Standard main starting
143630.W40006071!TMSUDB2.643: 081502: TUXEDO Version 6.4 32-bit Windows.
143630.W40006071!TMSUDB2.643: LIBTUX_CAT:262: INFO: Standard main starting
143630.W40006071!TMSUDB2.643: LIBTUX_CAT:466: ERROR: tpopen TPERMERRxa_open returned XAER_RMERR
143630.W40006071!TMSUDB2.643: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
143630.W40006071!tmboot.478: 081502: TUXEDO Version 6.4 32-bit Windows.
143630.W40006071!tmboot.478: CMDTUX_CAT:825: ERROR: Process TMSUDB2at LOCALPC failed with /T tperrno (TPERMERR - resource manager error)
143630.W40006071!TMSUDB2.531: 081502: TUXEDO Version 6.4 32-bit Windows.
143630.W40006071!TMSUDB2.531: LIBTUX_CAT:262: INFO: Standard main starting
143630.W40006071!TMSUDB2.531: LIBTUX_CAT:466: ERROR: tpopen TPERMERRxa_open returned XAER_RMERR
143630.W40006071!TMSUDB2.531: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
143630.W40006071!tmboot.478: CMDTUX_CAT:825: ERROR: Process TMSUDB2at LOCALPC failed with /T tperrno (TPERMERR - resource manager error)
143630.W40006071!TMSUDB2.341: 081502: TUXEDO Version 6.4 32-bit Windows.
143630.W40006071!TMSUDB2.341: LIBTUX_CAT:262: INFO: Standard main starting
143630.W40006071!TMSUDB2.341: LIBTUX_CAT:466: ERROR: tpopen TPERMERRxa_open returned XAER_RMERR
143630.W40006071!TMSUDB2.341: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
143630.W40006071!tmboot.478: CMDTUX_CAT:825: ERROR: Process TMSUDB2at LOCALPC failed with /T tperrno (TPERMERR - resource manager error)
143630.W40006071!TMSUDB2.427: 081502: TUXEDO Version 6.4 32-bit Windows.
143630.W40006071!TMSUDB2.427: LIBTUX_CAT:262: INFO: Standard main starting
143630.W40006071!TMSUDB2.427: LIBTUX_CAT:466: ERROR: tpopen TPERMERRxa_open returned XAER_RMERR
143630.W40006071!TMSUDB2.427: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
143630.W40006071!tmboot.478: CMDTUX_CAT:825: ERROR: Process TMSUDB2at LOCALPC failed with /T tperrno (TPERMERR - resource manager error)
143631.W40006071!DMADM.474: 081502: TUXEDO Version 6.4 32-bit Windows.
143631.W40006071!DMADM.474: LIBTUX_CAT:262: INFO: Standard main starting
143631.W40006071!DMADM.474: CMDGW_CAT:3149: INFO: BDMCONFIG environmentvariable not set. Using $APPDIR/BDMCONFIG
143631.W40006071!GWADM.596: 081502: TUXEDO Version 6.4 32-bit Windows.
143631.W40006071!GWADM.596: LIBTUX_CAT:262: INFO: Standard main starting
143631.W40006071!DMADM.474: CMDGW_CAT:3142: ERROR: Cannot send configto GWADM group=DOM_GW
143631.W40006071!GWADM.596: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
143631.W40006071!tmboot.478: CMDTUX_CAT:825: ERROR: Process GWADM atLOCALPC failed with /T tperrno (TPESVCFAIL - application level service
failure)
143631.W40006071!TMS.467: 081502: TUXEDO Version 6.4 32-bit Windows.
143631.W40006071!TMS.467: LIBTUX_CAT:262: INFO: Standard main starting
143631.W40006071!TMS.406: 081502: TUXEDO Version 6.4 32-bit Windows.
143631.W40006071!TMS.406: LIBTUX_CAT:262: INFO: Standard main starting
143632.W40006071!meddelandeadmv.603: 081502: TUXEDO Version 6.4 32-bitWindows.
143632.W40006071!meddelandeadmv.603: LIBTUX_CAT:262: INFO: Standardmain starting
143632.W40006071!TMSUDB2.429: 081502: TUXEDO Version 6.4 32-bit Windows.
143632.W40006071!TMSUDB2.429: LIBTUX_CAT:262: INFO: Standard main starting
143632.W40006071!TMSUDB2.429: LIBTUX_CAT:466: ERROR: tpopen TPERMERRxa_open returned XAER_RMERR
143632.W40006071!TMSUDB2.429: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
143632.W40006071!tmboot.478: CMDTUX_CAT:825: ERROR: Process TMSUDB2at LOCALPC failed with /T tperrno (TPERMERR - resource manager error)
143632.W40006071!TMSUDB2.435: 081502: TUXEDO Version 6.4 32-bit Windows.
143632.W40006071!TMSUDB2.435: LIBTUX_CAT:262: INFO: Standard main starting
143632.W40006071!TMSUDB2.435: LIBTUX_CAT:466: ERROR: tpopen TPERMERRxa_open returned XAER_RMERR
143632.W40006071!TMSUDB2.435: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
143632.W40006071!tmboot.478: CMDTUX_CAT:825: ERROR: Process TMSUDB2at LOCALPC failed with /T tperrno (TPERMERR - resource manager error)
143633.W40006071!sakerhet.425: 081502: TUXEDO Version 6.4 32-bit Windows.
143633.W40006071!sakerhet.425: LIBTUX_CAT:262: INFO: Standard mainstarting
143633.W40006071!sakerhet.425: LIBTUX_CAT:466: ERROR: tpopen TPERMERRxa_open returned XAER_RMERR
143634.W40006071!meddelandeadmi.397: 081502: TUXEDO Version 6.4 32-bitWindows.
143634.W40006071!meddelandeadmi.397: LIBTUX_CAT:262: INFO: Standardmain starting
143634.W40006071!meddelandeadmi.397: LIBTUX_CAT:466: ERROR: tpopenTPERMERR xa_open returned XAER_RMERR
143634.W40006071!fellogg.477: 081502: TUXEDO Version 6.4 32-bit Windows.
143634.W40006071!fellogg.477: LIBTUX_CAT:262: INFO: Standard main starting
143634.W40006071!fellogg.477: LIBTUX_CAT:466: ERROR: tpopen TPERMERRxa_open returned XAER_RMERR
143634.W40006071!meddelandeinfo.465: 081502: TUXEDO Version 6.4 32-bitWindows.
143634.W40006071!meddelandeinfo.465: LIBTUX_CAT:262: INFO: Standardmain starting
143634.W40006071!meddelandeinfo.465: LIBTUX_CAT:466: ERROR: tpopenTPERMERR xa_open returned XAER_RMERR
143834.W40006071!TMS.406: CMDTUX_CAT:457: INFO: TMS tpsvrdone complete
143834.W40006071!TMS.467: CMDTUX_CAT:457: INFO: TMS tpsvrdone complete
143834.W40006071!DMADM.474: CMDGW_CAT:1655: INFO: DMADMSVR is exiting
143834.W40006071!TMS.359: CMDTUX_CAT:457: INFO: TMS tpsvrdone complete
143834.W40006071!TMS.515: CMDTUX_CAT:457: INFO: TMS tpsvrdone complete
143834.W40006071!TMS.630: CMDTUX_CAT:457: INFO: TMS tpsvrdone complete
143834.W40006071!TMS.471: CMDTUX_CAT:457: INFO: TMS tpsvrdone complete
143834.W40006071!TMS.639: CMDTUX_CAT:457: INFO: TMS tpsvrdone complete
143834.W40006071!TMS.616: CMDTUX_CAT:457: INFO: TMS tpsvrdone complete
143838.W40006071!BBL.645: CMDTUX_CAT:26: INFO: The BBL is exiting system
144646.W40006071!tmadmin.351: 081502: TUXEDO Version 6.4 32-bit Windows.
144646.W40006071!tmadmin.351: TMADMIN_CAT:1330: INFO: Command: help

Bit locker drive encryption failed due to power failer and hard disk corrupted

I ran Bitlocker drive ecryption drive D. My pc is windows 7 ultimate, while it was in progress of 1% due to power failer the encryption failed, when power resume the drive didn't showed the file format nor the size but it shows the size in disk management.
It showed like this in My computer
I do Have the recovery code password and back of recovery password so I ran the "manage-bde-_unlock D:-rp[my code ]
and my pc got hang no other option rather than to press the restart button.
then I used commang "repair-bde -force D:I:-rp[my rp] and following info showed but it stucked in 1% about 8 hours, and there was no increase in the pecentage
I also connected the hardisk to mac but all othe partation showed but didn't showed the encrypted one.
I had lots of memorable picture and other backups so any one kindly help me to get out of this problem. Thanks for help

Hi,
The BitLocker encryption and decryption processes can be interrupted by turning the computer off, and it will resume where it left off the next time Windows starts. This is true even if the power is suddenly unavailable.
Bitlocker-repair (repair-bde) tool
can't repair a drive that failed during the encryption or decryption process.
In addition, could you please explain a bit for what drive you are trying to deal with? external one?
When you first restart your PC, have you seen any signs that indicate that the encryption is in process?
Regarding your scenario, please take a look to see if the following articles could help here:
Scenario 11: Recovering Data Protected by BitLocker Drive Encryption (Windows 7)
Besides, when running manage-bde command, did we followed the steps mentioned in the below article?
Scenario 14: Using a Data Recovery Agent to Recover BitLocker-Protected Drives (Windows 7)
Best regards
Michael Shao
TechNet Community Support

Cannot send email from my Touch (connection to smtp server fails)

Hello,
I have a new iPod Touch with 1.1.4 and the January apps. I am having a problem setting the Mail application.
I am trying to connect to the IMAP/SMTP servers at my university. I am using the exact same settings and passwords I use on my laptop, which works fine. I can receive email fine on my Touch, but every time I try to send one it fails tellings me "the connection to the outgoing server smtp.myuniversity.edu failed".
If I on purpose write a wrong password for the outgoing mail, the error message I get is different ("check the account settings for the outgoing server smtp.myuniversity.edu").
The university IT people confirmed my settings, and told me that there is nothing blocking any handheld device from using the server.
Does anyone know why this would happen?
Thanks,
Marcelo

Thank you very much for your responses
1) the link to mail setup is (sorry, it's quite long)
http://www.knowledgepak.com/kpaksonline/kpol.asp?PiAlias=kpolpi17&k2dockey=04096 3251575739@kpol17&ViewLink=true&SkipHeader=false&printformat=true
2) I am indeed using SSL, as instructed by IT
3) I do use port 587 instead of 25 (25 does not work either)
Any ideas? Thanks again.
MC

BSI ConnectToDataSet...failed

Hi
We have a problem with the BSI, we had been getting a dump "RFC_ERROR_SYSTEM_FAILURE", I followed the SAP Note 1068271 for the debug, and the result is:
=Thu Jan 22 11:53:37 2009
=SAP AG, Walldorf - Business API for BSI TaxFactory 8.0
=RfcAccept called
=Mapping ABAP RFC_PAYROLL_TAX_CALC_US_80 to C function srv_Payroll_Tax_Calc_US_80
=Mapping ABAP RFC_HR_TAXLOCATOR_US_80 to C function srv_hr_taxlocator_us_80
=Waiting for ABAP function calls
=Running function srv_Payroll_Tax_Calc_US_80
=Loading import parameters
=Loading export parameters
=Loading internal tables
=Calling Payroll_Tax_Calc_US
=Running Connect_DB_Payroll_Tax_Calc_US
BSI dataset -> 110
ConnectToDataSource...Succeeded
ConnectToDataSet...failed
Error String -> 7777 - [Oracle][ODBC][Ora]ORA-00933: SQL command not properly ended
=RFC error
operation/code Connect_DB_Payroll_Tax_Calc_US
key RFC_ERROR_SYSTEM_FAILURE
status
message See RFC trace file or SAP system log for more details
internal status
The RFC under sm59 is working fine, the error is on the connection to the Dataset according to the Debug log "ConnectToDataSet...failed".
I don't know what to check about the Dataset, could you please help me?
Best Regards

Yes, it's correct.
I checked it's 8.0.
I think is a problem with the parameters under tf80server.bat.
SET
TF80_CONNECT_STRING=DSN=;UID=;PW
D=;
SET TF80_SCHEMA_NAME=.TF80
REM for SAP trace debugging, uncomment below & see file
errors.txt in gateway working directory
REM C:\BSI\TAXFACTORY\tf80serverdebug.exe %*
REM else for usual operation
C:\BSI\TAXFACTORY\tf80server.exe %*
I don't know what is the "ODBC_DSN_NAME"
I have the user, password, the database name...
Best Regards

Installation of IPC AP 7.0 Jar is getting Failed when uploading in CRM

Hello Experts,
we did some changes in the previosly uploded version of IPC AP 7.0 customer user exit Jar file in eclipse.
While uploading the new modified jar through transaction /SAPCND/UE_DEV in CRM we are getting error :" installation of module <Jar file name > has failed ".
when we checked the logs in SM 53 we seen the below mentioned error:
Message: Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type com.sap.sql.sqlparser.CommonSQLParserException: - statement "DELETE FROM "SVMCRT_MOD_TR_T" WHERE "MODULE_NAME" LIKE ? ESCAPE ^ (reason: Modification of ABAP tables is not permit ted)" is not supported
caught: - statement "DELETE FROM "SVMCRT_MOD_TR_T" WHERE "MODULE_NAME" LIKE ? ESCAPE ^ (reason: Modification of ABAP tables is not permitted)" is not supported
--> com.sap.sql.log.OpenSQLException: Exception of type com.sap.sql.sqlparser.CommonSQLParserException: - statement "DELETE FROM "SVMCRT_MOD_TR_T" WHERE "MODULE_NAME" LIKE ? ESCAPE '^' (reason: Modification of ABAP tables is n" is not suppor ted
caught: - statement "DELETE FROM "SVMCRT_MOD_TR_T" WHERE "MODULE_NAME" LIKE ? ESCAPE '^' (reason: Modification of ABAP tables is not permitted)" is not supported
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Ljava/lang/Class;Ljava/lang/String;[Ljava/lang/Object;)Lcom/sap/sql/log/OpenSQLException;(Syslog.java:85)
at
if required i can post the complete stack trace.
any inputs/suggestions are most welcome.
Thanks & regards,
Siddharth

Hi Mark,
Yesterday after Posting the thread we found the same Note ,Issue occured because of JAVA write access was not enabled on the table ,After enabling it as mentioned in SAP Note, Jar file get successfully uploaded.
Thanks for your Help also.
Regards,
Siddharth

Upgrade to ERp6 phase STARTSAP_NBAS error: DDIC login fails

Hi
During an upgrade from 4.7 to ERP6 I get the following error
message in phase STARTSAP_NBAS:
SYSTEM START failed, code -2
-2: the test rfc did not work.
Try to log on to the system with user DDIC
When I try to log on to the system as user DDIC, I get the following
error message:
DB-Error -0
SAP* can log in .The password I submit is correct. I have not changed this password at
any time.
Any ideas are most welcome

Hi,
DB-Error -0 indicate problem with kernel, try to upgrade kernel.
check Note 760175 - 6.20: Logon not possible (after DB export or system copy)
regards,
kaushal

Running workbook from .bat fails to start application missing CORE40 dll

I have been running several workbook via windows task scheduler / vbscript &/or bat files.
I now have a new box which I access thru Remote Desktop Connection, so I can run all these automated updates without having my screen blinking everytime a shedule workbook starts.
If I click on the actual Discoverer icon, or the discoverer workbook shortuct, all works well.
If I click on the .bat file, or try to run the workbook via the cmd , it gives me the following error:
DIS4USR.EXE – Unable To Locate Component
“this application has failed to start because CORE40.DLL was not found. Re-installing the application may fix this problem.”
The dll is under c/orant/bin/core40.dll, which is where I've read it should be, and it works fine in my regular box...
Please help! URGENT :)
Thanks!

Hello
Check the PATH environment variables for the machine you are on and the one you are connecting to.
You might not have Discoverer's objects in the PATH.
Another possibility is that you have more than one piece of ORACLE software on the machine and you may need to also set the ORACLE_HOME within the BAT file.
Best wishes
Michael

Due to my laptop screen failing i have to return to facory settings, can i reinstall adobe reader and adobe air afterwards?

Due to my laptop screen failing I have to return it to factory settings, can I reinstall adobe reader and air afterwards?

I don't see why not. Do you foresee a special difficulty?

Downloads to documents folder fail due to parallel upload

Hi, mobile documents is a great tool that I use to replicate all business relevant documents to mobile clients. However there is one great disadvantage for me. When you download a file that is a bit larger (>1 MB), during the download the client will already start uploading the temporary file. So the download then fails as it cannot convert the temporary file into the final one.
This is something that does not happen for equivalent clients (for example skydrive). Do you think this is something that can be fixed?
thanks,
Heiko

Hi Heiko,
Let me explain again:
You said "uploader locks the file so that it can no longer be changed". For the temporary file it is the downloader which have locked the file. Hence, the impression that file is getting uploaded because it is locked is hence not correct.
The next version might be available in Q1\Q2 2014. We will keep everyone updated via community.
Best Regards,
Ashwani Kr Sharma

Xa_open - failed

Similar Messages

Maybe you are looking for