Member Login
Search
Jump to a Date
Sponsored Communities
Cool stuff
Neat Stuff

Visit our shop for nerds in control lifestyle products.
Thermal Overload
The threads that wouldn't die...
- PC reliability?
- Windows, real time
- PID loops
- PCs vs. PLCs
- Replacing people
- MS 'monopoly'?
- Software quality
- Where do we go from here?
- Why pay?
- PC reliability?
- Windows, real time
- PID loops
- PCs vs. PLCs
- Replacing people
- MS 'monopoly'?
- Software quality
- Where do we go from here?
- Why pay?
Fortune
BOO! We changed Coke again! BLEAH! BLEAH!
RSS Feed
www.control.com/rss/
To get a personalized feed, become a member at no cost.
Hi.
We moved(converted) FactoryLink 6.6 (WinNT) application to FactoryLink 7.5 (WinXp).
We can't run syb_hist.exe (no errors, no messages).Sybase client ASE 12.5 installed on PC.
All tables in FLCM is reading well.
Help, pls.
Anybody use FactoryLink 7.5 (WinXP+SP2) and Sybase DB(ASE 12.5)?
Alexander
We moved(converted) FactoryLink 6.6 (WinNT) application to FactoryLink 7.5 (WinXp).
We can't run syb_hist.exe (no errors, no messages).Sybase client ASE 12.5 installed on PC.
All tables in FLCM is reading well.
Help, pls.
Anybody use FactoryLink 7.5 (WinXP+SP2) and Sybase DB(ASE 12.5)?
Alexander
Hi Alexander,
The source of your problem can be several so, I'd do the following to isolate the problem:
1) Put the '-L' argument to Database Logger and Sybase Historian tasks (in System Configuration Information panel) to generate a LOG file from those tasks and have better and more info about the problem.
2) Use the ODBC historian task instead of Sybase historian to test or discard a problem from FactoryLink side (if both historians tasks have problem, the problem could be an incorrect setting to connect to your Sybase DB).
3) Create and use an ODBC connection from your WXP and test it in Excel (via Data/Import External Data/New Database Query) to retrieve data from your Sybase DB to your worksheet. With it, you'll have a secondary tool to verify if everything from Sybase side is right (user permissions, network connections, etc).
Let me know what you get to keep on helping you.
Best regards.
Saludos.
Gustavo A. Valero P.
BIConsulting C.A.
Valencia - Venezuela
gustavo.valero @ biconsulting. com
The source of your problem can be several so, I'd do the following to isolate the problem:
1) Put the '-L' argument to Database Logger and Sybase Historian tasks (in System Configuration Information panel) to generate a LOG file from those tasks and have better and more info about the problem.
2) Use the ODBC historian task instead of Sybase historian to test or discard a problem from FactoryLink side (if both historians tasks have problem, the problem could be an incorrect setting to connect to your Sybase DB).
3) Create and use an ODBC connection from your WXP and test it in Excel (via Data/Import External Data/New Database Query) to retrieve data from your Sybase DB to your worksheet. With it, you'll have a secondary tool to verify if everything from Sybase side is right (user permissions, network connections, etc).
Let me know what you get to keep on helping you.
Best regards.
Saludos.
Gustavo A. Valero P.
BIConsulting C.A.
Valencia - Venezuela
gustavo.valero @ biconsulting. com
From Control Engineering magazine...
Related articles from Control
Engineering magazine- Rockwell Automation introduces virtual design and production software utility
- FactoryTalk industry-specific applications launched
- Rockwell Automation releases VantagePoint for plant data visualization
- 14 new high-performance USB data acquisition devices
- New cyber security blog tackles DCS, SCADA vulnerabilities
- Analyzing Critical Flow Measurements
- Get the Most HMI for the Dollar
- Panel meter applications: 3-in. 2U three color touch modules
Above articles copyright 2008 Reed Business Information.
Subject to its Terms of Use.
Your use of this site is subject to the terms and conditions set forth under Legal Notices and the Privacy Policy. Please read those terms and conditions carefully. Subject to the rights expressly reserved to others under Legal Notices, the content of this site and the compilation thereof is © 1999-2008 Control Technology Corporation. All rights reserved.
Our Advertisers
Help keep our servers running...
Patronize our advertisers!
Patronize our advertisers!




