Topic: Sage with SME

[tariqf]

Hi I have a few clients who use Sage line 50 and line 100 products on their network. I understand these need a central SMB share for the data and hope to use SME samba to achieve this.

Has anyone experience of using Sage products with SME? Any pointers or advice would be much appreciated.

Thanks

[mdo]

We are using Sage (can't remember whether it is Line50 or 100) on one server (SME 6.0) without a problem. We created it's own ibay (share) and disabled opportunistic locking on that ibay just to be on the safe site.

The easiest way to disable this is to use a contrib called "Advanced workgroup" which you can search for in the forums.

Hope that helps.
Regards,
Michael

[giganoob]

sry for my english but ...

u can share files for Line 50 or Line 100 without any problems.

But you ll never work more than one person at the same time. Sage's program need a particular a server portion wich should be installed on a Windows server, mac server ou netware server.


Giganoob

[ReetP]

I have Line 50 V7 on a 6.0.1 box with several users.

Just did an install to it's own folder on the server and away it went....

Didn't bother with the locking, though perhaps I should ? Hasn't appeared to be a problem.

[tariqf]

Hi I found it very difficult to believe you could only have one concurrent user! I found this in the redhat forum that should do the trick although I haven't tried it yet...in smb.conf

[sageline50]
path=/home/netapps/sageline50
writable=yes
browsable=no
create mask=077
directory mask=077
veto oplock files=/*.mdb/*.MDB/*.ldb/*.LDB
locking=yes
share modes=yes

[jackl]

I have Line 50 V7 on a 6.0.1 box with several users.

Just did an install to it's own folder on the server and away it went....

Likewise we have one SME server hosting the sage data files for multiple companies with multi user access without any problems to date. Each company has it's own iBay with appropriate rights. We were told many things by a Sage agent ..that it needed to be running on the server to allow sharing etc. When informing them that it was already running on the server, we were told that that we must be mistaken and that it must be running on the server and that we were not aware of it. We were going to ask them when did they release the Linux version of Sage, but decide best to end the correspondence with them at this point.
I know in the past (2002-2003) there were issues with Sage on samba regarding file locking but can't recall what they were, presently we are runing Sage on samba 3.0.7, and all seems fine.

Regards
Jack

[tariqf]

Jakl if you have time would you mind putting a quick how-to on here for setting up an ibay for sage like yours?

This would be grately appreciated. I'm hoping to persuade one of my windows clients to dump their 2000 server for an SME box and I don't want any embarassing problems!

[jackl]

tariqf

In the case we dealt with it Sage was installed in a workgroup environment on a workstation that held the main Sage application and data. We identified which folders held the data for each company and moved each to it’s own share on the SME box. Using server-manager create a group for each company and a share for each company, giving only the relevant group read and write access accordingly. Map each share as a network drive  and then reconfigure the Sage clients to point to the new location.
From information given to us we thought originally that the main workstation would also have to be on for this to work, however we found that all clients worked away ok with the data alone on the SME server (6.0.1).  However to install a new client to a new computer there is a file called “netsetup.exe” in the shared Sage folders on the main workstation that you need to run.
Your case is different in that it is installed on a server you wish to dump. In that case I would create another share on the SME for the application (Sage) and the just follow what Reetp says in his post and as mentioned use the data shares to store the data. Also give neccesary user  access to the application share.

Rgds
Jack

[ReetP]

If I remember correctly, from server manager make your ibay on the server with relevant permissions for the users.

From a workstation run the normal setup but rathe rthan installing locally i.e c:\Line50 install it to a folder in the ibay that you have created - e.g. s:\Line50.

After that and as mentioned earlier, run netsetup.exe from the server from each client machine.

Sit back, make tea, .... or something   and relax in the knowledge that another W2k box has bitten the dust and the world is infinitesimally better off.

Job done.

Now, if I could just sort out my bloody raid   problem I'd be a happy bunny

[p-jones]

Have a client running Line50 V10 on SME6.0.01 and it just works. Set up an iBay, assigned permissions and off it went. (Actually we started with V8, went to V9 and now V10)

5 users, client setup on each w/station and point to data on SME ibay. Couldnt have been more simple or more smooth.

[Peter]

Been running Sage since SME V4 and SAGE V7 to and including V11 with Multi Company and single users. Install with confidence it just WORKS.

[slepmog]

Ha at last an airing for sage !

Have been working on this and doing some tests.  Have tried sme with oplocks turned off and it is disasterous for the speed.  Done a test with two pc's connecting to sage and it appears to work. Not been brave enough yet to switch over 8 pc's arrrgh the work !

A couple of points.  Sage have frequently recommended to me to use the full install and not the netsetup - dont know why but.....

If you want to amend the data locations, go to the sage\ accounts directory and dig out the company0 file - its a breeze.....

There is a sageforum.co.uk that is the only bb that I know relating to sage.  Good for some bits but best of all some speed trials performed by a muppit http://sageforum.co.uk/viewtopic.php?t=915
Dont think I will every do them again but it gave me a feel of what is going on.

I think there has been some slowing down of sage in V11 to knock out more than 5 users from a practical point of view.