|
没发现什么好东西) ?. o6 U8 Y7 F- S7 e) N: @5 t- j
: I, m1 G$ B" q2 X" p' l( ?& m
8 s& _) U1 H8 ]1 ZTechNote MG527386, 8/25/10 (0 votes)
- o- s2 Q' _& L. O
8 Y9 B J' `4 a* ]+ \Rate This TechNote
9 c. h5 u5 w# n/ _* A& H# T" g, bHow can we improve this?; P) W; C& F$ o" R
Low High
/ p5 o0 y3 b2 s4 H5 f5 DOn a scale of 1 to 5: $ H$ W4 p1 `# [) C6 G6 s$ G
1 2 3 4 5
3 f4 {% F: b" Q! T8 i
+ }2 [0 n/ I& Y/ t! i2 gWas this content helpful No Yes
8 |$ t B n% {! e9 g" z/ F8 [6 F( i3 b2 j- R5 M5 ~
# ]- W) J- D5 t- e9 D
0 S" S9 X1 t' ?5 l C7 K3 ^4 _+ o+ a1 A" C& I9 D+ w
Connection Failed. Could not connect to VeSys Manager
+ `; A+ z7 s# R! m/ p& ASymptoms
2 f9 Z, E- d" x4 {5 LIn new install of 2010.1, getting error when launching client.8 p( [9 {0 H" {0 n7 Q
8 W; T3 l" [ O
* g9 n6 I# X: iConnection Failed. Could not connect to VeSys Manager.' c- _; G/ l* C) O) Y/ W7 [: \
) X9 F) G) o4 V0 _' t u3 `( N8 M
Causes- [: }0 [* _3 }6 n
Installed as local.8 M5 d, M9 O+ }0 Q6 V. \' E4 R
TechNote ID* @! n, b- Z" z3 n. L! ]6 g
MG527386' U1 m/ p; T$ M$ h" S8 F
TechNote Type
' L' u9 f$ x/ t( u: y( B1 {+ a: kSolution3 L [ i& ]4 E0 C
Updated
% u) s) f4 Q2 M: @ K/ j8/25/10
/ U# ~- a5 b3 H' L ZProducts( F' p8 V' h7 J8 T( `( u
VeSys Design
, K# X6 O5 y8 w8 w8 w
/ M) N, Y. y/ p1 N. dVeSys Harness/ R+ }1 F( V; M6 l4 m$ i( o
7 |& I! j* f8 i% \" GVeSys Components. f& n: ]# g: L# R- V
# }. P" _$ `! C6 K8 V7 \1 C2 ?VeSys Engineer
; g% U5 a" d5 c7 v6 c8 @% ~) L+ [ n% F$ [- c
VeSys Integration0 G( b) E5 U5 _1 J2 j
, a0 a! T5 H* C, I6 H3 Q! WVeSys Service
- b$ f& D0 ~3 I: v% S& W: Q5 {& G8 ]( T' W$ W
Environment" R1 ?! D/ o$ V7 d5 L5 c! p
Solution4 C" i- I( \3 R5 ?
In vesysmanagerprops.xml change the connection from "local" to "remote".
; W9 }# }% |/ V5 ~0 E5 z5 P
/ i+ D* _8 Q3 o- Sthe file is located in the config folder where VeSys Manager is installed. |
|