|
没发现什么好东西
) u+ S4 w$ S6 @- R1 Z+ {0 K: K# f8 |6 U6 V2 z7 Q
: O5 U" C. Z" m( ]
TechNote MG527386, 8/25/10 (0 votes) 1 `3 M* `! I/ k/ g$ v& a' i
$ y( l2 o- I# ?7 c
Rate This TechNote
9 l) _& o. l M0 `1 X, lHow can we improve this?
' G& S2 w% [3 w* M Low High
. m3 O o9 X2 X! U4 U3 ~* h, }On a scale of 1 to 5:
* a* {2 q; D j) v2 P 1 2 3 4 5 ; K" F7 }5 |& g8 H& X
2 o* s+ w m! i9 U" _8 M
Was this content helpful No Yes 5 Y: d; x+ B! d
& ^7 w6 D& O$ Q
4 h( N1 v1 y" W9 [1 g
$ J1 o4 V- x9 G" H# s* B
; ?, {7 K5 g$ X' {6 r Connection Failed. Could not connect to VeSys Manager
6 m* O" d9 N3 @3 dSymptoms# [# H5 h0 u, n( o2 c9 t; s6 R
In new install of 2010.1, getting error when launching client.# F* x( y! P1 D& H
6 e7 E' A0 U/ V! y
0 H y* L7 u* w, y( M/ SConnection Failed. Could not connect to VeSys Manager.
0 H* m. K1 b6 R$ v+ E$ [- W9 w0 K! a* b' }
Causes
% u# F/ W6 y* M" \/ y6 pInstalled as local.
0 Z# ]7 P4 @& K9 y# S$ K+ dTechNote ID4 r1 y/ H) d1 v1 O" E
MG527386! F% G4 X: M9 e, M3 [+ P
TechNote Type5 q+ p2 y: V* S: O# Z3 R7 m
Solution
( ~. u% J: p' ~, k/ W: _Updated$ I3 G! e$ p+ ~# D. f/ y* G
8/25/103 O2 u3 U* r L d+ E* v
Products
X( z0 p4 n$ @* e( UVeSys Design
, O4 L5 [) f' K8 {9 B( n# B2 t# H3 I" ^6 M; W8 B
VeSys Harness4 f. _) [% |5 |2 \2 \9 z) ?
+ B8 T. a" U C! q7 F4 _( ^
VeSys Components
" T. `+ F7 m% M8 j6 y
( R9 B3 D; T- f5 p# oVeSys Engineer
* h q. N- ^3 X. ?' u0 H6 G+ E( ~5 W, K% D/ k7 V* x" E7 Y
VeSys Integration& r; |) i3 M6 X* H- [$ E" J j% n
8 S6 y h+ r" V$ d/ s% U4 O
VeSys Service' g$ c6 _& a. D- n% [6 b2 V- l2 S
$ D6 \# h# F/ m5 [6 X9 w' LEnvironment. s- t9 l$ z H0 Z) ?: P. o
Solution; A' e0 g. e8 {2 n8 P6 F7 Y
In vesysmanagerprops.xml change the connection from "local" to "remote".
o0 S* X; x6 v7 M
6 {* b0 d2 E1 Jthe file is located in the config folder where VeSys Manager is installed. |
|