776 reputation
46
bio website SharePointInterface.com
location Cincinnati, OH
age 43
visits member for 5 years, 5 months
seen Mar 26 '13 at 22:45

I am the “Lead Bitsmith” and owner of Bitstream Foundry, a software and custom development company based in Cincinnati, Ohio. I have been developing software and crafting solutions for over two decades, and I’ve focused on Microsoft’s SharePoint platform since 2004. I possess a somewhat eclectic set of SharePoint skills that come from time spent in a diverse set of roles, including consultant, product manager, solution architect, team lead, administrator, and platform evangelist. I am an author, blogger, and frequent speaker/instructor at SharePoint conferences, user groups, and similar events all over North America. I can be reached through my blog (http://SharePointInterface.com) or Twitter (@spmcdonough).

My Book
My Blog
LinkedIn
Twitter


Nov
20
awarded  Enlightened
Nov
20
awarded  Nice Answer
Jun
26
awarded  Yearling
Jun
27
awarded  Yearling
Jun
27
awarded  Yearling
Jan
7
comment How to solve Access Denied errors with stsadm -o retractsolution
Adding an account to the "Farm Administrators" group in SharePoint Central Admin has absolutely no effect on that account's rights in SQL Server. Becoming a farm admin gives you rights (within Central Admin) to initiate actions that are then taken on your behalf by farm/timer service account via delegation ... but it doesn't alter any permissions on the databases for the user account in SQL. Becoming a farm admin is a SharePoint permission change only -- not SQL Server.
Oct
20
answered Install both WSS and MOSS on same machine
Oct
6
comment Are you required to use named instance for SharePoint DB?
+1 to Nissan for his response. In addition, I'd highly recommend the use of SQL aliases if you aren't already using them. They buy you a certain degree of portability/abstraction (between SQL and the SharePoint environment) and are invaluable in the event that you should have to (a) recover from catastrophic SQL failure, or (b) relocate your farm to another database environment.
Oct
2
comment Changing WSS 3.0 to point to a new SQL instance
This question and answer (recently asked here) may also provide some additional assistance, as well: serverfault.com/questions/66818/66836#66836.
Oct
1
answered How to remove a cumulative update from a SharePoint server
Oct
1
comment “Access Denied” on certain SharePoint SSP links
Goofy the way that works, no? For what it's worth, I've tripped over that one myself before :-)
Sep
28
comment Need to move all MOSS DBs to named instance
Good question. I typically use the SQL Server Client Tools to manage aliases, so I wasn't sure about cliconfg.exe (since they aren't the same thing - but serve the same purpose). With a little checking, it would appear that cliconfg.exe is part of MDAC's (Microsoft's Data Access Components) distribution; I based that on Dan Guzman's response in the following chain: sqlnewsgroups.net/sqlserver/t1394-server-name-problem.aspx. Given that an MDAC distribution of some sort is on nearly every system these days, you're more likely than not to find it on a system regardless of MOSS.
Sep
25
comment Need to move all MOSS DBs to named instance
You also asked about SharePoint being built to check aliases. To be clear: this isn't a SharePoint behavior -- it's a SQL Server Client library behavior. Any SQL Server connection string can use the alias you established -- not just SharePoint. As I may have mentioned, this is commonly done for abstraction purposes to provide a certain level of location transparency to SQL operations for things like mirroring failover, DR, etc. Aliases are also commonly leveraged to map client access to SQL Servers running/listening on non-standard (i.e., non TCP:1433) ports.
Sep
25
comment Need to move all MOSS DBs to named instance
First off ... WOOT! That's great news, Agent; I'm glad that the aliases look to be (generally) working for you. You asked about SQL Server, aliases, and DNS. Your comparison to the HOSTS file is on-the-mark -- The SQL client will check for a local alias match before concluding that a connection string refers to a server/host name on the network. This behavior is specific to SQL server connection strings and database access Non-SQL access, on the other hand, will continue to use HOSTS and DNS for the resolution of endpoints. Aliases only affect SQL client connections. Does that help?
Sep
23
comment Need to move all MOSS DBs to named instance
Interestingly enough, I'll be in a position to test this soon myself. I'm building a new database server for one of my farms in the next week or so, and aliases aren't in use (due to an incompatibility between their use and DPM 2007's operation). As part of the move, I'll give this a shot (using aliases) and report my results, as well!
Sep
21
comment SharePoint Forms Site Administrator Access Denied
I believe the reason for this is because there isn't equivalence between the FBA username (which is probably something like "MyUserName") and the standard NTLM-based logon username (which is something like "MyDomain\MyUserName"). Make sense?
Sep
21
comment SharePoint Forms Site Administrator Access Denied
Another thought, Becky, came to mind when reading your comment: did you extend the central administration site with the additional provider information before granting the admin user full control? Though the admin account/user that you need to add (and grant full control to) already has a policy set, I believe you need to setup a second policy that will cover logins through the FBA provider (since username formats differ). To do this, you need to modify the central admin web.config with the additional provider info (which you have) and create a policy using the FBA-based username.
Sep
21
comment Need to move all MOSS DBs to named instance
I would expect a new alias to take effect immediately, but that's an educated guess. To avoid serious problems, you'll want to ensure that farm members aren't trying to connect while aliases are being established. The easiest way to do this would be temporarily take your SQL servers offline; alternatively, you'd need to shut down all SharePoint-related services (OSS, W3SVC, timer service, etc.) on all members. If you have VMs, I'd recommend testing a process there first to avoid prod problems. Your final point about aliases is accurate -- you'd be using SQLSERVER going forward. Good luck!
Sep
19
answered SharePoint Forms Site Administrator Access Denied
Sep
19
comment Need to move all MOSS DBs to named instance
Sorry that I didn't have a better answer for you. The issue is specifically with SharePoint configuration databases; they maintain references to server/host names and the database server instance names. WSS and MOSS are sensitive to environment changes for this reason. I don't think you're completely up the river yet, though. See if you can skirt the issue with SQL aliases (steps #1 through #4) in your current environment. I have some hope that it'll work for you. I would definitely like to hear how things work out. Good luck!