Guys,
I receive the following message in my eventlog:
The call to member StartListen failed. System.Messaging returned the following message:
Invalid queue path name.
I installed the NAS on a different server then my Sharepoint Server. I used the queue names, Navision already created during the installation (i.e. .\private$\nep_reply_queue and .\private$\repqmq
Any thoughts?
Kind regards,
Bas Dirkse
0
Comments
best practice and recommondation for NEP is:
If SharePoint is on machine A and NAS is running on machine B then
- create Job Queue on machine B
- create Reply Queue on machine A
- Set the right formatnames (.\xxx for local queue, FormatName:DIRECT=TCP:xxxx for remote queues).
If you have any questions please post a reply with the name/ip of the two machines and the queue names you have created.
HTH,
Rainer
BTW: What do you think about EP?
Thanx for your reaction!
I'm still not sure how to set up the queues.. I have the following config:
Machine A:
WinXP Prof
Navision 4.0 SP1 (client only)
NAS 4.0 SP1
Machine B:
Win2003 Server
IIS6.0, Sharepoint Serer
Correct me if I'm wrong, but I see 4 queue configurations in the setup form of the Portal (2 for Front End and 2 for Key Exchange)
I'm not sure what the usage is for the key exchange queues; I deselected the feature.
On the tab page Front End I set the following queues:
Request Queue: MachineA\private$\nep_request
Reply Queue: DIRECT=TCP:MachineB\private$\nep_reply
I'm also not sure how to setup the web.config file on the server.
Thanks,
Bas
sorry for the late reply, was somekind of busy.
First of all:
- MSMQ has to be installed on BOTH machines
My assumptions:
- Machine A (NAS) has IP 192.168.0.1
- Machine B (SharePoint) has IP 192.168.0.2
You have on Machine A the following queue:
.\private$\nep_request_queue
You have on Machine B the following queue:
.\private$\nep_reply_queue
Result:
This should be the configuration in Navision:
x Checkmark in "Front End Processing" (==TRUE)
x Request Queue: .\private\nep_request_queue
x Reply Queue:
FormatName:DIRECT=TCP:192.168.0.2\private$\nep_reply_queue
This should be the configuration in web.config on SharePoint:
<add key="JobQueues" value=
"FormatName:DIRECT=TCP:192.168.0.1\private$\nep_request_queue"/>
<add key="ReplyQueues" value=
"FormatName:DIRECT=TCP:192.168.0.2\private$\nep_reply_queue"/>
Notes:
I added some breaks for better display ;-)
Instead of using
- DIRECT=TCP:192.168.0.X
you may also use
- DIRECT=OS:MACHINENAMEX
The queue names have to match, so it is not important that the queue name is nep_reply_queue, you may also use something like nep_reply or MyReply,...
The code of the NAS has to start with NEP- and has to match in Navision and on the NAS-SnapIn-MMC-StartUpParameter.
HTH,
Rainer
Thanks for your help, it has been useful!
Do you know by any chance if it is possible to use filter ON THE WEB? I know it is possible to set a filter in de definition in Navision, but I want to set filters on the website...
Thanks again,
Kind regards,
Bas Dirkse
with EP it is not possible to set a filter directly on the web.
The only possibility is, that you define actions which will cause a new request and there you set the filter (but this one has to be defined beforehand in Navision).
But there will be out another product in the next couple of weeks that will enable filtering and navigation on Web Parts. It is called "IT IS activigence" from http://www.itis.de/activigence
HTH,
Rainer