|
没发现什么好东西
6 @2 w2 j( r% Y, [6 S- @) w1 L& H( e2 {
8 x6 s# q! U8 {1 R: \, @$ ATechNote MG527386, 8/25/10 (0 votes)
$ @4 R1 A7 |2 H1 i1 B8 L5 i2 l" z# Z b7 @
Rate This TechNote
7 b/ o ?/ C6 g1 |: q2 @How can we improve this?6 O" f u. y/ O+ w' w- q. J
Low High ; D& ^& t7 G* l0 W
On a scale of 1 to 5:
6 L* n6 B+ I. B# a7 v! b9 I! t2 | 1 2 3 4 5
' j1 }; O0 Y2 w# |$ H, L2 ]' n& ?4 _- k
; l" { a1 i; g2 h7 @& {2 l: i, qWas this content helpful No Yes
8 S: w* S0 {' A* H0 ^% ?/ _8 o; O' K# _, T! b% T; K
9 i$ z3 I6 E; ^
$ G& A* [. O( Z) e
+ t, A& u8 t! S; ] _& V Connection Failed. Could not connect to VeSys Manager
2 J9 T; ], Z+ `' O3 _' |Symptoms
7 @5 ~3 V8 e" x/ k* T9 pIn new install of 2010.1, getting error when launching client.) ? p/ [+ k& c& o# G- t6 i
. ^8 p- B4 Y6 e. s$ B
& x) t( w5 F; n6 i/ ]$ u( nConnection Failed. Could not connect to VeSys Manager.% y# x7 ^) T" d: U" f. d
9 I- T- K: j W1 F3 I; [
Causes1 V# y2 }) v( M( i' i# P3 I6 b
Installed as local.3 f4 E- [& T% J, k
TechNote ID
: L% _7 g& Z1 FMG527386
1 m3 d2 D" f$ Z) s+ _3 n. bTechNote Type. z! R$ Z# t% |
Solution% I; S8 U* N- B& |6 K
Updated; z" g. n5 K4 ?2 a# j: R
8/25/10, l- a% V7 r: m* d3 X0 o& i" \
Products
, _0 L6 D5 @6 \; ]) qVeSys Design! U" n, H8 W0 z+ l% @, U; S
; q2 p f3 p0 e; h# @) @$ ^' kVeSys Harness! I, L3 }* M, g" X* W: @" n
$ y; \: o1 J; U \9 t4 I3 \1 RVeSys Components
. Y0 [: c8 i( t9 S" j# m7 v% C
& g& E% a! ^6 a" FVeSys Engineer4 b+ `4 q& e, @( r: M2 N/ A
7 i: l }( y( n c2 ^! i
VeSys Integration% I2 u, R( T1 d2 \5 r& u
; X6 R- w" ? L$ R2 U
VeSys Service
! G5 y" S0 h( ?8 R
' t0 A$ w# l f& ]Environment+ _% J4 Y1 _% E y. i
Solution
# }$ b: K2 Q+ }7 ^2 S, U& ?2 RIn vesysmanagerprops.xml change the connection from "local" to "remote".5 ~- ^! P# F, _( }: H3 M3 U
& e9 J7 ]6 W6 l, E+ s$ B/ s5 C
the file is located in the config folder where VeSys Manager is installed. |
|