Applies to:
Siebel eCommunications eMail Response - Version: 7.7.2 SIA [18325] and later [Release: V7 and later ]
Siebel Email Response - Version: 7.7.2 SIA [18325] and later [Release: V7 and later]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.2 [18325] Pub Sect
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server
This document was previously published as Siebel SR 38-2700877531.
Symptoms
We have an Comm Inbound Receiver on our Test machine that worked fine up
until a certain day 2 months ago and then we have not been able to get
it to work again since then. I have attached the log file. I have
followed all recommendations on SRs regarding POP3, but I have not been
able to find a solution. I can login to the pop3 server fine from the
telnet command line and lock the mailbox, but Siebel never gets to the
point of trying to login based on the log files. I have also attached
the script of the telnet session.
Although this is not a
production issue, it is preventing us from testing critical fixes to the
production system. Thank you for your prompt attention to this matter.
Cause
Incorrect settings for the Comm Inbound Processor component.
Solution
Message 1
For the benefit of other users,
When the Siebel Services are started, the Comm inbound processor was exiting with the task status
SBL-GEN-01000: System was unable to allocate sufficient memory for the specified operation.
Upon
further investigation it was found out that the reason was the
tableowner pass and password parameters for the comm Inbound receiver
and Comm Inbound processor components were changed at the enterprise
component definition level making them visible in clear text. Once these
parameters were removed, the components started normally and the emails
were properly processed.
אין תגובות:
הוסף רשומת תגובה