Home Forums SQL Server 2008 SQL Server 2008 - General Error creating new db; "application is not configured for this database" RE: Error creating new db; "application is not configured for this database"

  • January 16, 2013 at 9:32 am

    #1577904

    cummings.rd (1/16/2013)

    Hi

    The DB I restored is 8.25 MB; I use SQL management studio 2008, I set the options for the restore as follows...

    Overwrite existing database WITH REPLACE

    Leave db ready ..RESTORE WITH RECOVERY

    The restore successfully completes BUT when I attempt to open the application the error is that the "...application is not configured for the db. Application will shut down"

    I can see the restored db in SQL studio 2008; should I have set my options to Preserve replication?

    Thanks for replying

    well you need to do two things, because it sounds like a basic setup issue.

    The application is reporting the database is not what it expects, so all you can do is check that the application and the database are where everyone expects them to be.

    #1: make sure the application's connection string information is actually pointing to that specific database. if the database is blank, it would probably connect to the master database, and you'd see the application report that same error, since it seems to be looking for specific objects that should exist and don't seem to.

    #2: Expand the database you say your restored in object explorer, and browse through the tables/procedures.

    do they exist, or is the folder empty, so all the objects are missing? that might be as simple as restoring the wrong backup.

    #3: The Login/USER that is being used: make sure that user actually has permissions to connect to that database; if that user did not have access to the dbo schema for example, it might look for dbo.MyApplicationSettingsTable, but not find it, due to permissions, and not due to non-existence.

    #4: You said you upgraded From version 3.00 to 3.03.

    were there any scripts that should have been run that changes the database to match this 3.03 verison, so if the app connects to a 3.00 database, it reports that error because it's checking/validating 3.03 verison objects?

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!