Exceptional, Peter! I believe that did the trick. At least with the credentials and jcif errors. Thank you so much!
Now if I try to open a connection, it throws no error. But if I try to ExchangeCloseConnection() (or any other Exchange API call), it gives a "variable does not exist" error. I'm assuming that simply means the connection failed to open (bad/invalid parameters??). Or should ExchangeOpenConnection() throw an exception if it fails? Pretty much just executing per the examples at http://openbd.org/manual/?/plugin_exchange ExchangeOpenConnection( connection="connExchange",url="https://* subdomain.mydomain.com*/EWS/exchange.asmx", domain="*mydomain*",username=variables.username, password=variables.password ); ExchangeCloseConnection(connExchange); Results in *Variable CONNEXCHANGE does not exist.* Again, going to https://*subdomain.mydomain.com*/EWS/exchange.asmx is successful in a browser using the same username/password credentials. So if the connection is failing, I'm guessing it's the domain parameter, but that should be correct as well. On Wed, Feb 20, 2013 at 12:29 PM, Peter J. Farrell <[email protected]>wrote: > Professor said the following on 02/20/2013 11:19 AM: > > THANK YOU, Peter! > > Glad to help. See below... > > > I went to findjar and found and installed the jar that contained > jcifs.ntlmssp.Type1Message (jcifs-1.2.15.jar), and then it complains about > > java.lang.NoSuchMethodError: > jcifs.ntlmssp.Type3Message.(Ljcifs/ntlmssp/Type2Message;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;I)V > at net.aw20.msexchange.ntlm.JCIFSEngine.generateType3Msg(Unknown Source) > > > Which is were I got hung up when I tried this before... because > Type3Message should *also *be in the jcifs lib. ?? > Has the Type3Message method been deprecated? Do I need a version of > jcifs earlier than 1.2.15?? > > I don't think you have the right version of jcifs. I looked at the method > signature in: > > net.aw20.msexchange.ntlm.JCIFSEngine.generateType3Msg > > which has: > > Type3Message t3m = new Type3Message(t2m, password, domain, username, > workstation, 0); > > Version 1.2.15 doesn't support this method signature (the last argument > "0" is for flags) and hence why it is complaining it cannot find a method > because Java uses method overloading and this method in jcifs is overloaded > - see http://en.wikipedia.org/wiki/Method_overloading). > > I did find the right method signature in version 1.3.17 which is from > 2011. 1.2.15 is pretty old -- from 2008. Download this jar, delete the > older version, drop this jar in and then start Tomcat and Apache: > > http://jcifs.samba.org/src/jcifs-1.3.17.zip > > Let me know how it goes. > > -- > Peter J. Farrell > OpenBD Steering Committee / Mach-II Lead > Developerhttp://blog.maestropublishing.com > Identi.ca / Twitter: @maestrofjp > > Please do not send me Microsoft Office/Apple iWork documents. Send > OpenDocument instead! http://fsf.org/campaigns/opendocument/ > > -- > -- > online documentation: http://openbd.org/manual/ > http://groups.google.com/group/openbd?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Open BlueDragon" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en --- You received this message because you are subscribed to the Google Groups "Open BlueDragon" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
