Error In Transacting Named Pipe Rightfax
to view faxes in FaxUtil or login to FaxUtil, "Error 231 in transacting named pipe" occurs. Solution: This error occurs for two reasons. Both are related to the RightFax database. Cause 1: RightFax database unable to handle workload You can expect this error regularly if you're sending a large batch of faxes each day at the same time. If that is your situation, you might consider distributing the job throughout the day or adding an additional RightFax server. Solution 1a: Determining work requests To view the number of work requests that the RightFax server needs to process, log on to Enterprise Fax Manager, and then click Utility > Show work requests. The number of work requests displayed for any field should not constantly increase during the day. For any work request increasing beyond 1000, you might want to contact Advantage Technologies Support directly to determine the cause: (866) 730-7700 Solution 1b: Viewing RightFax processes Use Task Manager to view processes on the RightFax server. On the Processes tab, see if any processes are maxing out the CPU. If the CPU is maxed out, then the Rightfax services and applications will run slower, possibly causing the "231" error. Solution 1c: Viewing and increasing database threads To view the status of the last RightFax database thread: 1. Open Enterprise Fax Manager. 2. Right-click the RighFax database module. 3. Select 'STATUS' from the dropdown menu 4. From the dropdown list of the status window, select the last database thread (NOT the file thread). The last database thread should show total commands executed of zero. If it's not zero, increase the number of database threads by 2 and test again. This number should not raise above 1 in a 24 hour period. If it is a large number within an hour after a restart, you should increase the number again immediately. The idea is to fine tune the level so that the last thread is seldom used but you do not have a lot of threads that are unused. Note: This will stop and restart the RightFax Server and database services. To increase the number of database threads: 1. Right-click the RightFax Database Module. 2. Choose Configure Service. 3. Click the Advanced tab. 4. Select a value in the Max Threads list. 5. Click OK. Please be aware that with 9.0 when using MSDE, there is a limit to the maximum connections that can be made to MSDE, and exceding this number can cause issues. Contact theRightFax Expertsfor your support related issues Posted by Mo Skaikay at 12:27 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Newer Post Older Post Home My Favorit
Monitor an unlimited number of servers with $49/year With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case. New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye http://rightfax-tech-tips.blogspot.com/2012/11/error-231-in-transacting-named-pipe.html on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers. read more... Event ID: 3318 Source: RightFax RPC Server Module Source: RightFax RPC http://www.eventid.net/display-eventid-3318-source-RightFax%20RPC%20Server%20Module-eventno-5811-phase-1.htm Server Module Type: Error Description:RPCDBT:Error (
all antivirus software before installing SP4. Some folks are reporting incomplete installation, more as it develops. Its somehow related to additional software they have installed or running. All have been able to http://kb.eventtracker.com/evtpass/evtpages/EventId_3318_RightFaxRPCServerModule_50024.asp gracefully back out of the installation. Two reports of icons changing, AD users & computers icons and all MS Office icons changed to the unknown http://maisonbisson.com/911pagers/text/keyterm/transacting/ type icon. Seems to only happen on servers. Some issues with VPOP3 and RAS not functioning correctly after applying SP4.There is now a fix for the error in VPOP3 problem. Apparently SP4 complained when the buffer passed for results was larger than expected, so you cant use a generic buffer now, it has to be correctly set up. (note just received confirmation on a second VPOP3 problem, been told that VPOP3 doesnt recognize RAS intermittently after applying SP4). In error in transacting the Control Panel, double-click RightFAX Server. Review the default settings.RightFAX runs adequately without changing these settings but there are a couple thatcan be changed with advantage.Allow notification, can be set to notify fax status via e-mail or a message box on aclient workstation.Retry settings, can be set to handle fax failures.After selecting these options, click OK. RightFAX services are restarted and the newoptions are activated.Log on as admin. Check that the following RightFAX services are running:RightFAX Queue HandlerRightFAX RPC Server ModuleRightFAX Server ModuleRightFAX Boardserver ModuleRightFAX Database ModuleRightFAX Workserver1 ModuleRightFAX Workserver2 ModuleRightFAX Workserver3 ModuleThese services are in manual start-up mode andare started by the RightFAX server module.Check that RightFAX has been added to the Programs menu on the Start button.Reference Links Did this information help you to resolve the problem? Yes: My problem was resolved. No: The information was not helpful / Partially helpful. Comments: Captcha Refresh
the following insertions string(s): RPCDBT:Error (2) in transacting named pipe 2:10 am September 12, 2001 Comments Off on 09/12@01:00:02 AUSFAX:[ResourceString] The description for Event ID (3318) in Source (RightFAX RPC Server Module) could not be found. It contains the following insertions string(s): RPCDBT:Error (2) in transacting named pipe 09/12@01:00:02 AUSFAX:[ResourceString] The description for Event ID (3318) in Source (RightFAX RPC Server Module) could not be found. It contains the following insertions string(s): RPCDBT:Error (2) in transacting named pipe 2:10 am September 12, 2001 Comments Off on 09/12@01:00:02 AUSFAX:[ResourceString] The description for Event ID (3318) in Source (RightFAX RPC Server Module) could not be found. It contains the following insertions string(s): RPCDBT:Error (2) in transacting named pipe 09/12@01:00:02 AUSFAX:[ResourceString] The description for Event ID (3318) in Source (RightFAX RPC Server Module) could not be found. It contains the following insertions string(s): RPCDBT:Error (2) in transacting named pipe 2:09 am September 12, 2001 Comments Off on 09/12@01:00:02 AUSFAX:[ResourceString] The description for Event ID (3318) in Source (RightFAX RPC Server Module) could not be found. It contains the following insertions string(s): RPCDBT:Error (2) in transacting named pipe 09/12@01:00:02 AUSFAX:[ResourceString] The description for Event ID (3318) in Source (RightFAX RPC Server Module) could not be found. It contains the following insertions string(s): RPCDBT:Error (2) in transacting named pipe 2:09 am September 12, 2001 Comments Off on 09/12@01:00:02 AUSFAX:[ResourceString] The description for Event ID (3318) in Source (RightFAX RPC Server Module) could not be found. It contains the following insertions string(s): RPCDBT:Error (2) in transacting named pipe in Source (RightFAX RPC Server Module) could not be found. It contains the following insertions string(s): RPCDBT:Error (231) in transacting named pipe 10:09 pm September 11, 2001 Comments Off on in Source (RightFAX RPC Server Module) could not be found. It contains the following insertions string(s): RPCDBT:Error (231) in transacting named pipe :Error (231) in transacting named pipe 10:09 pm September