|
没发现什么好东西
% u/ A; e9 Z0 {+ u/ Q$ S6 }
5 ~, L1 x$ j6 h& J
% o8 \6 ~0 m0 `+ B( {TechNote MG527386, 8/25/10 (0 votes)
8 c2 E S7 M( Q' z; S+ j& } N# L. J" E9 K
Rate This TechNote3 n% a4 r0 P5 [- Y) n$ k
How can we improve this?: S4 L. U5 c2 j
Low High ; j5 [/ h6 G! B, `
On a scale of 1 to 5:
* t d" ^) ]/ F# }1 {0 U) W, ~ 1 2 3 4 5
: k8 R: x5 f. b! R2 _
0 f( ]$ W- E- z9 W! E9 g) SWas this content helpful No Yes ( r' g. Y9 o5 i* |
$ e2 q/ e$ l H7 S) P6 a, P
. K. f0 s* z' z" ?! |* I. H' M
0 O- S: k& {9 @" @
9 J2 K2 ?' M, L1 i9 m V Connection Failed. Could not connect to VeSys Manager; T- U% M; ^% ^* C, j h t1 @
Symptoms0 e$ ?& h4 l" V
In new install of 2010.1, getting error when launching client.
& B0 I+ |) @# G$ S' T; F- f- J1 H
" b7 X# z1 g* x! U+ p$ {7 E5 W# q
Connection Failed. Could not connect to VeSys Manager.+ @4 U2 v+ l- t# }3 g2 Z; x
! I- x* k; R, Z% D
Causes6 z2 {- t5 x1 |, w& H1 N) q
Installed as local. j' Q$ @& \* s5 Z
TechNote ID$ `/ D( N4 l% m! f% @
MG527386
6 ] H D. E" P# P' m, uTechNote Type
, A; v& {7 C2 v# U0 |Solution
/ t: m1 X0 `6 X% ^$ ^+ ]Updated4 H9 N' c0 V& g% A% h) q
8/25/104 M! h; ~* V( ?! R% m
Products8 ^0 ~: ^; }) C1 u
VeSys Design& w8 P# S* {5 _1 O; ?% @& U# Z
2 ^# K; c/ T; ^! @6 p+ r% i
VeSys Harness
" E' z9 l4 D+ b. m. G3 _
+ j* o4 M# R Z% l* @5 d# oVeSys Components
- i8 m( e0 O& Y- P7 G, i9 X" [7 c6 W4 a$ z! c* N: X6 f& M
VeSys Engineer
S7 T# r2 j* r" e8 T3 f# \4 L4 F, n8 V* w, p7 G4 Y
VeSys Integration/ b& B) Z) E& m# h6 H- o
. E! L0 O* {. S/ W# vVeSys Service
! |7 _) E4 n, V! r3 i y7 n1 n$ \7 W1 _% g' j! ?$ p5 U* [
Environment
# K9 |; @; D Q& x9 ~- @! }# |Solution
# K F+ g- S$ r: X9 y7 W8 g4 oIn vesysmanagerprops.xml change the connection from "local" to "remote". g; d6 y z& y) x9 j6 y
2 R0 C9 b; N" T G
the file is located in the config folder where VeSys Manager is installed. |
|