Groupwise Error 80004005
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 7 - OLE Error 80004005 Want to Advertise Here? Solved Groupwise 7 - OLE Error 80004005 Posted on 2009-06-16 Groupware Server Hardware 1 Verified Solution 5 Comments 7,924 Views Last Modified: 2013-11-12 Several users that connected to Groupwise fine up until today are trying to log in and seeing an OLE Error 80004005. It refers to Groupwise not initializing successfully. Suggestion to run GW setup or contact system administrator. Research on the web revealed Novell's Group states error 80004005 is unspecified and has no fix or solution. I tried to log in the same users on another PC and got the same error. So I don't think it is Groupwise setup on the pc. I am the System Admin. and am wondering what to try next. Should I just reboot the server? 0 Question by:IT_Clinton Facebook Twitter LinkedIn Google LVL 10 Best Solution byDSPoole I should explain in more detail: 1) put the post office in client server/DIRECT Access mode 2) restart po agent 3) attach with the problem user via Direct Access 4) archive 5) delete mailbox Go to Solution 4 Comments LVL 18 Overall: Level 18 Groupware 14 Server Hardware 2 Message Active 3 days ago Expert Comment by:ZENandEmailguy2009-06-18 First step would be to reboot the server but I don't think that will be the solution. Have you run any maintenance on mailboxes/post office? Can you login to GroupWise with different users and see some get the error and some not? If some can, obviously they are likely fine. Those who cannot, we can try some different maintenance with GWCheck on ju
starting the groupwiseclient. The message is: Groupwise is not initialized correctly, please runsetup. When the people who are having this problem close their notifyprogram and start the groupwise client again, it runs without any problem.Any idea's ?Environment: windows 98 SE (dutch) with dutch GW6.5 SP5 client and windowsXP SP2 with dutch GW6.5 SP 5 clients.We have tried completely cleaning and reinstalling the groupwise client,however this does not solve the problem.Regards,Hen Automatic https://www.experts-exchange.com/questions/24496632/Groupwise-7-OLE-Error-80004005.html reply 2006-02-21 09:30:37 UTC PermalinkRaw Message Hen,It appears that in the past few days you have not received a response to yourposting. That concerns us, and has triggered this automated reply.Has your problem been resolved? If not, you might try one of the following options:- Do a search of our http://novell.support.groupwise.6x.clients.narkive.com/BktmFGtB/ole-error-80004005-starting-groupwise-when-notify-is-loaded knowledgebase at http://support.novell.com/search/kb_index.jsp- Check all of the other support tools and options available athttp://support.novell.com.- You could also try posting your message again. Make sure it is posted in thecorrect newsgroup. (http://support.novell.com/forums)Be sure to read the forum FAQ about what to expect in the way of responses:http://support.novell.com/forums/faq_general.htmlIf this is a reply to a duplicate posting, please ignore and accept our apologiesand rest assured we will issue a stern reprimand to our posting bot.Good luck!Your Novell Product Support Forums Teamhttp://support.novell.com/forums/ Hen Savelkoul 2006-03-09 10:23:53 UTC PermalinkRaw Message This is really a big problem in our organization. Each time when a userexperiences this error and closes notify the error goes away. Isn't anyoneelse experiencing this.We use zenworks to start the notify and groupwise clients, Does this perhapshave anything to do with it.Is it a timing issue ?We have tried uninstalling, cleaning and reinstalling the client, but thisdid not fix anything. It see
från GoogleLogga inDolda fältSök efter grupper eller meddelanden
80004005 - Unspecified ErrorThink of error 80004005 as meaning the script could not access your data. The most likely reason is a permissions related problem. Your best chance of resolving this problem is to study carefully any associated message, for example, 'File already in use', or 'Logon Failed'. Introduction to Error Code 80004005 Error 80004005 is a general error for all manner of events. I have to confess that I am still trying to understand all the causes of this code number. One thread that runs through error 80004005 problems is permissions. Another thread is incorrect format, for example you entering a number instead of a string. This is particularly true of telephone or fax numbers. My main interest is in VBScript errors, however, I have added database examples for completeness. The first branch in your decision tree is this an ASP error or some other ODBC error. Three types of 80004005 Error VBScript Connectivity Problems - E.g. SQL Data Access Components - MTS ‡ VBScript Symptoms What you see is WSH (Windows Script Host) message box. The script does not execute as you had hoped. Instead you get a message box like this picture: The Causes of Code Error 80004005 VBScript / CScript 1) In this case, VBScript was trying to store a password. With error 80004005 there is usually an element of access denied. Insufficient rights, wrong permissions. 2) It can occur when a VBScript attempts to connect to scriptpw.dll. There are other causes, such as connecting to COM objects or ADO, or other database object. 3) Another thread is Number v String value format. If you are dealing with a phone number, make sure that you add it as string value and not as a pure number. Extra information supplied by Murda McLoud. 'I worked out that had to convert the number to a string to stop the 80004005 error. Then the objUser.Put would work properly and save the data.' Solutions for Error 80004005 This has been a very difficult error to track down. Possibly the error was due to using WScript instead of CScript.Check the underlying database, for example, names, exclusive locks and especially permissions.One additional probl