|
|
Joined: Sep 2003
Posts: 39
Member
|
Member
Joined: Sep 2003
Posts: 39 |
Emanager will connect to phone equipment but when you click on the station equipment on the drop down menu it does not bring up the stations, it says it cannot find the database or access is not allowed. I have had a rather smart SQL server type individual check this out and he could not find out what is causing the problem. Any gurus out there that have seen this issue.
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Jun 2005
Posts: 2,714 Likes: 7
Member
|
Member
Joined: Jun 2005
Posts: 2,714 Likes: 7 |
My general thought is that if there was a database issue, then you should not even get as far as connecting to the PBX. Usually when I have an issue with SQL, then I can't even log into eManager, much less connect to the PBX.
The only thing that has worked for me is to reinstall Network eManager. If that doesn't work then uninstall the previous version, delete folder, reboot, then reinstall.
I am assuming that you are using the Windows 10 version of eManager NetworkeManagerV5.20BW10, not the Windows 7 version NetworkeManagerV5.20B26.
|
|
|
|
Joined: Sep 2003
Posts: 39
Member
|
Member
Joined: Sep 2003
Posts: 39 |
David: Thank you for responding to the problem. My SQL people are telling me the same thing. You are getting to the database but after that nothing works. I am using the V5.20BW10 version for Windows 10 but interesting enough when the emanager opens up it displays a V5.20BW20 version in the display bar at the bottom. The version I downloaded from Toshiba was the V5.20BW10 so I am not quite sure why this is not being displayed at the bottom. Any way I will uninstall everthing as you indicated, delete folder and reboot. Then reinstall. I think I have already done this probably twice but maybe it will be third time lucky.
|
|
|
|
Joined: Jan 2010
Posts: 937 Likes: 2
Moderator-Toshiba
|
Moderator-Toshiba
Joined: Jan 2010
Posts: 937 Likes: 2 |
I had success installing eManager onto the early release of Windows 10 with the v5.20BW10 but on recent installs it does not work. You have to add the WMI app and WMI SNMP app manually as they are not part of Windows add/remove components anymore. I still was unable to get the eManager to work but as you said it does connect but doesn't communicate properly.
I just run the software on a virtual Windows 7 installation and it work fine.
Regards Carl
|
|
|
|
Joined: Jun 2005
Posts: 2,714 Likes: 7
Member
|
Member
Joined: Jun 2005
Posts: 2,714 Likes: 7 |
I had success installing eManager onto the early release of Windows 10 with the v5.20BW10 but on recent installs it does not work. You have to add the WMI app and WMI SNMP app manually as they are not part of Windows add/remove components anymore. I still was unable to get the eManager to work but as you said it does connect but doesn't communicate properly.
I just run the software on a virtual Windows 7 installation and it work fine. Thanks. I figured out the SNMP, but didn't know about WMI SNMP. After trying to follow directions to install SNMP through Powershell, I found out that you can add those under Apps and Features - Optional features. When I installed Network Emanager on my laptop, SNMP was still under the Windows Features (under Programs and Features). So far Windows 10 works OK. I have a few odd things like error messages that don't popup correctly. I have a Virtual Windows XP for things that won't work on Windows 10;
|
|
|
Forums84
Topics94,384
Posts639,240
Members49,799
|
Most Online5,661 May 23rd, 2018
|
|
1 members (Yoda),
99
guests, and
105
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|