When I select 'Exchange Custom', put in the server and a valid profile. Close Hyena and reopen I get this message...
"Unable to find DAPI.DLL for Exchange Integration........"
I have verified that this file exists, and is in all the appropriate paths, so Hyena should be able to see it. (I've also placed in the Hyena directory, my profiles, and in the system path.)
I launch Hyena with my Admin account using the runas command. Everything in Hyena works, except exchange and that error that pops up when starting. If I select to use Extensions for Exchange. ("The first Option in the Exchange GUI") I don't get the error, but I still do not have the ability to administer Exchange objects.
When I click on the license tab, it shows that we are licensed for Exchange and Terminal server.
Please advise how we can use our purchased functionality. This is happening on machines with fresh installs of Hyena, Installation of hyena while logged in as admins, and on upgrades. The ESM and Exchange tools are installed on all our machines as well.
Any help would be greatly appreciated.
Thanks,
Ken Wincel
"Unable to find DAPI.DLL for Exchange Integration........"
I have verified that this file exists, and is in all the appropriate paths, so Hyena should be able to see it. (I've also placed in the Hyena directory, my profiles, and in the system path.)
I launch Hyena with my Admin account using the runas command. Everything in Hyena works, except exchange and that error that pops up when starting. If I select to use Extensions for Exchange. ("The first Option in the Exchange GUI") I don't get the error, but I still do not have the ability to administer Exchange objects.
When I click on the license tab, it shows that we are licensed for Exchange and Terminal server.
Please advise how we can use our purchased functionality. This is happening on machines with fresh installs of Hyena, Installation of hyena while logged in as admins, and on upgrades. The ESM and Exchange tools are installed on all our machines as well.
Any help would be greatly appreciated.
Thanks,
Ken Wincel
Comment