Q1. MW has pushed a message but it is not showing up on the Siebel UI or in the database. What should I do?
You can check for any one of the below or all of the below
a. Check if the Adapters are up and running.
b. Check if the Adapters are using the right srf
c. Look for the errors generated in the folder \Sybase39\Siebel-3_9\bin. The log file names are usually
similar to the Adapter dat file names

Q2. How do I bounce the Adapters?
a. If the adapters are up, you will see an instance of ADPWatch.exe running on your desktop. Close this exe
first and then start closing all the Adapter screens. This should close all the running instances of the
Adapter
b. Double-click the ADPWatch.exe available on the desktop and click Look Now button. This will start all
the adapters.
c. Alternately you can also start the adapters by clicking on the ADPWatch.exe available in folder
\Sybase39\Siebel-3_9\bin
 
Q3. MW has pushed a message but my adapter is crashing. What should I do?
This means that there is corrupt message lying in the MW queue due to which your adapter is crashing. The only solution to this problem is to ask the Middle Ware team to clear the queue and push the message once again.
 
Q4. When do I need to extract new formats (ncm and MW formats)?
· If you have created a new IO which will be using NEON adapter to talk to Siebel Objects..
· If you have modified an existing IO which will use NEON adapter to talk to Siebel Objects
 
Q5. When does error “Port xxx busy” comes after the adaptors are restarted?
Whenever adaptors are restarted, sometime the earlier instance doesn’t release the port, hence the new adaptor instance is not able to acquire the port as per setting in .dat file. To remove this error, restart the adaptors again and if the error is still persistent then machine restart is required.