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!

Mas 90 Client Print errors

Status
Not open for further replies.

Ossymoon

IS-IT--Management
Oct 22, 2003
5
US
Good Day
I am having some trouble with printing with mas90
The Server side of mas recently when through an emergency server change, when the old server crashed. Everything appears to be working except prininting. Mas does not seem to find the new location of the reports for Crystal. I checked the sota.ini and it correctly lists the path. I can copy and paste that path into windows exploroer and get where the reports are. When I try and print however, I get an error, but I notice that \ on the path is switched too // instead of \path://devel/apps/Mas90
error says
cant find //devel/apps/Mas90/...
Any ideas here?

Thanks
Ossymoon
 
I figured out what the problem was...

The user groups didn't have write access to the MAS90 server directory and data files. When they were adding data though mas90 itself, it looked as a system service writing, which was ok, but when crystal reports kicked in to print, It switched to the NTFS group permissions, which were not allowing write access. I have since fixed this, and everything started working


Everyone have a good weekend
Ossymoon
 
Ossymoon,

I have a similar problem too. When we tried to print graphical form from workstation, error message indicates 'unable to locate reports file'. But it works fine when we printed the report from the server. I checked sota.ini file but could not found any path setting. Here is the path of our server....//account-server/mas90....Is there a way to defeat this problem?
 
Smai

First, lets look at the sota.ini file
servers paths should look something similar to
1=server:port:alias=something:path=\\server\share

Next look at your NTFS or file system premissions for the folder mas is located, your mas users should have READ AND WRITE premission to the folders under mas. That was the origianl problem i was having, they could see the share, see into the folders but they didn't have write access, so it was erroring out

Ossy
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top