Full Text Extraction error

Audrius,

I am pleased to report that your suggestions have lead me to fix the problem.  None of the msprocessors where loaded in the shepherd.xml file so I unregistered and registered and all is good.  Thank you for your assistance.

Sean

Sean,

Please see the following link to find out about logging in ProjectWise version you  use: http://communities.bentley.com/Wiki/view.aspx/Troubleshooting_ProjectWise_Orchestration_Framework_And_Document_Processors

That version of the product was also storing the processors with their paths in shepherd.xml (under Program Files/Bentley/Orchestration Framework). You may check if msprocessor is registered there. Probably you are dealing with incomplete or broken processor registration.

"Regular" way to resolve the registration issue is to re-install ProjectWise Integration Server.

Other, a bit more complicated, is to locate DmsAfpEngine.exe in Program Files and run it with parameters "-register ftr" (do not use quotes). This will try to re-apply FTR configuration. If that does not help, you may try "-unregister ftr" first, and then "-register ftr". That is a shorter version of what happens on AFP uninstall and install.

I think that is as far as we can go discussing this, before this becomes too detailed for a forum discussion. Bentley Support have much expertise in helping to resolve customer specific issues.

thanks,

Audrius

MicroStation ver 08.09.04.88

ProjectWise ver 08.09.04.09

Sean,

you are correct. 9 messages are awaiting for processing.

If you run Orchestration Administrator, it should show the processors under the machines on the left side pane. And because  you do not find that log file suggests that I may have miss-guessed the ProjectWise version you are using. Could you please provide both ProjectWise and Microstation versions?

Thanks,

Audrius

Audrius,

 Based upon your response I checked into your suggestions and below I have responded.

I looked in the MSMQ node and the queues do exist even the msprocessor1 does show, however the msprocessor1_job does show 9 messages so I am assuming that there are tasks waiting to go.

I could not find the loggingservice.log and the windows appliocation log you describe I assume you are describing the event viewer and I did not find anything out of the ordinary.

MicroStation is installed and is in the default install folder.  I ran MicroStation from the server.  If the OF thinks the processor is on a different machine how do I check this?

TIA

Sean

Sean,

All AFP (Automated File Processing)  processors and dispatchers run 24x7, not only when they have job to do. So must the ustation.exe. If processor is not running, that explains the error - you cannot get the size of the queue that is not active (have no queue reader bound to it).

You may inspect the queues and find their properties using Computer Management console. Under Services and Applications you will find a MSMQ node. Look for  private queues, and all queues used by Orchestration framework (OF) and AFP will be there. Only for the problem you try to solve, I don't think it is a place to look first.

The service responsible for starting processors (PW OF Shepherd) must have problems starting msprocessor, if you do not see it in the task manager. If it fails - the error is probably recorded in OF log (%allusersprofile%\Application Data\Bentley\Logs\LoggingService.log), or in Windows Application log. Finding and studying a reported error could lead us to understanding why the processor is not running.

I will give here few reasons that in my opinion may cause this problem:

• Microstation was uninstalled.
• Microstation was reinstalled to a diferent folder after PWIS setup.
• Machine name has changed and OF thinks the processor runs on a different machine.

 thanks,

Audrius

Anthony thanks for the reply and I have a few more questions.

 All other process are running and have no errors so I am connected to the right database with OF.

Where does the queue exist?

There is not a ustation running at this time in the task manager and I would assume that this processor does not start unitl the scheduled time I have set in PW Admin.

 Thanks.

The Orchestration Framework calls into MQMgmtGetInfo to determine the number of messages waiting in the queue.

If the function returns an error code we translate it into a message.  Over the years MQMgmtGetInfo added a new return code.  We didn't have a message for it, so the default behavior was to just display the return code value.  The value 3222142980 in hex is  0xC00E0004.  This translate to  MQ_ERROR_QUEUE_NOT_ACTIVE -  The queue is not open or may not exist

http://msdn.microsoft.com/en-us/library/ms700118(VS.85).aspx

We updated the code to reflect this change.

However, you want insight into the real problem. 

I have never seen this problem, but here are a few things to check. 

Check to make sure the queue exists. 

Is the MicroStation Processor running?  Through task manager do you have a running instance of ustation with all the GUI instances shutdown?

Are you browsing the right OF database?  From the OF installdir run dbsetup.exe.  Does your database match the one in your OF browser in the OF admin?

HTH,

Anthony

As I monitor the instances with the Orchestration Framework Administrator I see that the MicroStation Processor in the full text extraction monitor has a red x which obviously is a problem.  The error is "Failed to obtain queue size due to the following error:3222142980".

Anyone have this problem or able to provide some insight on the error?

Thanks