Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Error creating new db; "application is not configured for this database" Expand / Collapse
Author
Message
Posted Monday, January 14, 2013 1:18 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, April 03, 2013 8:56 AM
Points: 6, Visits: 13
I have a db that I am trying to export from a slightly older version to a newer version. Vendor says the db structure is the same. Both are created on SQL 2005, schema should be the same. App version moved from 3.0.x to 3.0.3 so no big change.

I installed the 3.0.3 app and deleted the default (empty) db. Then I ran this script.
USE master;
GO
CREATE DATABASE SLMD_ABP
ON (FILENAME = 'C:\Database\SLMD_ABP.mdf'),
(FILENAME = 'C:\Database\SLMD_ABP_Log.ldf')
FOR ATTACH;
GO

I refreshed the view so I could see the new db. Now when I try to open it I get this message ...
"The application XXX is not configured for this database. The application will shut down".

Any ideas on what I can do to resolve this. There is no support coming from the vendor.
Post #1406922
Posted Monday, January 14, 2013 2:18 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 3:11 AM
Points: 12,744, Visits: 31,066
i'm guessing that the application does not expect an empty database...it expects a database with specific tables, procedures, views etc to exist, but probably many of those objects are allowed to be empty(as in now ROWS of data) for a new installation.

it looks for a certain table, and if it doesn't find it, it knows the "database is not configured for this application", and bails out.


Lowell

--There is no spoon, and there's no default ORDER BY in sql server either.
Actually, Common Sense is so rare, it should be considered a Superpower. --my son
Post #1406946
Posted Monday, January 14, 2013 2:30 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, April 03, 2013 8:56 AM
Points: 6, Visits: 13
I may not understand correctly what you are stating so please bear with me. The database I am transferring isn't empty. It has lots of information across the tables.

I am upgrading the application which requires an uninstall of the old app to install the new app. I wouldn't uninstall the old until I was certain the new could recieve the db from the old. So I am testing it on another Win 7 computer.

I was wondering if there was some step I should have made before I created the backup, copy of the detached db and simple copy of the db folder to prepare it for the move to the new app? There were no active connections when I performed any of these steps.

Thanks for replying !!
Post #1406947
Posted Monday, January 14, 2013 2:35 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 3:11 AM
Points: 12,744, Visits: 31,066
cummings.rd (1/14/2013)
I may not understand correctly what you are stating so please bear with me. The database I am transferring isn't empty. It has lots of information across the tables.

I am upgrading the application which requires an uninstall of the old app to install the new app. I wouldn't uninstall the old until I was certain the new could recieve the db from the old. So I am testing it on another Win 7 computer.

I was wondering if there was some step I should have made before I created the backup, copy of the detached db and simple copy of the db folder to prepare it for the move to the new app? There were no active connections when I performed any of these steps.

Thanks for replying !!


that seems to be the issue: the command you pasted(CREATE DATABASE SLMD_ABP)
creates an empty database...that's not what you wanted.

you've got the plan mostly right: you need to backup the existing database, copy it to the other server, and RESTORE the database as the name of your choice. just copying alone is not enough...you need to run the RESTORE command; probably through the GUI, since it can help you the best.


Lowell

--There is no spoon, and there's no default ORDER BY in sql server either.
Actually, Common Sense is so rare, it should be considered a Superpower. --my son
Post #1406950
Posted Monday, January 14, 2013 3:20 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, April 03, 2013 8:56 AM
Points: 6, Visits: 13
I may not understand correctly what you are stating so please bear with me. The database I am transferring isn't empty. It has lots of information across the tables.

I am upgrading the application which requires an uninstall of the old app to install the new app. I wouldn't uninstall the old until I was certain the new could recieve the db from the old. So I am testing it on another Win 7 computer.

I was wondering if there was some step I should have made before I created the backup, copy of the detached db and simple copy of the db folder to prepare it for the move to the new app? There were no active connections when I performed any of these steps.

Thanks for replying !!
Post #1406959
Posted Monday, January 14, 2013 3:21 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, April 03, 2013 8:56 AM
Points: 6, Visits: 13
Oh man, thanks for pointing that out. I'll try the restore operation. I appreciate the help.

Post #1406961
Posted Wednesday, January 16, 2013 9:14 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, April 03, 2013 8:56 AM
Points: 6, Visits: 13
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
Post #1407913
Posted Wednesday, January 16, 2013 9:32 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 3:11 AM
Points: 12,744, Visits: 31,066
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

--There is no spoon, and there's no default ORDER BY in sql server either.
Actually, Common Sense is so rare, it should be considered a Superpower. --my son
Post #1407935
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse