| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 237.1 | Things to try | CAMINO::VINELEAF | | Tue Jan 14 1997 21:22 | 34 |
| 237.2 | Service Pack 1 solved the problem | OSTV03::K_HORIE | | Thu Jan 16 1997 09:22 | 11 |
| 237.3 | logon/logoff problem | OSTV03::K_HORIE | | Mon Jan 27 1997 10:17 | 27 |
| Hi, I'm back.
Yes, I have been able to start TPsystem as a Windows service with
ACMSxp_T31, Intel WNT V4.0 (Build 1381: Service Pack 1) and DCE V1.1b.
But, when I try to logoff, leaving the TPsystem running, the logon-box
doesn't appear. If I stop the TPsystem from the other box, the logon-box
appears.
I can not logoff without stopping the TPsystem.
There is another problem.
If I configure the TPsystem to start automatically during the OS
starting-up, I can not logon.
I enter the username and password, press the OK button and everything
hangs. If I stop the TPsystem from the other box, the logon sequence
continues.
I can not logon either, without stopping the TPsystem.
Has anyone succeeded in logging-on/off while running a TPsystem as a
Windows service ?
Kouji Horie
|
| 237.4 | One data point... | CAMINO::VINELEAF | | Mon Jan 27 1997 16:44 | 16 |
|
Well, I just tried it, and I was able to both log off when the TPcontroller
is running as a service, and to log on when the TP system automatically
started as a result of rebooting my system. So it seems that works in some
cases. We just have to figure out what's different about yours.
Please provide more information about the TPsystem - do you have
autostart servers? What kind? How many? Is the username for the TPcontroller
local to the box or is it part of a domain? Is DCE having any problems
starting up? Is there anything in the event log file? How about the ACMSxp
log file?
I am running with a newer version of ACMSxp and DCE V1.1C SSB. That may
make a difference, but I think that what you want to do should work.
Ken
|
| 237.5 | DCE problem ? | OSTV03::K_HORIE | | Tue Jan 28 1997 10:27 | 231 |
|
Ken,
Thanks for your reply.
>do you have autostart servers? What kind? How many?
I have only just made a TPsystem. So, the TPcontroller and the event
server should be running. There is no other ACMSxp server.
> Is the username for the TPcontroller local to the box or is it part of a
>domain?
The box is not part of any domain. Thus the username is local to the
box.
>Is DCE having any problems starting up? Is there anything in the event log
>file?
An error occures. ( I guess DCEstart attempts to start RPCSS. )
But, finally all DCE services start.
The following messages have remained in the event log.
DCEstart Information
DCE services are being started..
DCEstart Error
Unable to start service : An instance of the service is already running
DCEstart Information
Nt service started: Sec_Clientd.
sec_clientd Information
Service started as requested by service manager.
DCEstart Information
Nt service started: Cdsadv.
CDS Advertiser Information
CDS Advertiser event; Service started as requested by service control
manager.
DCEstart Information
Nt service started: Dtsd.
dtsd Information
Service started as requested by service manager.
DCEstart Information
DCE services started successfully..
>How about the ACMSxp log file?
Please see the following ACMSxp log. The TPsystem itself has started
successfully. Finally, I have stopped the TPsystem from the other box
because I could not logon.
(BTW, time stamp of ACMSxp log file on WNT is GMT time. On VMS, it's JST
time. Do you know how to configure to set the time stamp to localtime?
I have set TZ enviroment variable as JST-9. If TZ were not set,
acms_start_tpsystem.exe would not work.)
********************************************************************************
ACMS Log Report
service_test_default.log
1997-01-28-09:26:20.186
********************************************************************************
SELECTION CRITERIA:
Before:
Since:
Format: SYSTEM
Type: audit fault trace security status
Principal:
TPSystem:
Server:
Interface:
Procedure:
Request ID:
Device:
********************************************************************************
********************************************************************************
USER: k_horie
TIME: 1997-01-28-08:49:49.155
POSTED BY: TPController Process
PID: 89
TYPE: status
OLD STATE: not started
NEW STATE: starting
ENTITY CLASS: TPSystem
TPSystem: service_test
********************************************************************************
USER: k_horie
TIME: 1997-01-28-08:49:58.198
POSTED BY: TPController Process
PID: 89
TYPE: status
OLD STATE: not started
NEW STATE: starting
ENTITY CLASS: Server
TPSystem: service_test
Server: acms_event_svr
********************************************************************************
USER: k_horie
TIME: 1997-01-28-08:50:03.505
POSTED BY: TPController Process
PID: 89
TYPE: status
OLD STATE: not started
NEW STATE: starting
ENTITY CLASS: Process
TPSystem: service_test
Server: acms_event_svr
Process: 113
********************************************************************************
USER: k_horie
TIME: 1997-01-28-08:50:04.347
POSTED BY: TPController Process
PID: 89
TYPE: status
OLD STATE: starting
NEW STATE: started
ENTITY CLASS: TPSystem
TPSystem: service_test
********************************************************************************
USER: k_horie
TIME: 1997-01-28-08:50:25.898
POSTED BY: Server Process
PID: 113
TYPE: status
OLD STATE: starting
NEW STATE: started
ENTITY CLASS: Process
TPSystem: service_test
Server: acms_event_svr
Process: 113
********************************************************************************
USER: k_horie
TIME: 1997-01-28-09:21:48.055
POSTED BY: TPController Process
PID: 89
TYPE: status
OLD STATE: started
NEW STATE: stopping
ENTITY CLASS: TPSystem
TPSystem: service_test
********************************************************************************
USER: k_horie
TIME: 1997-01-28-09:21:48.095
POSTED BY: TPController Process
PID: 89
TYPE: status
OLD STATE: started
NEW STATE: stopping
ENTITY CLASS: Server
TPSystem: service_test
Server: acms_event_svr
********************************************************************************
USER: k_horie
TIME: 1997-01-28-09:21:48.155
POSTED BY: Server Process
PID: 113
TYPE: status
OLD STATE: started
NEW STATE: stopping
ENTITY CLASS: Process
TPSystem: service_test
Server: acms_event_svr
Process: 113
********************************************************************************
USER: k_horie
TIME: 1997-01-28-09:21:51.770
POSTED BY: TPController Process
PID: 89
TYPE: status
OLD STATE: stopping
NEW STATE: not started
ENTITY CLASS: Process
TPSystem: service_test
Server: acms_event_svr
Process: 113
********************************************************************************
USER: k_horie
TIME: 1997-01-28-09:21:54.304
POSTED BY: TPController Process
PID: 89
TYPE: status
OLD STATE: stopping
NEW STATE: not started
ENTITY CLASS: Server
TPSystem: service_test
Server: acms_event_svr
********************************************************************************
USER: k_horie
TIME: 1997-01-28-09:21:54.584
POSTED BY: TPController Process
PID: 89
TYPE: status
OLD STATE: stopping
NEW STATE: not started
ENTITY CLASS: TPSystem
TPSystem: service_test
>I am running with a newer version of ACMSxp and DCE V1.1C SSB.
I suspect that DCE V1.1B does not completely support WNT4.0. I'm going to
try DCE V1.1C as soon as it is available.
|
| 237.6 | | CAMINO::VINELEAF | | Tue Jan 28 1997 12:07 | 17 |
| Your test configuration is identical to mine.
> Do you know how to configure to set the time stamp to localtime?
Check here:
Control Panel
Date/Time
Time Zone Tab
> I suspect that DCE V1.1B does not completely support WNT4.0. I'm going to
> try DCE V1.1C as soon as it is available.
I wouldn't surprise me. There are significant differences between
V1.1B and V1.1C.
Ken
|
| 237.7 | Time Zone | OSTV03::K_HORIE | | Tue Jan 28 1997 21:53 | 49 |
| >> Do you know how to configure to set the time stamp to localtime?
>
>Check here:
>
>Control Panel
> Date/Time
> Time Zone Tab
Yes, it has already been the correct time zone. [(GMT+09:00) Tokyo, Osaka,...]
The time stamp of acmsadmin command output is also GMT on WNT.
Please see the following. I typed a same command on WNT and on VMS at almost
same time.
on WNT
D:\>acmsadmin show tpsystem /.:/acmsxp_jit133/hello
TPsystem /.:/acmsxp_jit133/hello
AT 1997-01-29-02:08:57.598+00:00I-----
Show successful
D:\>
on VMS Alpha
TEPCO> acmsadmin show tpsystem /.:/acmsxp_jit133/hello
TPsystem /.:/acmsxp_jit133/hello
AT 1997-01-29-11:08:56.246+09:00I-----
Show successful
TEPCO>
I have checked two other WNT boxes (Alpha/Intel, WNT3.51, ACMSxpT3.1, DCE1.1B),
the acmsadmin time stamp on these boxes were GMT at that time.
Kouji Horie
|
| 237.8 | failed again with DCE1.1C | OSTV03::K_HORIE | | Thu May 15 1997 23:29 | 172 |
| Unfortunately, I'm back.
I've upgrade my intel PC with DCE1.1C(with ECO DCENT11CE01), ACMSxp V30 and
WNT 4.0 workstation service pack 2 and tried to start a tpsystem as a service
again.
I can start a tpsystem from the control panel as a service, but I can not
start it automatically at system boot time. The tpsystem logfile shows that
the TPController process could not access the namespace. It seems like that
the TPController process started before DCE servers started. However, in the
registory of the tpsystem service (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet-
\Services\ACMSxp_tpsys1), the dependency between the services is set as
DependsOnService:REG_MULTI_SZ:DCEStart.
I have another problem. As same as written in *.3, when I try to logoff
leaving the TPsystem running, the logon-box doesn't appear. If I stop the
TPsystem from the other box, the logon-box appears.
Any information about these problem whould be appreciated.
These problems is very serious for our project.
We need you help!
I created the tpsystem as follows.
C:\>acms_create_tpsystem
ACMSxp for Windows NT V3.0
TP system name[]: /.:/acmsxp/tpsys1
Default namespace profile [/.:/acmsxp/tpsys1_profile]:
TPsystem work directory [C:\ACMSxp\tpsys1]:
DCE principal name to run TP system under []: tepco
Key directory [C:\ACMSxp\tpsys1]:
Create a Windows NT service for TP system [y|n] (n)? y
Windows username to run TP system under: tepco
Password []:
Should the TPsystem automatically startup when the system starts [y|n] (n)? y
Creating TPsystem with:
TPsystem name: /.:/acmsxp/tpsys1
default namespace profile: /.:/acmsxp/tpsys1_profile
work directory: C:\ACMSxp\tpsys1
DCE principal name: tepco
Key file directory: C:\ACMSxp\tpsys1
Create with Encina support: no
Create as Windows service: yes
Windows username for service: tepco
Autostart TPsystem when
system starts: yes
Is this OK [y|n] (n)? y
Checking for the name space directory for the TP system:
/.:/acmsxp
Created directory C:\ACMSxp\tpsys1
Putting TP system into TP system list
Creating the configuration database
Creating TPsystem /.:/acmsxp/tpsys1 in cdb and namespace
Creating the Windows NT service for the TP system
TPsystem tpsys1 successfully created
C:\>
This is the content of the tpsystem log file.
********************************************************************************
ACMS Log Report
tpsys1_default.log
1997-05-16-01:36:05.153
********************************************************************************
SELECTION CRITERIA:
Before:
Since:
Format: SYSTEM
Type: audit fault trace security status
Principal:
TPSystem:
Server:
Interface:
Procedure:
Request ID:
Device:
********************************************************************************
********************************************************************************
USER: tepco
TIME: 1997-05-16-01:33:04.959
POSTED BY: TPController Process
PID: 94
TYPE: status
OLD STATE: not started
NEW STATE: starting
ENTITY CLASS: TPSystem
TPSystem: tpsys1
********************************************************************************
USER: tepco
TIME: 1997-05-16-01:33:11.338
POSTED BY: TPController Process
PID: 94
TYPE: status
OLD STATE: not started
NEW STATE: starting
ENTITY CLASS: Server
TPSystem: tpsys1
Server: acms_event_svr
********************************************************************************
USER: tepco
TIME: 1997-05-16-01:33:11.518
POSTED BY: TPController Process
PID: 94
TYPE: fault
EXECUTION CONTEXT INFORMATION:
TPSystem: /.:/acmsxp/tpsys1
SEVERITY: error
rpc MESSAGE TEXT: entry not found ( dce / rpc )
tps MESSAGE TEXT: %TPS-E-SVRNOTSTARTED, Server not started
********************************************************************************
USER: tepco
TIME: 1997-05-16-01:33:11.518
POSTED BY: TPController Process
PID: 94
TYPE: status
OLD STATE: starting
NEW STATE: not started
ENTITY CLASS: Server
TPSystem: tpsys1
Server: acms_event_svr
********************************************************************************
USER: tepco
TIME: 1997-05-16-01:33:11.538
POSTED BY: TPController Process
PID: 94
TYPE: fault
EXECUTION CONTEXT INFORMATION:
TPSystem: /.:/acmsxp/tpsys1
SEVERITY: fatal
tps MESSAGE TEXT: %TPS-F-INVNSDIRNAME, Invalid namespace directory name
********************************************************************************
USER: tepco
TIME: 1997-05-16-01:33:11.538
POSTED BY: TPController Process
PID: 94
TYPE: fault
EXECUTION CONTEXT INFORMATION:
TPSystem: /.:/acmsxp/tpsys1
SEVERITY: fatal
tps MESSAGE TEXT: %TPS-F-INVNSDIRNAME, Invalid namespace directory name
********************************************************************************
USER: tepco
TIME: 1997-05-16-01:33:11.548
POSTED BY: TPController Process
PID: 94
TYPE: status
OLD STATE: starting
NEW STATE: stopping
ENTITY CLASS: TPSystem
TPSystem: tpsys1
|
| 237.9 | Please advise me! | OSTV03::K_HORIE | | Wed May 21 1997 08:04 | 2 |
| These problems are critical for our project with a client.
Any help would be appreciated.
|
| 237.10 | | CAMINO::VINELEAF | | Wed May 21 1997 18:41 | 3 |
| We are looking into this problem and will get back to you
as soon as possible.
|
| 237.11 | English WNT4 is good. | OSTV03::K_HORIE | | Thu May 22 1997 08:54 | 11 |
| Today, I installed the English version of WNT4 in an intel PC and
I confirmed that I could logoff/logon remaining a tp-system running
as a service program.
It might be a Japanese version of WNT4 specific problem.
If so, it's a very complicated problem for us.
If you have any idea about something I should try, please advise me.
Kouji Horie
|