Hi,
All of a sudden I started getting an unusual sequence of warnings whilst trying to export jobs in DS Manager from both of my development and acceptance environments. It happens only when I try this whilst logged in remotely onto the machine that hosts both the server and the client.
Exporting locally from my machine reports no problems.
The messages coming up are as follows:
- MyCreateObject: Internal error - Could not create object with OLEType=VMDataStage.CDSRProgress
- CDSRepos.Initialize: Internal error - Could not create frmProgress object
After I click on "OK" on these warning windows, my DS Manager just closes.
Has anybody got any ideas as to why this happens.
Regards,
Novak
Problems while exporting from DS Manager
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Have you installed ANY other Windows software that might have overwritten the DataStage DLLs?
The object that can not be created is the export progress reporter.
Re-installing the client is the probable solution.
The object that can not be created is the export progress reporter.
Re-installing the client is the probable solution.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Probably not. For a start you don't know the names of the DLLs. The objects are exposed by the OLE Automation servers represented by the DLLs (sometimes by OCX files). Without a heck of a lot of work you can't know which are in which.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
I know its been a long time since this topic has been opened but I only got around to fix it now, so...
Fortunately Ray, I did not have to go the lengths of re-installing the client, as machine restart fixed it up.
I would've done it long ago, but the remote machine is not under my control.
Thanks a lot,
Novak
Fortunately Ray, I did not have to go the lengths of re-installing the client, as machine restart fixed it up.
I would've done it long ago, but the remote machine is not under my control.
Thanks a lot,
Novak