ACT5 v. 7.0.4.82 can't open database on new computer/install

For clarification, you're trying to open a local database or a database on a networked computer?

- Clarification: we are  trying to open a databse on a 2003 sbs server.     ( However, in troubleshooting this I attempted to create a new local database, was not able to, error message says something about 'couldn't find master table'.   When i track that down on the act knowledge base, it says you need to reinstall act.    I downloaded the act removal.exe - it would not run, so i followed the instructions for a manual removal.  I also uninstalled xp service pack 3 (...in an attempt to make this workstation exactly the same as the other machines, which use act sucessfully)
update:  I have re-installed ACT and have the same issue:  error message says it couldn't connect to the database server and that I should disable any firewall software. (  i have disabled the windows firewall as that is the only firewall present)
starting to pull my hair out here.....

That error is usualy not a firewall issue... it just means it can't connect. Can you try all the items in the link from my first post?

Sounds like SQL didn't install properly.  That may or may not be the cause of your connectivity issue, but I suspect that's why you couldn't create a local database.  If you uninstall ACT! and SQL, install SQL manually from the CD folder Dependencies called SQLEXPR.EXE, you may run into the SQL problem.  The ACT! installer, when run normally, continues to race along even if the SQL install fails.

here are the items from that link with my comments in (quotes)

 *  The Share Database option is not enabled  (..database opens on others machines, so that's not it)
    * The .PAD file is damaged (...again, that's not it, the pad files opens for others
    * Your installed version of ACT! is different than the version of ACT! on the Computer hosting the shared database.  (....we're all running 7.0.482)
    * The MSSQL$ACT7 Service is not started or is disabled (the service is running)
    * Firewall or Anti-Virus software is blocking access to the database
    * Microsoft SQL Server 2005 is Installed ( nope )
    * The Preferences file is damaged  (... this I will look into )
    * You have installed Microsoft Outlook 2003 with Business Contact Manager (...no, it's not installed
    * Your database is damaged ( ...database is fine, works for other users)
    * The ACT! program is damaged.  ( it's a new install of the program )

- i'll look into the 'preference' file and report back

question for ActGuru:   in order to uninstall sql, do I need to uninstall the whole act program from this machine?

I'd also try to get that local database working - "new install" isn't a confirmation that you've got a good install.  Opening a local database, like the ACTDemo is though.

- thanks to everyone for their help. the client has asked me to contact a local act specialist (...we'll see if they still support act7).  I will follow up with what happens ( if they don't support it, i'll try GL's suggestion of a clean install following the outlined steps)
geek3

update:  we have been told by an ACT consultant ( who does custom database design) that the problem is with sql on the server ( our server is 2003 sbs premium) and that we need to have sql 'allow another instance'    ( perhaps I should post this question in another area.....also, if I was speaking with this person directly I would ask them:  why is Act not allowing me to create a local database then....seems to me there is more than one issue here..... but to clarify, all we are trying to do is to have this workstation be able to access the Act7 database on the server, just the way our 4 other machines have been for several years.)    any suggestions???
thanks
geek3

Yeah, you're right, that solution is inconsistent with both problems.  If you didn't already have the ACT7 instance created, the other machines shouldn't be able to access the DB on the server either.  You're also correct that it would have nothing to do with the ability to open / create a local database.

- update: i spoke with the ACT consultant directly who has explained the situation:  apparently,  sql never installed correctly on the local machine...which would explain the different problems  ( it doesn't show up in add/remove programs>control panel, even though it shows up as a service and can be stopped/started w/o errors of any kind)
we are going to have the client reinstall windows with sp2, and NOT install sp3, and not install any other software/update.   then we will install ACT.  thanks to GL and ActGuru  ( assume that if i post no further, re-installing windows and THEN Act did the trick)
~geek3

Doing the uninstall/reinstall would have completely removed SQL - it's one of the functions of the uninstaller.

geek3, as mentioned, the local install of SQL shouldn't have anything to do with not being able to connect to the ACT! DB on the server.  Reinstalling windows seems a little extreme, like repaving the lot to fill a pothole...

i trust you are correct, but the Act consultant said that the service needs to be running correctly on the local machine as well (???).....
i'll follow up and let you know what happens after the re-install  - .... the other option provided to the client was to upgrade Act and they opted out!    

With ACT! 7.0, the service did need to be running on the local machine

Upgrading is definately the best option .... historically, 7.0 was one of the worst versions

- update:   the client was able to get around this problem (...not upgrading the software...!)

  He re-installed xp sp2 (....and didn't  update anything from microsoft...i.e. did not apply  sp3 l)  Act7 was able to install/run the database on the server sucessfully.  It's just a guess, but I think installing xp service pack3 may have been the problem(???) ( even though we uninstalled it at one point )...
Thanks for your help.

while I haven't heard any specific issues re XPsp3, I guess not a lot of ACT!7 users still around... so it's possible.

If sp3 adds .Net 2.0 (does it?), that would cause ACT!7 to have issues as (despite MS saying different .Net frameworks wouldn't conflict), many .Net 1.1 apps (including MS's own) fail when 2.0 is added.

i'm not sure if it does (... the user had also install a version of quickbook...not sure which version, but that may have added it?)
going to close this question-thanks