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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SBT Client Installation Help on XP Pro SP3

Status
Not open for further replies.

techsupporter2010

Technical User
Sep 16, 2010
4
US
I was tasked with setting up a new computer at my company with SBT application residing on a server. NO-one seems to know how it all works, including myself so forgive me for my ignorance.
This was setup for someone on the same machine, different hdd, who was already using SBT correctly from XP but computer had other issues with viruses, etc. that it was faster to just re-install Windows on another partition and make SBT work from the same comp. again.
I was told by someone who's fiddled with SBT in the past that all I'd need to do on a new system is to make a correct shortcut to the application residing on the server.

SBT server application resides on company server eg. \\servername\pro\sbtw.exe thus I mapped the network drive, lets say drive Z: on the comp to \\servername and made the shortcut to Z:\pro\sbtw.exe -t on the new comp. Mind you, this is exactly the same shortcut copied before reinstallation except the old shortcut had drive F: mapped to same location which I assume shouldn't matter.

When I click on the shortcut it brings up the login window into SBT, into which I enter correct username and password and then I get 'error:1002 input/output error.... DO Z:\pro\sbtw.exe'
I can copy the exact error if that would help. Is there anything else I need to install on local comp to access the SBT server ? Are there temp files created that need to be stored in specific directories on local machine and if so where ?

Here's the real kicker, if I just go to several other random Win7 Home machines on the network and just create exactly the same shortcut, with drives mapped exactly the same, then I can get into the SBT under the same password and username without installing any software.

If anyone can give me a hint that would be great as this seems to be the only place online that offers anything that resembles help on SBT.
 
Hi,

Here are some tips you should try:

1. Install the client program in that computer. How?
Try to find the SBT installation CD, put it into the computer CD reader, run the client option, follow the questions you will be asked, done!

But if don't find the SBT installation CD...try this:


2. Install VFP 5.0 or VFP 6.0 in that computer.


Good luck buddy, hope that helps you.

Please feed back!



 
Thanks, I'll try that.
I can't find SBT install CD but found VFP7.0 so I'll try that.

Any idea why it works on Win 7 home client without installing any other software besides making the shortcut ?
 
ok, found the sbt workstation install and its a version 7.2,
ran the installation, pointed to the directory where application resides on server and still the same error.
Found the oldest VFP version we have and installed that as well, same problem.
For my situation I mapped drive Z to point to \\servername\pro

Here is the error I keep getting after inputting correct user and password into sbt:
"error 1002: Input/Output operation failure. Called from m_opentable
Line number: 0
Program code causing error:
DO Z:\pro\sbtw.exe
 
There is a little thing you mentioned at the beginning that I forgot and I think could be the key of the problem:

"SBT server application resides on company server eg. \\servername\pro\sbtw.exe thus I mapped the network drive, lets say drive Z: on the comp to \\servername and made the shortcut to Z:\pro\sbtw.exe -t on the new comp. Mind you, this is exactly the same shortcut copied before reinstallation except the old shortcut had drive F: mapped to same location which I assume shouldn't matter."

Previous version was running on drive F:, now you mapped it to Z: Do not do that!! go back and mapp drive F:

Why?

Because SBT has one .MEM file per installed module (AR, AP, IC..) like ARFDOSnn.MEM,APFDOSnn.MEM where nn is the company number.

Those .MEM files store information about path and datafile names. Paths in .MEM files are still pointing to F:

There are more system datafiles storing paths as well: SYSDATA, SYCPATH, SYCCOMP.

It is easier and faster you mapp drive F: back, otherwise you will have to modify a lot of SBT system datafiles to point to Z:

Keep feeding back!

 
That was going to be my next try and you reaffirmed my suspicion.
I went to other computers which has SBT clients on them and they were all mapped to F: as the network drives. I thought of trying that right away but Windows reconfigured all the drives on the system after install and drive F got taken up by one of the peripherals on comp.

Unplugged the peripherals taking up F drive, remapped to F: drive and voila, that did the trick !!
Thanks BrianoNur for the help.
No one in the company has any clue to how it works so its helpful to know how its setup under the hood.
Thanks again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top