A
Alexander Borodin
We're having some trouble getting Symantec ACT operational under Terminal
Services. The TS is running on Server 2003; this same problem has afflicted
us since TS2K though:
The ACT program itself launches fine, but the ACT word processor and email
"bridges" don't work. Here are some details:
1. Administrators are not affected, only regular users; so we're thinking it
's a permissions issue.
2. The error message we're getting when attempting to use the word
processor/email functionality are:
a. Failed to connect to word processor: ACT Word Processor; then:
b. The word processor driver is not running
We've turned on auditing in Group Policy for both successes and failures;
however the failure event logged doesn't give us much clue as to what's
going wrong:
----begin even
Object Open:
Object Server: SC Manager
Object Type: SC_MANAGER OBJECT
Object Name: ServicesActive
Handle ID: -
Operation ID: {0,9391572}
Process ID: 528
Image File Name: C:\WINDOWS\system32\services.exe
Primary User Name: AMFAPPSERVER2$
Primary Domain: AMFLLC
Primary Logon ID: (0x0,0x3E7)
Client User Name: carolyn
Client Domain: AMFLLC
Client Logon ID: (0x0,0x8E9134)
Accesses: DELETE
READ_CONTROL
WRITE_DAC
WRITE_OWNER
Connect to service controller
Create a new service
Enumerate services
Lock service database for exclusive access
Query service database lock state
Set last-known-good state of service database
Privileges: -
Restricted Sid Count: 0
Access Mask: 0xF003F
----end event
We've given a test user full access rights to both the ACT directory, and
the Symantec registry key under HKLU\Software; we've also tried granting
full access rights on HKLM\Software\Symantec as well, to no avail. Has
anyone gotten this ACT functionality to work successfully in Terminal
Services for regular users? Any input would be greatly appreciated.
Thank you,
-Alexander Borodin, Larry Prilliman
Available Mortgage Funding
Services. The TS is running on Server 2003; this same problem has afflicted
us since TS2K though:
The ACT program itself launches fine, but the ACT word processor and email
"bridges" don't work. Here are some details:
1. Administrators are not affected, only regular users; so we're thinking it
's a permissions issue.
2. The error message we're getting when attempting to use the word
processor/email functionality are:
a. Failed to connect to word processor: ACT Word Processor; then:
b. The word processor driver is not running
We've turned on auditing in Group Policy for both successes and failures;
however the failure event logged doesn't give us much clue as to what's
going wrong:
----begin even
Object Open:
Object Server: SC Manager
Object Type: SC_MANAGER OBJECT
Object Name: ServicesActive
Handle ID: -
Operation ID: {0,9391572}
Process ID: 528
Image File Name: C:\WINDOWS\system32\services.exe
Primary User Name: AMFAPPSERVER2$
Primary Domain: AMFLLC
Primary Logon ID: (0x0,0x3E7)
Client User Name: carolyn
Client Domain: AMFLLC
Client Logon ID: (0x0,0x8E9134)
Accesses: DELETE
READ_CONTROL
WRITE_DAC
WRITE_OWNER
Connect to service controller
Create a new service
Enumerate services
Lock service database for exclusive access
Query service database lock state
Set last-known-good state of service database
Privileges: -
Restricted Sid Count: 0
Access Mask: 0xF003F
----end event
We've given a test user full access rights to both the ACT directory, and
the Symantec registry key under HKLU\Software; we've also tried granting
full access rights on HKLM\Software\Symantec as well, to no avail. Has
anyone gotten this ACT functionality to work successfully in Terminal
Services for regular users? Any input would be greatly appreciated.
Thank you,
-Alexander Borodin, Larry Prilliman
Available Mortgage Funding