Page 1 of 1
Datastage Designer problems
Posted: Thu Feb 19, 2004 8:01 am
by raj_cipher
Hi,
My Datastage designer is giving some problems.
1) Its not opening at times.Gives a message Invalid Picture.
2) The job i'm opening shows a msg - DSObjects not found.Unable to retrive the links. The job links are not there.
Anyone could help me in this regards.
Posted: Thu Feb 19, 2004 8:16 am
by chulett
Hmm... your first issue sounds like something I would attempt to solve by re-installing the Client. Perhaps some .dll or other component got stepped on by another application or installation.
Your second problem sounds pretty serious,
perhaps a corrupted Server/DSEngine repository. You are going to need the help of the big Under The Covers Guys like Ray or Ken or Kim (or whomever) that can give you some things to try to rebuild or reindex or whatever is appropriate to recover your projects.
Posted: Thu Feb 19, 2004 2:49 pm
by ray.wurlod
DSObjects is the control that delivers objects to DataStage clients that allow them to open and maintain connections, invoke code on the server and, in general, do all the things they do that require a connection.
Definitely sounds like an incomplete installation.
Try uninstalling. When this is unsuccessful, click on the Details button and record the names of the offending DLLs. Then re-boot before installing the DataStage client software again (so that the DLLs definitely aren't in memory), and re-boot after installing (it's the Microsoft way of doing things!) so that old versions are definitely replaced.
Posted: Sat Feb 21, 2004 7:09 am
by raj_cipher
Hi ,
Atlast solved the Pblm !!!!!!!!!!!!!!!
If v by-pass the user name,Password authentication while logging in to DS we get this error.
If v give those stuffs and proceed v r able to save it.
I don't understand wat diff. it makes. !!!!!!!!!!!!!
Posted: Sat Feb 21, 2004 4:47 pm
by ray.wurlod
Posted: Mon Feb 23, 2004 11:33 am
by wdudek
I had a problem a couple of months ago where after we were hit by a virus, several dll's were corrupted. I believe that after running the fix from microsoft the problem went away. I had to contact Ascential to resolve the issue, but unfortunately I can't remember exactly what they had me do.
Posted: Mon Feb 23, 2004 11:57 am
by chulett
For that kind of thing it's usually simplest to just reinstall the Client.
Posted: Thu Feb 26, 2004 2:15 pm
by wdudek
re-installing the client didn't resolve the problem, it had something to do with a dll that either wasn't removed/over written, or was a windows dll.