July 23, 2008 11:58pm pdt

1. kmartin7 2,000
1. areevesh... 2,000
1. mlmcc 2,000
1. geneus 2,000
1. PaulsonG... 2,000
1. lwolfens... 2,000
1. OutlawSy... 2,000
1. natoka 2,000
1. ericpete 2,000
10. mass2612 1,500
10. BillBach 1,500
10. MOA81 1,500
10. KCTS 1,500
10. jd_wight 1,500
10. lesouef 1,500
10. sysreq2000 1,500
10. vincem1099 1,500
10. dpetr000 1,500

1. rama_kri... 19,930
2. DennisL 10,478
3. minichicken 8,500
4. nav_kum_v 5,575
5. MOA81 5,500
5. jonvaughan 5,500
7. Ritesh_Garg 5,000
8. mlmcc 4,000
9. stephenmraj 3,000
9. mhci 3,000
9. hilay 3,000
12. cvvood 2,814
13. turn123 2,500
14. kmartin7 2,000
14. jgilligan1 2,000
14. ajay_erdci 2,000
14. SysExpert 2,000
14. meluhk 2,000
14. natoka 2,000
14. lwolfens... 2,000
14. OutlawSy... 2,000
14. tbarbe01 2,000
14. arrkerr1024 2,000
14. RobSampson 2,000
14. ericpete 2,000
14. dovidmichel 2,000
14. amit_g 2,000
14. geneus 2,000
14. PaulsonG... 2,000
14. areevesh... 2,000

03.29.2004 at 12:45PM PST, ID: 20936406

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

7.2

ODBC Connection to Progress fails to open PROMSGS

Zone: ERP Software

Tags: progress, odbc, open, promsgs

using a Merant 3.70 32-bit Progress ODBC driver, i can append data to an existing table structure manually through a SQL Server DTS package. if i try to schedule it as a job within the SQL Server Agent, it fails. Does anyone know how the ODBC is trying to open PROMSGS and what permissions it needs to have? Suggestions? ---ssam

following is the actual error message:

DTSRun: Loading... DTSRun: Executing... DTSRun OnStart: Copy Data from Results to [SytelineImport].[dbo].[custaddr] Step DTSRun OnError: Copy Data from Results to [SytelineImport].[dbo].[custaddr] Step, Error = -2147467259 (80004005) Error string: [MERANT][ODBC PROGRESS driver]msgOpen: unable to open message file: PROMSGS Error source: Microsoft OLE DB Provider for ODBC Drivers Help file: Help context: 0 Error Detail Records: Error: -2147467259 (80004005); Provider Error: 0 (0) Error string: [MERANT][ODBC PROGRESS driver]msgOpen: unable to open message file: PROMSGS Error source: Microsoft OLE DB Provider for ODBC Drivers Help file: Help context: 0 DTSRun OnFinish: Copy Data from Results to [SytelineImport].[dbo].[custaddr] Step DTSRun: Package execution complete. Process Exit Code 1. The step failed.

Start your free trial to view this solution

Question Stats

Zone: Database

Question Asked By: ssam

Solution Provided By: jgilligan1

Participating Experts: 4

Solution Grade: A

Translate:

Loading Advertisement...

Microsoft

Internet Protocols
Applications

Development
OS

Hardware
Windows Security

Apple

Operating Systems
Hardware

Programming
Networking

Software

Internet

Search Engines
File Sharing
WebTrends / Stats
Spy / Ad Blockers

Web Browsers
New Net Users
Web Development
Chat / IM

Anti Spam
Web Servers
Anti-Virus
Email Clients

Gamers

Tips
Online / MMORPG
Puzzle
Emulators

Action / Adventure
Role Playing
Consoles
Game Programming

Strategy
Sports
Misc
Computer Games

Digital Living

Hardware
Automotive
New Net Users
New Users

Software
Digital Music
Gaming World
Home Security

Apple
Networking Hardware

