This is probably a bug, affects linux version 3.6.4 too. You have to edit openfire.xml file (don't know where it is on windows, probably inside openfire/conf dir) and add text marked with red:
<!-- root element, all properties must be under this element -->
<!-- Disable either port by setting the value to -1 -->
Then restart openfire and you should login as admin with your password (password is admin if setup was skipped).
Big thanks to mr. Oxymoron for this post: http://www.igniterealtime.org/community/message/179404#179404
I had the same problem as OP
I've added admin to the openfire.xml file --> now the admin console page cannot be displayed
If I change <setup> back to false the admin console comes back, but my configuration is (of course) gone
I'm really finding Openfire difficult to configure. Originally I wanted to authenticate against AD but after a few hours of struggling with "Base DN" and AD attribute names I've gone for something less ambitious. Is there a helpful "howto" which would walk me through getting _something_ up and running?
p.s. version 3.6.4 of Openfire running on WIndows Server 2003 SP2
p.p.s Have tried again and now get errors in the Openfire console, see attached textfile
openfire.txt.zip 872 bytes
your error said, that the database is used by other proces, is openfire server up?may be you should take alook at task manager and shut it down (the db) manually
The addition of the <admin>...</admin> to my openfire.xml fixed my problem. Thanks for the help!
This changing the .xml file did worked for me and I am able to login again. Thanks for the fix.
Is the firewall allowing openfire to pass?
Are you running it as a service or the gui app?
If the gui app are there any errors in the window?
I also have same problem, but i just change my config (openfire.xml) form "<setup>true</setup>" to false, and start the setup from beginig, and it work again.. just fine..
I had the same issue.
Would not let me log into the admin console.
looked at the settings int the db.
They were fine.
set the config file setting for setup to false.
ran through the configuration again with the settings.
I can now login to the admin console.
there is a bug somewhere.
Had the same problem, when running Openfire as a service under W2K3.
My workaround: stoped the service and started the admin console from the menue (with windows admin-account), then I was able to login...