|
没发现什么好东西5 O1 n' Q' ?: h- G2 p- s7 v; x5 b
" {) k! I% x+ `
# O4 }$ s( R$ ITechNote MG527386, 8/25/10 (0 votes) 4 E$ F* ?6 m' E- o8 A. ?
$ j3 |1 t" e% h8 ^Rate This TechNote1 E# j8 G1 q. a) Q s' Z. a
How can we improve this?' g, B1 x4 |; V6 [5 D
Low High
/ [, x4 Z$ |7 L2 cOn a scale of 1 to 5:
& X2 i# }) d' c I 1 2 3 4 5
" W" O; | h9 B% R8 C5 ]
( a9 N# x$ X$ |7 ~- m! Y* {8 Y4 rWas this content helpful No Yes ( T1 x0 W' z9 D' a F
- ~# O- m$ r& D8 z! M: w ) p M6 k$ s! a6 g* F
) G. w1 s/ \# ]- i6 ^( {
( `! w9 X3 k7 C7 v5 W& P Connection Failed. Could not connect to VeSys Manager3 Q: B# e+ t$ I, j, P: A$ H: O
Symptoms, u9 W+ T0 `" n6 [
In new install of 2010.1, getting error when launching client.
& P4 F/ Y: o$ J( Y- T J6 U, X; {
7 h" L6 }, R. [) ]& u7 p1 O' d& B& I6 O3 g% B- v
Connection Failed. Could not connect to VeSys Manager. U( m! {: ] U2 c0 _9 G, G
/ }/ A* K) Y3 u L* wCauses. Z5 v2 o3 V) J
Installed as local.
: k% t- N- v o! |+ l4 ]) vTechNote ID- V- r' t2 q4 [4 M k8 }
MG527386
1 p) R1 ^# B. ?" |& u1 Q2 ?; X, VTechNote Type( O2 g2 G6 z8 u* q' S
Solution$ Y( ]8 R+ x8 y O* Z h6 c) M
Updated
% r3 \' B; H% ~) x3 q8/25/10( l3 ^' I3 H8 z/ l* a3 j- \ ]; n
Products2 L% F1 l; s) d1 g/ p
VeSys Design5 |5 Z& z4 j( d0 z
/ j8 s( w2 P" l4 P- r& BVeSys Harness
8 @ k# j# h1 p7 B4 C
5 k. n9 K4 q1 d0 bVeSys Components2 |) d+ N( ^( z" f! f
$ w* Z% ^$ e: `+ V7 BVeSys Engineer& I N% h- Y |* `( w: L4 }
7 h$ I4 k7 Z# x/ \7 C# `! E5 m
VeSys Integration0 J( G/ _4 C# J; m
! C: u' E5 V0 s5 P$ g) [VeSys Service ~ u' l3 _* u4 a( @- g
4 L' Q( b D$ D' ?* q: s9 rEnvironment4 |" G, m* h7 p& g( s- H9 `$ G
Solution- d9 U7 _ T; A$ r
In vesysmanagerprops.xml change the connection from "local" to "remote".' B0 i* _% c8 [1 e N" W
% J1 W% }; \5 V; j; ~
the file is located in the config folder where VeSys Manager is installed. |
|