Virus & Spyware

Vulnerabilities
IDS
Encryption
Anti-Virus

Operating Systems Security
Software Firewalls
WebApplications
Cell Phones

Operating Systems
Internet
Hardware Firewalls

Hardware

Displays / Monitors
Handhelds / PDAs
Components
Peripherals
Laptops/Notebooks

Servers
Misc
Apple
Embedded Hardware
Networking Hardware

Storage
Desktops
New Users

Software

System Utilities
Industry Specific
Network Management
Photos / Graphics
Page Layout
VMware
Misc
Web Development

OS
CYGWIN
Voice Recognition
Virtualization
Message Queue
Quality Assurance
Security
Firewalls

MultiMedia Applications
Development
Database
Office / Productivity
Business Management
OS/2 Apps
Server Software
Internet / Email

ITPro

OS
Storage
Encryption
Operating Systems Security
Apple Hardware
Laptops & Notebooks
Servers
Networking Hardware
Peripherals
Devices

Displays / Monitors
WebTrends / Stats
Search Engines
Firewalls
Web Computing
WebApplications
IDS
Vulnerabilities
Email Clients
File Sharing

Spy / Ad Blockers
Web Browsers
Web Servers
Networking
Anti-Virus
Consulting
Chat / IM
Anti Spam

Developer

Web Servers
Web Browsers
Game Programming
Dev Tools
Industry Specific
Office / Productivity

Database
CYGWIN
Web Development
Search Engines
File Sharing
WebTrends / Stats

Programming
Content Management
Application Servers
Protocols

Storage

Removable Backup Media
Storage Technology
Servers

Grid
Remote Access
Backup / Restore

Misc
Hard Drives

Miscellaneous
Security
Development
Linux
VMware

MainFrame OS
Unix
Apple
OS / 2
AS / 400

BeOS
Microsoft
VMS / OpenVMS

Database

Oracle
Miscellaneous
MySQL
Software
Sybase
Contact Management
PostgreSQL
Data Manipulation
Clarion
InterSystems Cache

Siebel
MUMPS
OLAP
SQLBase
SAS
GIS & GPS
4GL
Berkeley DB
DB2
Informix

Interbase / Firebird
FoxPro
Reporting
LDAP
Filemaker Pro
MS SQL Server
dBase
MS Access

Security

Misc
Web Browsers
Software Firewalls
Operating Systems Security
File Sharing

Spy / Ad Blockers
Vulnerabilities
WebApplications
IDS
Anti-Virus

Encryption
Anti Spam
Email Clients
VPN
Chat / IM

Programming

Editors IDEs
Installation
Handhelds / PDAs
Multimedia Programming
System / Kernel
Automation

Algorithms
Game
Signal Processing
Project Management
Open Source
Database

Misc
Languages
Processor Platforms
Theory

Web Development

Scripting
Blogs
Web Servers
Software
Search Engines
Web Graphics
Web Services

Images
Internet Marketing
Images and Photos
Components
Document Imaging
Web Languages/Standards
Illustration

WebApplications
Fonts
WebTrends / Stats
Authoring
Digital Camera Software
Miscellaneous

Networking

Protocols
Apple Networking
Network Management
Message Queue
Application Servers
Content Management
File Servers
Email Servers
Misc
Java Editors & IDEs

Wireless
Networking Hardware
Backup / Restore
System Utilities
ISPs & Hosting
Web Servers
Storage Technology
Removable Backup Media
Servers
Web Computing

Broadband
Grid
OS / 2
Novell Netware
Unix Networking
Windows Networking
Security
Telecommunications
Operating Systems
Linux Networking

Other

Lounge
Business Travel
Community Support
New Net Users

Philosophy / Religion
Math / Science
Miscellaneous
URLs

Expert Lounge
Politics
Puzzles / Riddles
Automotive

Community Support

Suggestions
New to EE
New Topics
CleanUp

Announcements
General
Feedback

Input
EE Bugs

