home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
Products
IR Server Suite (IRSS)
tv3 external channel changer
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="and-81" data-source="post: 139550" data-attributes="member: 11844"><p>Hey again,</p><p></p><p>It doesn't matter that event.exe is part of girder, it's a separate executable. and it's being run by the "System" user.</p><p></p><p>When you are in the configuration app you are running in your user account, not the system user account. This is the difference between the configuration app and the TV service. It could be that whatever method of Inter-Process Communication the Event.exe uses is not accessible by a "System" account process due to the lower privileges that the System process has. This has been my experience with Named Pipes IPC for example, as this is something I am working with at the moment on a new set of plugins and apps.</p><p></p><p>I can't say for sure that this is the cause of your problems, but it makes sense.</p><p></p><p>Try this:</p><p></p><p>Go to Start Menu, Run ...</p><p>Type "services.msc" and click ok.</p><p>Locate the TV Service in the list and right-click it, select Properties.</p><p>Under the "Log In" tab try the following (one at a time):</p><p></p><p>1. Try selecting "Allow service to interact with desktop".</p><p></p><p>If that doesn't work try:</p><p></p><p>2. Try selecting "This account" (radio button) and then enter your user account details and having the service run under your account.</p><p></p><p>You may need to reboot on each of these attempts to ensure the change has taken effect.</p><p></p><p>Give that a go.</p><p></p><p>Thanks,</p></blockquote><p></p>
[QUOTE="and-81, post: 139550, member: 11844"] Hey again, It doesn't matter that event.exe is part of girder, it's a separate executable. and it's being run by the "System" user. When you are in the configuration app you are running in your user account, not the system user account. This is the difference between the configuration app and the TV service. It could be that whatever method of Inter-Process Communication the Event.exe uses is not accessible by a "System" account process due to the lower privileges that the System process has. This has been my experience with Named Pipes IPC for example, as this is something I am working with at the moment on a new set of plugins and apps. I can't say for sure that this is the cause of your problems, but it makes sense. Try this: Go to Start Menu, Run ... Type "services.msc" and click ok. Locate the TV Service in the list and right-click it, select Properties. Under the "Log In" tab try the following (one at a time): 1. Try selecting "Allow service to interact with desktop". If that doesn't work try: 2. Try selecting "This account" (radio button) and then enter your user account details and having the service run under your account. You may need to reboot on each of these attempts to ensure the change has taken effect. Give that a go. Thanks, [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Products
IR Server Suite (IRSS)
tv3 external channel changer
Contact us
RSS
Top
Bottom