Groupwise Error 8913
Novell GroupWise 5.2. GroupWise Support Pack 2. Novell GroupWise 5.5. Novell NetWare 4.11 IP between domains through a 56K line and a Cisco router. symptom 8913 write error at one domain and 8913 read error at the other domain. Error: 8913. Error received on Message Transfer Agent. change IWSP5b.EXE applied. fix Changing link type to UNC in Link Configuration allows the Message Transfer Agent to send/receive without error . NOTE: Customer also updated to GroupWise 5.2 Support Pack 3 agents, which may have also contributed to the solution of this problem . document Document Title: 8913 write error at one domain and 8913 read error at the other domain. Document ID: 10007700 Solution ID: 1.0.305317.1818336 Creation Date: 30Sep1998 Modified Date: 09May2002 Novell Product Class:GroupwareNetWare disclaimer The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.
of the error: Windows Windows Groupwise Error 8913 are caused by misconfigured system files. So, from my experience, If you received a Windows Groupwise Error 8913 message then there is a 97.5% chance that your computer has registry problems. The Windows Windows Groupwise Error 8913 are easy to repair. By downloading and running the registry repair tool RegCure Pro, you can quickly and effectively fix this problem and prevent others from occuring. Simply click the links below for your free download. To Fix the problem you need to follow the 3 steps : STEP 1: Download & http://support.novell.com/docs/Tids/Solutions/10007700.html Install RegCure Pro for Free. NOTE: If the download link doesn't work you may need to Download it Directly from a Mirror Here. STEP 2: Click "Quick Scan" Button to Scan Your Computer. STEP 3: Click the "Repair All" Button to Repair Your PC! That's All! Scott Chan Technical Description of System Error(for Experts only): Microsoft Windows [Version 5.2.4630] (C) Copyright 1985-2014 Microsoft Corp. C:\Documents and Settings\Administrator>RegCure Pro.exe http://computerfixerrorsfree.com/windows-groupwise-error-8913.php Windows Windows Groupwise Error 8913 may caused by some of the following errors Windows Explorer ErrorsJavascript ErrorsHardware MalfunctionError Symptom include:Can not printing fileBlue ScreenIO errorShutdown problemsHttp error Tags: Windows Windows Groupwise Error 8913 4 Response to “RegCure Pro ” NumbersSays: at 9:22 PM Thank you so much! After spending countless hours on this stupid windows groupwise error 8913 problem I almost gave up. RegCure worked like a charm on the first try. It took a bit longer than 10 minutes, closer to 30, but by the time it was finished my PC worked great again. Corinne Says: at 3:47 AM Just ran this on my wife's computer and for the first time in a long time, it finally works again! Regcure found over 2500 errors including the Windows Groupwise Error 8913 and fixed them all. I'm not a PC guru by any stretch, but this was a godsend. Cheers! Arletta Says: at 4:48 AM worked just like it said. no more errors and officially back in action. ty ty ty Brian Says: at 9:12 AM it worked!!!!!!! Download Now: Windows Error Repair Tool *RegCure Pro will repair Windows Error and registry data errors on your PC Compatible with ALL Versions of Windows Including Windo
any of your clients or Servers on auto-negotiate ports for speed and/or duplex? They don't like it, on a quiet network http://ngwlist.com/pipermail/ngw/2000-June/026016.html it works sometimes, but really show up when it get busy. Set them to fixed and set Servers (inetcfg) to fixed too. John John Whitehorn Academic Computing Services Information Services Directorate https://www.experts-exchange.com/questions/21528622/Groupwise-6-0-3-on-new-Windows-XP-SP2-Machine.html The University of Nottingham University Park Nottingham NG7 2RD >>> John.Brines at is.ctscorp.com 07/06/00 09:20:10 >>> We are having major problems with Client Server connection, here is the story. At groupwise error the start of our GroupWise install all our clients were using Direct Mode as most of our clients didn't have TCPIP installed. We then installed TCPIP and then forced all our clients to use client server. Once we did this we started to encounter major problems 1. Sent mail not being sent although it looked as if it was. 2. Sent mail groupwise error 8913 with attachments sitting for ages then coming up with an 8913 error. 3. Sent mail with attachments sitting for ages then crashing out of GroupWise. We have had to put all our clients back to Direct Mode. There are four PCs in my office three of them have the above problems and one (my PC) doesn't. We are using mainly Windows NT4 Workstation SP6a and GroupWise 5.5 EP SP1 Please help. Regards John. ================================================================== Notice: This message is intended solely for the person to whom it is addressed. Unintended recipients will be legally responsible for unauthorized use, disclosure, copying or distribution. If you have received this message in error, please notify the sender immediately by replying to this message. Then delete this message from your system. Thank you. CTS Corporation UK Ltd 44 (0)1698 505050 Phone Blantyre Industrial Estate, 44 (0)1698 506050 Fax High Blantyre, Glasgow, United Kingdom. www.ctscorp.com ================================================================== Previous message: Other List Next message: [ngw] Calendar as HTML Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the ngw mailing list
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Groupwise 6.0.3 on new Windows XP SP2 Machine Want to Advertise Here? Solved Groupwise 6.0.3 on new Windows XP SP2 Machine Posted on 2005-08-16 Groupware 1 Verified Solution 15 Comments 221 Views Last Modified: 2013-11-12 Hello all, I just installed 3 new Dell Optiplex GX280 with Windows XP Service Pack 2 and Groupwise 6.0.3. Groupwise cannot send out attactments. Either it times out or just sits there. I have the Windows Firewall Service and Security Center Service stopped. I have reinstalled Groupwise and Microsoft Mail Client, I have also tried different Novell Clients. I have other PC's with Windows XP SP2 and they have no issues. The Groupwise Error Is get is 8913 after 10-20 minutes of trying to sent the attachment. Hopefully someone can help. 0 Question by:networx-fl Facebook Twitter LinkedIn Google LVL 35 Active 5 days ago Best Solution byShineOn How do you patch your machines? Have you been using the Windows Update site or do you have a WSUS server or something else? Have you ensured that the patch levels on the new XPSP2 boxes are the same Go to Solution 12 Comments LVL 35 Overall: Level 35 Groupware 12 Message Active 5 days ago Expert Comment by:ShineOn2005-08-16 Is this with any attachment, no matter how large or how small? 0 LVL 34 Overall: Level 34 Groupware 13 Message Expert Comment by:PsiCop2005-08-16 1) Uninstall the GroupWise client 2) Uninstall Windoze Messaging 3) Reboot 4) Reinstall the GroupWise client If you need the M$ Mail client, then install it AFTER the GroupWise client. 0 LVL 35 Overall: Level 35 Groupware 12 Message Active 5 days ago Expert Comment by:ShineOn2005-08-16 It shouldn't matter what Novell client32 you're using (although the most current for your platform is best) because the GroupWise client doesn't use the Novell client if you're in client/server mode. It just uses TCP/IP. Generically speaking, an 8913 error is a "socket write failure." I would suspect something with the network configuration on the Dell PC's, but this kind of thing