Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Weird script happenings

Status
Not open for further replies.

Nostferatu

IS-IT--Management
Feb 16, 2001
63
GB
OK, so this is a login script issue...

We have a metframe farm, and as we are using a 16 bit version of oracle require that certain .ini files in set-up for each user so as to enable the nescessary pathing for various resources.

In this example we have a Perth (Aus) Office, and the Head office in Reading (UK).
Location has its own login script that processes certain drive mappings and some of the security features, it also checks the computer name as the script initialises, and if it is one of the metaframe farm servers it is sent to run the metaframe.cmd command copying across the required files.

This script has run well for a long time, however... One particular user in Perth had a problem, and looking into it I discovered the files were not being pulled over thru the script.
Changing the script to the Reading script however recified this problem, then changing his script back to Perth.bat (windows 95 systems on site, his however is NT WK but hence the .bat not cmd) enabled hom to proceed normally... I can go into more detail if nescessary, just dont want to write an essay...
Steve Marshall
Group IT
Technical Support Supervisor
(aka General Meddler)
The Expro Group
Reading
UK
 
Are you saying that this is only a problem for one user in Perth, and that other users at that location are OK?

Login scripts usually call *.cmd files rather than *.bat files, but either should work.

Did the user in question originate from Reading?

Have you tried running Filemon to see where the script is falling over?

I hope this helps.
 
Hiya Engineer...

Yes the user is in Perth, the scripts are identicle except for the .bat and .cmd naming. and the script appears to be falling over when calling the metframe.cmd script that copies the required files into the users profile path, saying that access has been denied to the relevant folder.

As I stated earlier though, if I change the login script to the reading version reading.cmd it works fine and subsequent logins using the perth.bat file work ok.

I believe this may have something to do with username length (its 10 chars) but dont really see how... however upon trying to replicate the problem, it failed when creating a user name call test123456 but worked with test12 but that still does not explain the fact that after running the Reading script once, the Perth script will subsequently work ok.

Thanks in advance for any help Steve Marshall
Group IT
Technical Support Supervisor
(aka General Meddler)
The Expro Group
Reading
UK
 
OK, try running filemon - if you're getting access denied messages, then you may need to adjust the permissions on shares, folders or files.

You can get Filemon from - and it's free!

The questions I would be asking myself at this point are:

What are the differences between the Reading and the Perth login scripts - what do they individually accomplish?

If you put pauses in the Perth script the first time it is run, can you locate the error by comparing it with the Reading script?

My hunch is that the Reading script maps a network drive to a share, and the Perth one does not. Hence your access denied messages, as the system attempts to access something that, to all intents and purposes, is not there.

The length of the username would only come into play if the system administrator (presumably you) had set a maximum length (I believe the default is 13 characters for NT).

I hope this helps
 
Hence the confusion I have engineer... the two scirpts begin by identifying the computer name of the current users system, and the script is identicle in both, if the system is any one of 6 server names (IE they have launched a published app, or desktop session) then the script sends them stright to the metaframe.cmd script which runs the file copying and directory creation process.

As I mentioned before the Perth script will work after the Reading script has run...

I am off to download filemon now though, and see what happens, thanks for the URL Steve Marshall
Group IT
Technical Support Supervisor
(aka General Meddler)
The Expro Group
Reading
UK
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top