Installation issue -- Invalid object name 'ac_Stores'

[CaptainPalapa]

So....after getting the folder-based permissions all correct, and getting the database.config pointed to the correct, empty database, with all the SQL-based roles assigned that were indicated in the getting started guide, I'm now getting "Invalid object name 'ac_stores'."

It would seem obvious to me (a developer!) that the system is looking for a table that doesn't exists. But isn't this the point of the /install/ folder? To do that for me? Or is there some manual SQL script I'm supposed to run.

Any help?

Thanks,
Will B.
(Using AC7 trial prior to purchase!)

[jmestep]

The second step in running the install is where it sets up the database. Did you enter the database info into the config file? The install prompts you for that in a web page during the install process, then proceeds to build the tables in the database.

[CaptainPalapa]

Actually, no...there were no screens that asked me. After getting the configuration (IIS, permissions, etc) that would prevent typical issues, I got some error about not being able to connect to the database. So I found the database.config file, updated all the info to match the new SQL Server instance...and voila! Got the error in my original post.

Any further thoughts?

By the way...I see you post a lot in these forums! That's really helpful of you. I have yet to receive any response from AC on support tickets from Thursday and Friday. I guess if I should decide to go with AC (which I'm starting to question now), I'll have to rely on the forums or my own good luck, right?

[AbleMods]

It sounds like you didn't create the initial database instance in SQL prior to running the AC7 install script.

When I do an AC7 install, I create the initial database. The install script will create the tables for you in step 2 as Judy described, but I still make the initial database.

Go into your SQL Management program and drill down to the databases level. Is there a database created? You should be able to choose this database during the install steps of the AC7 install page. You shouldn't have to modify the database.config file at all to make a successful installation.

What OS platform are you installing to?

By the way...I see you post a lot in these forums! That's really helpful of you. I have yet to receive any response from AC on support tickets from Thursday and Friday. I guess if I should decide to go with AC (which I'm starting to question now), I'll have to rely on the forums or my own good luck, right?
Actually, no...there were no screens that asked me. After getting the configuration (IIS, permissions, etc) that would prevent typical issues, I got some error about not being able to connect to the database. So I found the database.config file, updated all the info to match the new SQL Server instance...and voila! Got the error in my original post.

Any further thoughts?

By the way...I see you post a lot in these forums! That's really helpful of you. I have yet to receive any response from AC on support tickets from Thursday and Friday. I guess if I should decide to go with AC (which I'm starting to question now), I'll have to rely on the forums or my own good luck, right?

Able's philosophy with the forums in the past has been a "users helping users" mentality. They do show themselves when their time permits, however the first priority is their product(s) and the forums a distant second. No response to any support ticket would be a concern for me - support is key to any product of this type regardless of your in-house schedules or deadlines.

[CaptainPalapa]

Absolutely...I have definitely done the database instance portion. (I've been programming and building db's for about, oh, 15 years or so.) So, I created the database instance, the user has appropriate logins (and now full dbo access, as well). The information in the database.config file is all correct. (And since the system seems to know that the tables don't exist, I'm assuming it can connect.)

I believe in your post, however, you mentioned that the install would ask me for the information? If this is correct, perhaps I made the mistake of providing the database.config modifications, when I shouldn't have? Maybe that's why the system is skipping that step. I'll re-unzip the files, re-establish file permissions, etc. and see what happens then. Afterwards, I'll post another update.

Thanks for the help.

[AbleMods]

I'm not sure what the install page will do if it sees an existing database.config - my guess would be it does skip that part.

I agree a restart of the whole process would be a good idea - at least now knowing the perms issue won't get in the way, the install script should run straight through without error.

Let me know - I'll help any way I can.

[CaptainPalapa]

Indeed. Sure enough...I deleted all the old files, copied the new ones in, modified the permissions, went to /install/ and it gave me the install, etc. The problem, apparently, was that I had modified the database.config file with all the necessary information. Honestly, though....I did that, because at some point it indicated it couldn't get to my database. Probably because I tried the site, not the install folder.

The other problem that I initially had was something about needing to setup an application pool in IIS. I don't totally understand this, as I'm a Coldfusion guy, not a .NET guy! But a buddy of mine understood it...and got it corrected for me.

I know I'll be back...thanks for all the help provided in the form of replies!

[AbleMods]

Glad you got it working - we're here if you need more help

[Logan Rhodehamel]

The problem, apparently, was that I had modified the database.config file with all the necessary information.

Yes, that's it. There are certain services (like URL Rewriting) that we can't enable prior to installation. The way we determine this is by the connection string. If a valid connection string is present, we assume the database is created and enable these services.

[joea84]

Hi,

I saw this error on my local machine, but things worked fine in production. You can't use windows authentication. You must used mixed authentication on sql server. Create a sql user name and password and give that user dbo permissions. When doing the connection string, put that user name and password in.