Upgrade to BES 4.1.4 for Groupwise failed
 

Well, my day is just turning out to be grand. :)

I had scheduled today to upgrade our BES from 4.1.3 to 4.1.4. I read through the upgrade guide, backed up the DB and registry, and was ready to go.

The Groupwise client I had installed was 7.0.2 since our Groupwise admin had set only versions > 7 as allowed to connect. I upgraded to 7.0.3 before the upgrade since I had read in another forum that this version was recommended over 6.5 SP7. Turns out that's not true.

Now I get the following in the GWCO logs:

[54001] (04/14 16:14:28):{0x798} {GWCO} {GWConnector} Starting GWConnector
[34192] (04/14 16:14:28):{0x798} {GWCO} {GWConnector} Database Edition=PERSONAL_MSDE
[34157] (04/14 16:14:28):{0x798} {GWCO} {GWConnector} Novell GroupWiseObject Library: C:\Novell\GroupWise\\gwcma1.dll, Version: 7.0.1
[34493] (04/14 16:14:28):{0x798} {GWCO} {GWConnector} GWConnector Version: 4.1.4.15
[34481] (04/14 16:14:28):{0x798} {GWCO} {GWConnector} GW API Mode=GW_OAPI
[34154] (04/14 16:14:28):{0x798} {GWCO} {GWConnector} Mailstore test start, test level=1
[34116] (04/14 16:14:28):{0x798} {GWCO} {thronsop} Login: Start
[14121] (04/14 16:14:28):{0x798} {GWCO} {} Error checking FID, Error=System.Runtime.InteropServices.COMException (0x80020009): An invalid argument was passed in the function call.
at System.RuntimeType.ForwardCallToInvokeMember(Strin g memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData)
at GroupwareTypeLibrary.DIGWAccount8.get_AccountPrope rty(AccountPropertiesConstants etAcctProp)
at ConnectorLibrary.ICEWrapper.GetFID(String& sCurFID)
[14123] (04/14 16:14:28):{0x798} {GWCO} {}
[14047] (04/14 16:14:28):{0x798} {GWCO} {thronsop} Login Failed, Username=thronsop
[34045] (04/14 16:14:28):{0x798} {GWCO} {thronsop} Logout admin user
[14095] (04/14 16:14:28):{0x798} {GWCO} {GWConnector} Mailstore test failed
[54002] (04/14 16:14:28):{0x798} {GWCO} {GWConnector} Terminating GWConnector

I'm seeing if the Groupwise admin will allow 6.5 SP7 to connect and I'm in the process of reinstalling 6.5 SP7.

However, 7.0.2 worked fine with BES 4.1.3. Anything else I should check?

Thanks

No minimum version set in Groupwise and SSL is no longer required but we get the same error.

The version of GW you are using cannot access this PO.

Now there's this in GWCO logs:

[14123] (04/14 16:51:18):{0x814} {GWCO} {} MultiLogin failed, error=System.Runtime.InteropServices.COMException (0x80004005): Login unsuccessful
at System.RuntimeType.ForwardCallToInvokeMember(Strin g memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData)
at GroupwareTypeLibrary.DIGWSession4.MultiLogin(Strin g vUserID, Object vCommandLine, Object vPassword, Object vWhenToPrompt, Object vReserved)
at ConnectorLibrary.ICEWrapper.AccountLogin(String& sUserID, String& sDomain, String& sPOA, String& sFID3)

We are really at a loss here. It almost looks like BES can't use the Groupwise install to talk to the POA but I can log in through the Groupwise client just fine if I open it and give it my username and password. Nothing else has been changed.

[30000] (04/14 17:41:18):{0xCC8} Current Date: 2008/04/14
[54001] (04/14 17:41:18):{0x960} {GWCO} {GWConnector} Starting GWConnector
[34192] (04/14 17:41:19):{0x960} {GWCO} {GWConnector} Database Edition=PERSONAL_MSDE
[34157] (04/14 17:41:19):{0x960} {GWCO} {GWConnector} Novell GroupWiseObject Library: C:\Novell\GroupWise\\gwcma1.dll, Version: 7.0.1
[34493] (04/14 17:41:19):{0x960} {GWCO} {GWConnector} GWConnector Version: 4.1.4.15
[34481] (04/14 17:41:19):{0x960} {GWCO} {GWConnector} GW API Mode=GW_OAPI
[34154] (04/14 17:41:19):{0x960} {GWCO} {GWConnector} Mailstore test start, test level=1
[34116] (04/14 17:41:19):{0x960} {GWCO} {thronsop} Login: Start
[14121] (04/14 17:41:19):{0x960} {GWCO} {} Error checking FID, Error=System.Runtime.InteropServices.COMException (0x80020009): An invalid argument was passed in the function call.
at System.RuntimeType.ForwardCallToInvokeMember(Strin g memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData)
at GroupwareTypeLibrary.DIGWAccount8.get_AccountPrope rty(AccountPropertiesConstants etAcctProp)
at ConnectorLibrary.ICEWrapper.GetFID(String& sCurFID)
[14123] (04/14 17:41:19):{0x960} {GWCO} {}
[14047] (04/14 17:41:19):{0x960} {GWCO} {thronsop} Login Failed, Username=thronsop
[34045] (04/14 17:41:19):{0x960} {GWCO} {thronsop} Logout admin user
[14095] (04/14 17:41:19):{0x960} {GWCO} {GWConnector} Mailstore test failed
[54002] (04/14 17:41:19):{0x960} {GWCO} {GWConnector} Terminating GWConnector

We found a fix for our issue. We needed to update our Groupwise servers to 7.0.2 HP or better to allow Groupwise client 7.0.3 to work with BES. I was using 7.0.1 on the BES to communicate with Groupwise 7.0 SP1 before and it worked with BES 4.1.3 but apparently won't with 4.1.4 or something with the upgrade broke it.

Now we're upgrading our post offices to 7.0.2 HP and have the 7.0.3 client installed on the BES and we're beginning to work again. One user on the first upgraded Groupwise server is working flawlessly but the other is not. He can only view old information. He can send email and it will appear in his Sent items in Groupwise but no new emails show up on his BB.

Outside of a complete wipe and reload is there anything else I can try? I've tried removing Desktop[Sync] and undeleting it, re-activating his BB, re-sending service books, and manual reconciliation. His BB is pointed at the right folder but nothing shows up save for a few old messages from the end of March that are deleted in Groupwise.

Thanks

Im at a loss as well, we did the upgrade about 2 weeks ago and only took about 45 minutes, we went from 4.1.3 and GW 6.5.7 to 4.1.4 and GW 7.03 without any issues at all, granted we had 7.03 already running on the PO's and 7.03 running on all of our client machines, it was the other way around for us, we saw several issues on the 6.5.7 side of the world trying to talk to 7.03 PO's.

Have you tried adding a new user with a new device to the system to test that? You may or may not have to wipe and reload, which i hope isnt that big of a deal.

B

We eventually just wiped the Blackberry and re-activated it and the issue was resolved. Hopefully that step isn't required for the other users who are on other PO's still waiting to be upgraded tonight.

I hope everything works without a hitch for ya.

B