Starting Director raises 'Run-time error 13' exception

coface · Post by **coface** » Wed Jun 11, 2008 5:18 am

Hello,
On a windows (Windows 2000) client I have installed Microsoft's DOT NET (release 1.1) and the DataStage client (release 7.5.2). Afterwards I performed a reboot. After the logon several messageboxes - because of missing DLL's - are popping up. All of them are related to DataStage. The Designer, Manager and Adminstrator are working without any problems at all. But when I try to start the director the exception 'Run-time error 13 type mismatch' gets raised.
Any help will be appreciated...

Rgds
Jan H.

ArndW · Post by **ArndW** » Wed Jun 11, 2008 5:49 am

Which did you install first, DS or the dot.net update? Have you tried re-installing DS?

chulett · Post by **chulett** » Wed Jun 11, 2008 6:43 am

That would be the first thing I'd try - a reinstallation of the client.

coface · Post by **coface** » Wed Jun 11, 2008 7:30 am

chulett wrote:That would be the first thing I'd try - a reinstallation of the client.

The first install of the DataStage client raised the described exception. Afterwards I deinstalled DataStage and bounced the windows pc. Then I installed DOT NET first and as as next step the client once again.
That didn't change anything at all...

Rgds
Jan H.

chulett · Post by **chulett** » Wed Jun 11, 2008 7:47 am

Sometimes the 'reinstall' need to be complete. As in the old installation needs to be nuked. If you want to try that, it woudl involve these steps:

1) Uninstall the client.
2) Delete any leftover 'Ascential' directories.
3) Use regedit to remove any leftover 'Ascential' keywords.
4) Reboot.
5) Reinstall.

If you are uncomfortable with #3 then I wouldn't suggest taking this route, however, I've seen that can be a critical step in the process.

coface · Post by **coface** » Mon Dec 29, 2008 8:12 am

Already resolved a while ago...
Error was due to a wrong version of a windows library (dll)

Marc.Gendreau@Lafarge-na. · Fri Apr 17, 2009 6:28 am

I have the same issue. Can you provide me with more details on which windows library (dll) was causing the issue ?
Thank you.

Marc.Gendreau@Lafarge-na. · Fri Apr 17, 2009 6:30 am

Found the issue. The language standard format was set to 'English (United States)' instead of 'French Canadian' on a windows french pc version.
In summary: Be carefull with language setting and windows version.