DSXchange

Hi DS Gurus,

While running a job, which produced lot of warnings and it issued 'Run-time error '9': Subscript out of range'. Logged into administrator and cleared log using CLEAR RT_LOGxxx.

Encountered the same error 'Run-time error '9': Subscript out of range', while logging into designer but i am able to login to DS administrator.

Could someone throw some light on this?

Note: Able to access other projects in the same server.

Regards
Elavenil

If you get an error like that simply by logging on, I would think you have some kind of corruption in the project / XMETA database and you should be contacting your official support provider for help.

I think this is a Windows (Visual Basic) error. Can you log in with Director client?

Thie is not just an Xmeta error. I get it with datastage 7.5 client also. Its a visual basic error with some sort of repository corruption issue that interferes with the working of datastage clients.

So... would the solution then be a complete reinstall of the client?

I also be curious if this happens to other people or just the OP. The latter would seem to confirm the need to reinstall the client.

Haven't reinstalled the 7.51 A client , Just open director witha different job category showing; as it would require re installing v 8.7 client and a multi client manager - not enough time to go through that pain right now. A search on IBM site (alt+w) may help .
The OP can attempt to open a different job category.

chulett wrote:I also be curious if this happens to other people or just the OP.

It may not have been obvious, but I meant other people in the OP's office.

Thanks everyone for your responses.

Hi Ray,

I am getting the same error when i login to Director client as well.

Hi Ramesh,

Tried enabling the trace by following IBM recommendation in the URL but it did not help. I could not make out anything based on the entries available in the trace files.

Hi Chullet,

Would like to perform reinstallation of client as a last resort.

Appreciate your help.

Regards
Elavenil

Help us out with one thing - does this error happen for other developers in your office or just you?

Might it be possible that you installed some other software (or had software installed/updated automatically) on your client PC? This might have overwritten DLLs and thus caused your problems. A client re-installation would solve your problem if that were the cause.

Hi Chullet,

This issue occurs for everyone who logs into this project.

Hi ArndW,

There is no other SW installation on this server.

Still trying to figure out the cause of this issue. Few developers created jobs on this project but no backup of them so recovery of those jobs are very critical.

Regards
Elavenil

elavenil wrote:This issue occurs for everyone who logs into this project.

That's an important bit of information and rules out the whole client-side possibility. Rather than trying to "figure this out" I'd suggest getting this in front of your official support provider if you haven't already.

Hi Ramesh,

Checked in 'C:\winnt\system32' of the client machines and both files exist in the directory.

I think that this is not related to client as we are able to login to other projects and only this project is the issue.

Checked in the server and do not see any core dumps.

As recommended, ISAlite can be run to identify any symptoms of this issue.

Regards
Elavenil