|
没发现什么好东西& V8 B( s9 J1 v# `. U: _2 L: e
' Y3 k/ ] S8 N& u( d& m+ o' |& `; d
; E+ e1 g# P3 E+ m! aTechNote MG527386, 8/25/10 (0 votes)
0 }% H. m O" ]0 f' H6 L
# l; n, ?: q8 Z& D$ k# @0 HRate This TechNote
1 U8 _* N- R& K$ N: d) Y. {How can we improve this?) t9 o& W( L8 G! M$ ~/ |1 K
Low High
& M W6 |6 r- L1 N( r! c" NOn a scale of 1 to 5: 6 H9 V4 r9 X) }) P: f
1 2 3 4 5 - {2 S# r7 O, {0 \6 ?6 `+ s
$ T# G7 J8 ^4 u! n9 CWas this content helpful No Yes
3 b$ D9 G5 x; L1 C
( E: M( L/ C2 A) ] + u3 R9 ^$ E4 e0 w9 U3 U) R* z
6 F6 u4 [" X4 W3 r
# _7 j0 S' w, w* D) v9 @
Connection Failed. Could not connect to VeSys Manager1 D9 L# `& t: F
Symptoms
" l; _1 x/ J+ e6 Z! b+ U* PIn new install of 2010.1, getting error when launching client.5 \' ]+ G# B" t! r7 T3 \ F
5 W+ C8 ~- B+ b' ?. K6 S3 U
; B% C7 X. f" q; l, W( pConnection Failed. Could not connect to VeSys Manager.
9 p' q9 |* H9 {7 ]3 u0 T1 X$ D! e
- M3 W. ^( i7 R+ nCauses
% y5 a+ K% a2 Q" d1 f. K9 _Installed as local./ C: ?% t4 `9 X9 ?) \0 u \6 H
TechNote ID
4 f5 e4 H8 c' Y2 `3 P/ n* s6 kMG527386: q4 O' J/ G) V
TechNote Type
8 O& u7 Z$ B* V4 T7 d1 o. R1 Z. eSolution
1 x0 |+ y+ g2 v$ t' @Updated- u% i6 m; k7 ^% v1 l2 q- c
8/25/10
6 x2 n% l* c1 K( a, x1 S+ Y+ p) oProducts: a0 ~- v* L# _. i9 g5 |6 w
VeSys Design
8 d) `; C2 d9 t: B* }* Q/ d' t/ \# w8 H2 a3 c" @2 N5 n! ^( n
VeSys Harness! Z; i. D; L+ Y& h7 X
- C9 R1 c" `" M3 H: o" S) ] f8 R
VeSys Components
) j L& A7 b8 b6 T( @, L5 @
X* W$ R, c7 ^# [; i- |9 ?VeSys Engineer
2 ~% E/ S! F1 h8 X
: d; U: b* s' j1 hVeSys Integration2 R E" _! R, f' _
2 O5 K6 Z$ d0 G) Y+ q
VeSys Service0 z9 X: N) w7 B( {
0 ], M+ X2 v7 M" ~5 }6 k% ]Environment
9 e, \8 h6 G) K+ rSolution
0 W! t2 H# ?$ u. FIn vesysmanagerprops.xml change the connection from "local" to "remote".4 d) e: S+ f; ?' q4 A# X, ?8 o
6 r e, y6 I0 b0 u% Z
the file is located in the config folder where VeSys Manager is installed. |
|