Well, I've got it all working, finally. I can actually log into my
Domain as a Standard User and use BCM V2.
I THINK it was related to the .Net 2.0 or Visual Studio Beta stuff. I
read UseNet posts that Whidbey Beta installs (like mine) would mess up
BCM 2.0.
What I did to make it all work (some steps are probably not needed....)
Removed ALL instances of MSDE SQL databases.
Removed ALL Visual Studio 2005, SQL 2005, and other ASP.Net developer
applications.
Removed .Net 2.0 Beta
FIXED a weird problem with a Visual Studio directory, which was causing
severe errors. Halfway through finally re-installing SBA/BCM, I was
getting messages about "insufficient rights". But I was a DOMAIN ADMIN,
with full LOCAL ADMIN rights! And when I tried logging is as Local
Admin, I STILL got "insufficient rights" messages. I couldn't access or
delete an empty directory, the "Viewer" directory in Crystal Reports in
Visual Studio 2003 .Net. finally took ownership of the directory, gave
myself Full Control, Rebooted, and was able to delete the dumb
directory.
Despite errors and Outlook warnings the first time or two I log into
Outlook and enable BCM, it finally DOES work. I was able to import my
saved .BCM data records into the new MicrosoftSMLBIZ SQL database and
all is well.
Thanks for the info about the BCMUsers Group not being used in BCM V2.
Microsoft has no references to that deletion. I assume the BCMUsers
Group had special rights, either for the Registry, for for the MSDE SQL
databases, that a Standard User doesn't have. Apparently BCM V2 does
away with the need for the special rights.
|