|
|
|
|
Joined: Dec 2010
Posts: 681
Member
|
|
Member
Joined: Dec 2010
Posts: 681 |
Hey guys,
Hopefully someone can give me a good answer to this. I have been pulling my hairs for 5 days on this issue.
I have a client who has a 7200 and we put in a Windows 2008 Server R2 to run the Samsung CTI Applications. It has OS Link V3, Dataview and Easyset V3 running on the pc. The programs are all configured in accordance with Samsung's wonderful litterature. I got IIS 7.0 running on the server. I can access the dataview page, but when I login it gives me 500 internal server error. Does anyone know what could be wrong?
If you happen to have any literature or anything to help it would be highly appreciated.
Thanks,
Cubano
|
|
|
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: Jan 2005
Posts: 340
Member
|
|
Member
Joined: Jan 2005
Posts: 340 |
This is for server 2003, I dont know if it will help or not. But here ya go! Windows 2003 prohibits the IUSR from being able to access COM objects (a specific type of resource used by Windows) and EasySet V3 uses a COM object to talk to the switch. So when a user connects to the EasySet server they are logged in as the IUSR and then prevented from talking to the switch. This wasn’t always this way, it was changed in a recent patch released by Microsoft.
Te solution to this problem is to force people who connect to the server to log in with a local admin account. The solution is to change the anonymous access from IUSR to be a local admin account. *Please* be aware that doing this is a security threat, but it is Microsoft’s recommended strategy to fix the problem. What it means is that anyone connecting to EasySet gets logged in as an admin on the server. There exists the potential for a malicious user to somehow exploit this admin account and do Bad Things™.
Due to a recent change to Windows 2003 we highly recommend using a PC running an operating system other than Windows 2003 when installing OfficeServ EasySet. We understand that this is not always possible, so for installations that must use Windows 2003 the following change MUST be made to the server after installation of EasySet to prevent a [Login Error] from being displayed.
Click Start
Click Administrative Tools
Click Internet Information Services (IIS) Manager
Expand the computer name
Expand Web Sites
Expand Default Web Site
Right-click EasySet
Click Properties
Click the Directory Security tab
Click the Edit… button at the top of the window under “Authentication and access controlâ€Â
Click Browse
In the text box type administrator
Click Check Names (the name should change to be underlined, indicating the user has been found)
Click OK
In the Password box type the password for the PC’s Administrator account
Hit enter
Retype the password
Click OK
Click OK again
Close the IIS manager
Click Start
Click Run…
Type iisreset
Click OK
Once the IIS reset has completed you may now log in to EasySet.
The problem is created by Microsoft, and they themselves recommend fixing it in this way.
|
|
|
|
|
Joined: Jan 2005
Posts: 340
Member
|
|
Member
Joined: Jan 2005
Posts: 340 |
This is for server 2003, I dont know if it will help or not. But here ya go! Windows 2003 prohibits the IUSR from being able to access COM objects (a specific type of resource used by Windows) and EasySet V3 uses a COM object to talk to the switch. So when a user connects to the EasySet server they are logged in as the IUSR and then prevented from talking to the switch. This wasn’t always this way, it was changed in a recent patch released by Microsoft.
Te solution to this problem is to force people who connect to the server to log in with a local admin account. The solution is to change the anonymous access from IUSR to be a local admin account. *Please* be aware that doing this is a security threat, but it is Microsoft’s recommended strategy to fix the problem. What it means is that anyone connecting to EasySet gets logged in as an admin on the server. There exists the potential for a malicious user to somehow exploit this admin account and do Bad Things™.
Due to a recent change to Windows 2003 we highly recommend using a PC running an operating system other than Windows 2003 when installing OfficeServ EasySet. We understand that this is not always possible, so for installations that must use Windows 2003 the following change MUST be made to the server after installation of EasySet to prevent a [Login Error] from being displayed.
Click Start
Click Administrative Tools
Click Internet Information Services (IIS) Manager
Expand the computer name
Expand Web Sites
Expand Default Web Site
Right-click EasySet
Click Properties
Click the Directory Security tab
Click the Edit… button at the top of the window under “Authentication and access controlâ€Â
Click Browse
In the text box type administrator
Click Check Names (the name should change to be underlined, indicating the user has been found)
Click OK
In the Password box type the password for the PC’s Administrator account
Hit enter
Retype the password
Click OK
Click OK again
Close the IIS manager
Click Start
Click Run…
Type iisreset
Click OK
Once the IIS reset has completed you may now log in to EasySet.
The problem is created by Microsoft, and they themselves recommend fixing it in this way.
|
|
|
|
|
Joined: Jun 2006
Posts: 3,004 Likes: 4
Moderator-Samsung
|
|
Moderator-Samsung
Joined: Jun 2006
Posts: 3,004 Likes: 4 |
At the back of the easyset and dataview user guides are troubleshooting steps.
You need to install iis 6 compatibility and enable parent paths from memory
|
|
|
|
Forums84
Topics94,562
Posts640,149
Members49,864
| |
Most Online5,661
May 23rd, 2018
|
|
|
0 members (),
13
guests, and
89
robots. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|
|
