|
没发现什么好东西1 X# D9 V- x2 c% U- o, ^' t
5 x% @ T1 M' n7 a: _! e' y4 L
" G7 h5 u8 _3 w9 K9 Z! |: p
TechNote MG527386, 8/25/10 (0 votes) : O, J! I$ V# B: R( _$ z( z( x% N! T
0 ~. v6 \# l9 b/ ~3 U1 hRate This TechNote
/ G$ I. D+ k4 Z9 s, yHow can we improve this?9 l4 M0 n+ o. w# h
Low High
' z* ~; W: `' ^ `" k1 GOn a scale of 1 to 5:
6 l8 ~# y: @; O# } 1 2 3 4 5
: w8 q4 R6 O" P % E, b( k7 s) ], \) f3 O
Was this content helpful No Yes
" r5 ^( b& U3 F5 _4 [+ f
' l7 g9 F& r1 U. L 3 @# c7 i3 ~7 [6 }6 J, ]
- \2 h. r$ C- A1 i% c0 p
3 V9 L- X, u/ z- r! v% A" ] Connection Failed. Could not connect to VeSys Manager# l8 @6 m- j* i4 k6 M x) b
Symptoms2 n; t* _. W: R
In new install of 2010.1, getting error when launching client.
+ R* d% t6 g$ w+ a4 D
/ d! X. m6 t& i" m8 R' f7 `9 v7 H" K" T
Connection Failed. Could not connect to VeSys Manager.
m. A8 Q# u; A3 w& f6 ?
/ l; G( H2 [6 i- i/ pCauses
% h/ X$ E+ ~3 M. S3 q. z5 Q' cInstalled as local.( l1 ~9 _0 g( w0 q4 _( M
TechNote ID
& K* V/ L) |, e) B3 ^: [- yMG5273868 e" _6 B* O# n1 m' j; [
TechNote Type
/ v( e7 l% d7 Q' ]Solution
1 e4 K, N* V# XUpdated
7 ` w9 X8 ]9 n4 \" e) v: C8/25/10- A+ _' q$ I9 I* u
Products
& U' f3 C. f5 f8 S) k6 N9 q, iVeSys Design
0 H! h" }; f$ B' m5 {# A% v$ l3 R) C% j
VeSys Harness
2 @6 P) @) ] f# W9 r
+ f" Z# o) P0 K8 u3 U0 OVeSys Components9 Y# l0 h+ x8 U
9 y$ W+ g6 E4 n: J6 i
VeSys Engineer# M' \0 f g: |: U. g1 \+ v
# w1 X( A4 I* H% m" V0 _& TVeSys Integration7 T4 W n" T5 \ Q% k5 B
" |& [, R& ^( O Z* g1 S
VeSys Service; K3 l0 q! Y( x- [- Z% T
5 g& e, V% j0 {: |# o1 jEnvironment
1 k/ w, h; W. B7 B. NSolution
+ W7 L x/ m! ]- R% hIn vesysmanagerprops.xml change the connection from "local" to "remote".3 `$ f4 e$ i( t1 E
6 U! H7 b6 z' Y8 u+ _the file is located in the config folder where VeSys Manager is installed. |
|