how enable BCM 2007 to recognize bcm 2003 data base?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a my bcm 2003 data base. It appears that BCM 2007 does not recognize
the (mdf,ldf). nor can I import it. BCM 2007 cannot select it not recognize
it.

If there is an integrity problem with the my 2003 database is there a way to
fix it so that 2007 will recognize it ???

Seymour
 
Seymour,

The following command is an example on Vista. Open a command prompt and
enter the following, replacing MSSmallBusiness with a unique database name
and point to your .mdf and .ldf files:

OSQL -S .\MSSMLBIZ -E -Q "EXEC sp_attach_db @dbname = 'MSSmallBusiness',
@filename1 = 'C:\Users\<USER>\AppData\local\Microsoft\Business Contact
Manager\MSSmallBusiness.mdf', @filename2 =
'C:\Users\<USER>\AppData\local\Microsoft\Business Contact Manager\
MSSmallBusiness.ldf';"
 
Hello-

I also am trying to migrate my bcm 2003 data into my bcm 2007 and tried to
enter what you suggested into the command prompt and got this error: failed
with operating system error 5 (access denied)

Any suggestion on how to fix this?
 
Hello-

I also am trying to migrate my bcm 2003 data into my bcm 2007 and tried to
enter what you suggested into the command prompt and got this error: failed
with operating system error 5 (access denied)

Any suggestion on how to fix this?








- Show quoted text -
Click to expand...

The current user must have permission to use Sql Server. Make sure you
are in the admin group and install BCM. That will create the sql
instance and you will have permission to create databases in it. Then
copy your mdf file to folder C:\Users\<USER>\AppData\local\Microsoft
\Business Contact Manager\.

Then, when you start Outlook, the BCM first use wizard will ask you
which database you want to use and your mdf should show up as a
database.

If it doesn't, cancel the BCM wizard, try the osql command, and
restart Outlook.
 
stupid question...how do I do this

The current user must have permission to use Sql Server. Make sure you








- Show quoted text -
Click to expand...

The quick answer is to install BCM yourself, with your login. That is
probably the case with 90% of users: one user per PC.

When that is not the case, then things get complicated and depend on
the details. Different versions of BCM have done things differently,
Vista handles permissions differently from Xp, the home versions of
Windows are different from the pro versions, PCs on domain networks
behave differently from standalone PCs, and so on. BCM is designed to
"just work" for the 90% case, and does the best it can with the
infinite possible other permutations.

I just checked the permissions in the BCM instance of Sql Server.
Everyone (the NT User group) has permission to logon to Sql, and
everyone has permission to create databases from Sql's master
database. That means that when a user runs BCM for the first time and
chooses to create a new database, BCM must connect to the master
database, create the database for that user, and then connect to and
use that database. There doesn't seem to be a permission for restoring
databases, so I suspect that all that's required to restore a database
is permission to create a new database. If that's the case with the
OSQL command, that it connects to the master database, from there
tries to create a database using an existing mdf file, and then fails
with a permission error, then the likely problem, in my experience, is
that Sql doesn't have permission to manipulate files in a folder it is
trying to use. I've seen that a lot recently on Vista. It didn't use
to be an issue because Sql used to run as administrator, but
permissions have been tightened up significatly with Sql Server 2005
and Vista. What's actually going wrong, causing the permission error,
in your case is going to depend on your particular circumstances, the
details. So, my advice, is to rerun the BCM Setup yourself.

If you already did that, then you could search this newsgroup for
"network service" (the login the sql service uses), and see what
worked for other users with similar issues.
 
Back
Top