Openfire 3.5.0 AD integration issues with Windows 2000 Advanced Server

I have a Win 2000 Adv. Server running with latest patches. I tried to

install Openfire 3.5.0 and I wanted AD integration, I did it in the past with a 2003

server and everything worked perfectly. However on Windows 2000 Adv. Server I

cannot pass from the setup on AD information details.

The problem: when testing the account to authenticate I get the following

error:

Test: connection settings

status: Error

Erro authenticating with LDAP server. Check supplied credentials

The following is the warning log:

2008.04.22 21:44:29 Error when trying to update to new name

java.sql.SQLException: Table not found in statement [UPDATE jiveVersion SET

name=‘openfire’ WHERE name=‘wildfire’]

at org.hsqldb.jdbc.Util.throwError(Unknown Source)

at org.hsqldb.jdbc.jdbcPreparedStatement.<init>(Unknown Source)

at org.hsqldb.jdbc.jdbcConnection.prepareStatement(Unknown Source)

at

org.jivesoftware.database.AbstractConnection.prepareStatement(AbstractConnection .java:36)

at org.jivesoftware.database.SchemaManager.updateToOpenfire(SchemaManager.java:298 )

at

org.jivesoftware.database.SchemaManager.checkOpenfireSchema(SchemaManager.java:6 6)

at

org.jivesoftware.database.DbConnectionManager.setConnectionProvider(DbConnection Manager.java:467)

at org.jivesoftware.openfire.admin.setup.setup_002ddatasource_002dsettings_jsp._js pService(setup_002ddatasource_002dsettings_jsp.java:155)

at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491)

at

org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.jav a:1074)

at

com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118 )

at

com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)

at

org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.jav a:1065)

at org.jivesoftware.util.LocaleFilter.doFilter(LocaleFilter.java:65)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.ja va:1065)

at

org.jivesoftware.util.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFi lter.java:41)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.ja va:1065)

at org.jivesoftware.admin.PluginFilter.doFilter(PluginFilter.java:69)

at

org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.jav a:1065)

at org.jivesoftware.admin.AuthCheckFilter.doFilter(AuthCheckFilter.java:98)

at

org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.jav a:1065)

at

org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)

at

org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185)

at

org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)

at

org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689)

at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391)

at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollect ion.java:146)

at

org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)

at

org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)

at org.mortbay.jetty.Server.handle(Server.java:285)

at

org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:457)

at

org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.ja va:751)

at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:500)

at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)

at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:357)

at

org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:329)

at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)

I have checked all details of the cn path and everything is

correct. Account is correct, I tried with different administrators

accounts but same error. The server is running the lates updates and

Java version 1.6.0.

I also tried with an old version of Openfire, ver. 3.3.1 but same error.

My doubt is if Openfire supports windows 2000 AD

or not because on Windows 2003 works like a charm. I tried to find this

specifications on the web page but couldnt find it at all.

And if its supported any idea of what could be the problem?

Thanks

Francisco

problem solved

A bit late to reply - but it looks like the problem was with the database, not the AD settings directly, is that right?