Successmaker - Ugh.....
hi all, just replaced our aging DC's here and one of the requirements is to continue the use of Successmaker till somthing else comes along that is better.
i have migrated over the server end with ease and i hope with some success to folowing the RM notes. However now i am stuck on the client end of things.
Installation goes ok until i get to the ODBC setup part which i cannot fathom out the details for.
IP: (Succesmaker server)
Port : 2638
Database name: (SMS i assume)
Datasource name: (dont know)
Password: ******** (autofilled for me)
Clicking next >>
Error installing ODBC
DriverName=Adaptive Server Anywhere 8.0
Description = Error Calling ODBC API
Adaptive Server Anywhere 8.0
this is on a Windows 7 machine.
One concern for me is that the notes specify that the old RMPublic drive is used, this is currently my new shared drive letter do i need to use this or used the method in other posts of moving the information to a local drive and subst it ?
Appreciate any help given here.
Have a look here, this may give you some tips.
You do have my sympathies, as Successmaker is pretty awful the way it runs and feels very old. As far as I'm aware, RM no longer sell Successmaker anymore.
Unfortunatly i am running an old version 1.3 and some of the points listed do not apply to me.
I have been in touch with RM and they want money £50 for support. But then that does not ensure that i can get this off the ground.
Its a shame as many people are still using this and no sign of any replacement other than gossip that person were taking it over..........
I dont think it works on a Windows 7 machine unless you have the latest version.
It was too much hassle to do a full new server install so we just stayed with the old version on Windows XP.
I suspect eventually a web version will be published. There's nothing (from what I remember) that would stop it doing so, but it'll need completely re-working and would probably run off MySQL or MS SQL as its back end.
Try the database and datasource name as sme (though if it shows as sms in Sybase SQLA then use that). We have an even older version, which runs stably on Windows 7 x64 clients. Somehow. Took a fair bit of tweaking, the server is still on 2003, and it'll be staying that way!
i dont pretty much that with creating a VM with 2k3 and only SMS. bit of a waste but after reading a few threads seemed the best an easiest way to get this online.
These are Win732bit machines if that makes any odds.
Do i need a sybase driver installing on the machine.
Got slightly different error after adding SMS in the DSN part.
"Error connecting to DSN 'sms', check your ODBC setup information and try again."
This has nothing to do with your post what so ever but thought I'd mention it as you have reminded me, was looking through my old store room the other day when I cam across.. A disc with Successmaker on it for Windows 95 :)
Those where THE days!
Your a legend, that worked. Thank you. just got to make sure it all works now :-/
A disc with Successmaker on it for Windows 95 http://staticc2.cdngeek.net/images/smilies/smile.png < When i started here i found many old software titles on 3.5" floppy !! and a sealed copy of Veritas backup. !!
I hope this thread helps someone else in the future.
Those where THE days!
The working solution incase someone else needs this !!
IP: (Your SMS Server)
Port : 2638
Database name: sme
Datasource name: sme
I've just come across this thread and although I see that you found the details you required to complete the setup, SuccessMaker Enterprise 1.3 doesn't support operating systems beyond Windows XP and Windows Server 2003, so may not behave as it should.
RM SuccessMaker customers can order a free of charge installation pack for SuccessMaker Enterprise 1.7.2 which supports Windows Vista, Windows 7 and Windows Server 2008 including R2 from RM Sales. Details about this version, how to order it and how to install it are in this Knowledge Library article: SuccessMaker Enterprise 1.7.2 installation guides The installation pack and licence codes are available free of charge whether or not the customer has a current support contract.