|
Joined: Jun 2009
Posts: 4
Member
|
OP
Member
Joined: Jun 2009
Posts: 4 |
I recently installed emanager on an older XP box. No domain, all defaults in place. The software installed fine and I can connect to my CIX with no trouble. However, I receive an access denied error when trying to look at any setting in the menus. No matter waht, all I get is: Network eManager server reported this status: CixName=C-Path, Status=WBEM_E_ACCESS_DENIED When I clik OK to acknowledge the error I am brought back to the Equipment Details page and cannot do anything. Any advice as to what that error is from? Thank you!
|
|
|
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 2009
Posts: 4
Member
|
OP
Member
Joined: Jun 2009
Posts: 4 |
Typically that error is a permissions issue in the SQL database from what I understand. Is there anything that needs to be configured in IIS or SQL after installing with the defaults?
|
|
|
|
Joined: Dec 2007
Posts: 2,033
Moderator-Toshiba
|
Moderator-Toshiba
Joined: Dec 2007
Posts: 2,033 |
I think that was fixed with the default install on Network eManager
On earlier versions you had to manually allow IIS and M&M tools.
What version have you installed?
- Tony Ohio Data LLC Phone systems, data networks, firewalls and servers in Central Ohio. Some people aren't used to an environment where excellence is expected.
|
|
|
|
Joined: Jun 2009
Posts: 4
Member
|
OP
Member
Joined: Jun 2009
Posts: 4 |
Problem resolved. The error 'WBEM access denied' was caused, in my case, from COM + permissions. I had to go into Component services and adjust the permissions for the two EManager applications in COM + Applications. All worked great after those permissions were adjusted.
|
|
|
|
Joined: Aug 2009
Posts: 2
Member
|
Member
Joined: Aug 2009
Posts: 2 |
I have Windows XP and I had Network eManager V5.20B05 working before I left yesterday....I came in this morning and I get a Connection failed! Toshiba:WBEM_E_ACCESS_DENIED....All that happen between now and yesterday was my computer restarting....Can anyone help....I've tried this on several computers already....I've unistalled and reinstalled and it will work for a day...but the following day seems like i always get the WBEM_E_ACCESS_DENIED problem....Can anyone help? Thanks
|
|
|
|
Joined: Aug 2009
Posts: 1
Member
|
Member
Joined: Aug 2009
Posts: 1 |
Originally posted by JnelconCpath: Problem resolved. The error 'WBEM access denied' was caused, in my case, from COM + permissions. I had to go into Component services and adjust the permissions for the two EManager applications in COM + Applications. All worked great after those permissions were adjusted. Thanks! This is what fixed the problem. For those of you who are still having this issue, here are the step by step instructions. 1. Open Control Panel > Administrative Tools > Component Services 2. Expand Component Services > Computers > My Computer > COM+ Applications > 3. Right-Click IIS-{Default Web Site//Root/eManager} 4. Click Properties 5. Identity Tab 6. Next to "This User" click Browse 7. Enter a local admin account (typically eManagerUser, but any local admin account will work) 8. Type in the password/confirm password 9. Click Ok 10. Restart the machine This is what work for me. Hope it helps.
|
|
|
|
Joined: Jun 2009
Posts: 4
Member
|
OP
Member
Joined: Jun 2009
Posts: 4 |
I want to update this now that there are new operating systems and a new version of emanager. I ran into this same error when attempting to install the new version of Emanager on Windows 7. I didn't know what to do and I stumbled on this old thread form 2009 in which I helped solve the problem! I got caught up on this solution and went to work on Windows 7. I got emanager 5.2 to install ok, and after adding the site to the local intranet zone in Internet Explorer, I added the computer to the domain. Boom - I lost access. Turns out its the App Pool Identity that is the problem on a domain. During install, emanager uses the emanageruser to access the database and as the app pool identity in IIS. Once on a domain, that user account is worthless. here is the fix. In IIS, click the Application Pool Locate the emanager app pool, right click and edit advanced settings. From there, change the app pool identity to the local system account. That's it. I can now access this form a web browser anywhere in the network (domain). There are no longer any COM Plus Applications listed in Component Services with version 5.2.
|
|
|
Forums84
Topics94,262
Posts638,693
Members49,757
|
Most Online5,661 May 23rd, 2018
|
|
0 members (),
114
guests, and
83
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|