Problem trying to view data and running a job

anilkona · Post by **anilkona** » Mon Jun 27, 2005 6:53 pm

We are encountering a strange problem with Ascential 7.5.

we are ONLY able to view data or run a server job with one particular user id. When we login as other users (even administrator) we are not able to view the data. It just hangs on the screen where we try to view the data.

Anyone had this problem? The permissions on the project are set as 'Everyone' -> DataStage Developer.

The server is sitting on Windows 2000 box. Clients are on XP.

Thanks,
-Anil

chulett · Post by **chulett** » Mon Jun 27, 2005 6:57 pm

View what kind of data? From where? Is this one user the same user that created the jobs?

ps. Don't mark the post as a UNIX OS post if your server runs on Windows. It confuses things.

anilkona · Post by **anilkona** » Mon Jun 27, 2005 6:59 pm

View Data from the stage definition. The stage definition is of type ODBC. There is a button on the stage which says 'View Data'.

The user that is trying to view the data is different from the user that created the job. Does this matter?

FYI, The project is NOT a protected project

Sorry for the confusion on the server. I corrected the post.

chulett · Post by **chulett** » Mon Jun 27, 2005 7:14 pm

It's not suppose to matter... just trying to get as much information as possible about the problem.

Ok, so just a problem viewing ODBC data. Do both people (the 'working' one and the 'non-working' ones) use the same logon information to your ODBC database or do they each have their own?

It would probably be good to know what database you are connecting to via ODBC - SQL Server? Too much information is better than not enough information.

anilkona · Post by **anilkona** » Mon Jun 27, 2005 7:17 pm

Both users connect to the data source with the same user name and password. The strange thing about this is the user that is not able to access is the admin and the user that created the job and is able to view data is ordinary user.

We are connecting to a Db2 database sitting on AS400. We are using IBM's client access express ODBC drivers .

anilkona · Post by **anilkona** » Fri Jul 01, 2005 4:05 pm

This problem is solved after changing the timeout on the administrator page and reboot of the server.