04.09.2004 at 06:23AM PDT, ID: 10790997

jgilligan1:

Well, there are at least a couple of problems.

1. You do not have your environment variables set, depending on how your doing your ODBC connect, you need to specifify at least a couple of variables ahead of your active DB session.

1. DLC=/usr/dlc91x/ (wherever you have progress installed)
2. PROMSG=$DLC/promsgs - this typically is under your DLC directory and points to a storage file which controlls the error messages that progress reports on.

Other than that, as far as permissions are concerned, you don't need to have anything other that read only. But as far as access to the database you may also wish to set that to read only as well.

If that doesn't show you any love, you may consider the PEG (http://www.peg.com) , it may be a faux pas to mention it here but this is a usergroup which is very small but has some excellent progress experts (many of whom work for Progress itself) , You'd be hard pressed to find a more competent group than those guys when it comes to Progress.

Hope that helps,

Joe Gilligan
Perpetual student.

Accepted Solution

04.09.2004 at 06:47AM PDT, ID: 10791146

prairieits:

I can tell you with 100 percent certainty that jgilligan1's answer is correct, except that you are using a Windows OS, so rather than the /usr reference, your path is going to be c:\progress\something... Same will hold true for the PROMSGS path.

Good luck,
Jerod

04.11.2004 at 12:37AM PDT, ID: 10800142

Varrus:

Hello:

The only other thing I might add is two more environment variables:

IDLC=c:/dlcxxx
IPROMSGS=$DLC/promsgs

These will be the same values as the DLC and PROMSGS variables.

I have found this has solved my previous Merant 3.7 ODBC connection funnies!

Cheers!

Peter

04.12.2004 at 10:44AM PDT, ID: 10807052

jgilligan1:

Geepers, Sorry about the Unix/Dos issue. I work in a bunch of different OS's and forget myself alot.

Hopefully, the environment issues will resolve the problem but it may not completely do so if there are some other issues.

Regards,

Joe G.

04.12.2004 at 12:42PM PDT, ID: 10807911

ssam:

jgilligan1 was essentially correct; the solution was actually, though, an update/upgrade to the client installed on the box where the SQL server resided.

07.26.2005 at 06:22AM PDT, ID: 14526647

YelenaC1:

I have exactly the same problem and all my environment variables are set up correctly. (DLC, IDLC, PROMSGS, IPROMSGS).

What do you mean by "client update/upgrade"?

07.26.2005 at 06:30AM PDT, ID: 14526741

jgilligan1:

It's possible that there is a problem with the ODBC not being completely compatible with the specific version of Progress. What versions/platform of each are you using?

Regards,

Joe G.

07.26.2005 at 06:39AM PDT, ID: 14526872

YelenaC1:

Progress version is 9.1C on unix.
SQL Server instance is installed on Windows Server 2003.
Merant 3.7 is also installed on Windows Server 2003 ( the same server).

If I test the connection manually from ODBC utility, it connects correctly.

If I run DTS package manually, it runs fine. The only time I have a problem if it is run as a job. That's when I get the PROMSGS error.

07.26.2005 at 06:46AM PDT, ID: 14526938

jgilligan1:

When you say a job, do you mean a cron/batch job from Unix?

07.26.2005 at 06:58AM PDT, ID: 14527074

YelenaC1:

No, I mean a Job within SQL Server Agent. If you look at the very first original question on this thread, it explains my problem exactly. I am running a DTS package in SQL Server, moving data from Progress to SQL, using DSN with Merant 3.70 driver.

When I schedule a DTS package to run in SQL Server Agent, it makes it a job. That job fails with the error described above.

07.26.2005 at 07:47AM PDT, ID: 14527649

jgilligan1:

Ok. So does the promsgs file exist in the proper spot? I have also seen instances where this kind of message crops of when the Progress running on the workstation is not installed properly or rather it is copied rather than installed.

Joe G.

20080236-EE-VQP-29