|
没发现什么好东西1 y# T- }7 ]$ @; h+ k
( M2 }, g. K4 ~* j+ t' L( A
+ ^. ^: Y! [. p0 [5 m6 `TechNote MG527386, 8/25/10 (0 votes)
9 a+ l' `0 V( q2 o# Y9 _5 E$ e0 b! H9 U
Rate This TechNote: W8 h) ]( H5 b4 A) R# x
How can we improve this?
# O; q" b# ~: E Low High
' N. N- Y) B% j l0 V M) k2 ZOn a scale of 1 to 5: 0 H* W& v/ m. w5 Q0 L3 Y
1 2 3 4 5
& m8 u: y" C' q2 U; i
% m2 u% s8 L" m S' O7 Y5 `* Y7 zWas this content helpful No Yes # X& v" w+ R# ^' I- ^: X9 `* E
3 ~ N: h# H& k7 S7 }" W$ c' S
. N0 ^ {. X/ f/ |! [5 [ _; S7 d
2 ?& n1 a% [, M( D% w Connection Failed. Could not connect to VeSys Manager
- }4 z: B- F6 K! ~7 L9 ^0 FSymptoms
- [0 m/ U4 v4 [& O; F& ]5 IIn new install of 2010.1, getting error when launching client.
+ b2 i9 P& q. b0 ~3 {! ^: [: \6 p6 J
$ l9 R. ]) l0 V, e) P# h* R+ O3 |; {6 [% k O
Connection Failed. Could not connect to VeSys Manager.$ H1 g' }* [5 r6 H
2 D0 J# Y x/ pCauses
# [3 `( t* {% q& F/ o: IInstalled as local.6 G9 ]/ R. l$ A! F- ^
TechNote ID
0 G1 c, e. @: Q7 C0 \ j4 X. ]MG527386# L S) j- h [! G, w1 N3 `0 P
TechNote Type
$ X% b( d, {3 |7 ~9 ]5 hSolution
) D5 S2 I( G9 E* v G+ fUpdated
( t4 o: ^) I x: \. n8/25/10
* A W5 d" U! a5 V/ M! i: dProducts
, L9 J5 r" w, {$ FVeSys Design
# g0 ?+ D8 g9 P, [8 l) R5 `
. ^4 T5 k) q/ zVeSys Harness$ j& j- c6 Q" ^3 a- U+ S$ ?
, s* u+ A1 n$ X8 d7 eVeSys Components
1 B- Z/ g- s* U, P* U5 V8 z0 B' v' D, w/ J
VeSys Engineer
/ y: U) A/ F3 j9 M3 m- X! z# L; D" P5 _
VeSys Integration8 }: p8 ^. s$ G" u
0 U9 F$ i; L2 ^VeSys Service# j; E# H2 H% m$ K" X
) l- r, N, g0 K2 W% \ Y6 _5 t6 uEnvironment0 b* M$ R0 H1 |) y
Solution, Z8 D% W3 }1 s
In vesysmanagerprops.xml change the connection from "local" to "remote".
( H8 i4 i* D. c* e) }0 H3 a' w) R# A4 ?, N8 h
the file is located in the config folder where VeSys Manager is installed. |
|