SP 2010 Keeps prompting for Credentials

Whenever a user tries to edit a document in SP 2010 (Excel, Word, etc), they are able to click edit document and then it loads up into Word or Excel and keeps on nagging you for your domain credentials. If you add your proper credentials it still comes back.
I guess the fact that it lets me click the edit document or check out button that my account has proper permissions. I've tried the recommendations of putting the fqdn into my trusted sites. I even get it without using the fqdn (https://sp)
Thanks! This is really bugging me...

More Related Resource Links

Hi,
I have CBA setup successfully on my sites. One site is setup for anonymous access and I have disabled "client integration" on that web application.
I have a list of MS Office documents on a wiki. When I click on one I am asked to either save or open or cancel. Saving works fine but when I choose open, it launches the associated MS Office app. I am then prompted for a login from CBA.
I can click cancel and the logon screen appears again. After clicking cancel the 2nd time the document appears in the MS Office app, Word in this case.
My question is how do I prevent my users from being prompted for a CBA login when clicking on these files and opening them in the native app on their machine?
--TR

I have a sharepoint document library
http://mycompany/sites/documentLibrary. When browsing to this site through Internet Explorer on a terminal server I can get to the site without being prompted for a username and password, which is what I want. The site appears as "local intranet" according
to IE.

When browsing to the UNC path \\mycompany\sites\documentLibrary we are being prompted for a username and password. After putting in the credentials the document library displays. I need for the server to be able to access the site via UNC path without being
prompted for credentials as we have several in house applications relying on doing so

The funny thing is this was working until recently. What's changed? I have no idea. I have an almost identical terminal server on the same subnet/OS/windows patch level that allows access without prompting for a username or password, and the only thing I had
to do for that server was enable the web client service..

Things I have tried so far:

- Checked the Web Client service is enabled, started and set to automatic. Restarted the server just to make sure.
- Added http://mycompany, \\mycompany etc to the trusted zone.
- Set the truste

Is there a solution to resolve the constant "Prompts" For user id's and passwords when a person tries to open/launch/edit office documents from sharepoint 2010.

My setup: sharepoint fqdn in the domain sp.domainname.local, The sharepoint server is a member of this internal domain. In dns I have local zone of sp.domainname.com with a cname that points to the internal sharepoint server. There is no issue
in users accessing the server both internal and external, The issue arises when Office documents are launched from SP2010.

In central admin I have configured the alternate access mappings to be
http://sp

I have also tried putting the fqdn dns name of the sharepoint server in IE8 trusted zone but
no luck, I still get credential prompts.

I think the issue might be that Office does not see that the files are coming from the fqdn of sp.domainname.com so hence the prompts.

Trying to fix this as right now its a total pita. I found some previous posts on this issue with SP2007 but found nothing that really addresses this in SP2010.

I have a report that is filtered with the User!UserID parameter, and I want to make it prompt the user to enter credentials or at least make the user select his credentials from the drop-down list of the parameter.

I have a 2 web applications configured. One web application is configured for an Intranet and the other is configured for a MySite. These web applications are accessed internally
and externally. With the internal applications I'm using integrated windows authentication and with the external applications I'm using basic authentication.

Everything works great except when I access the application externally. I obviously have to authenticate to 2 applications, the Intranet application and MySite application. The
issue is when I initially access a page on the Intranet that has user profile pictures from the MySite on it. If there are 6 profile images on the page then I'm asked to authenticate 6 times to the MySite web application. If there is 1 profile image then I
only have to authenticate once. Once I leave that page then I don't have to authenticate again.

Why do I have to authenticate for each profile image? Why can't I just authenticate authenticate to the MySite once?

This post covers another useful improvement in VS 2010 - HTML/ASP.NET/JavaScript snippet support. Snippets allow you to be more productive within source view by allowing you to create chunks of code and markup that you can quickly apply and use in your application with a minimum of character typing.

Visual Studio has supported the concept of "snippets" for VB and C# in previous releases - but not for HTML, ASP.NET markup and JavaScript. With VS 2010 we now support snippets for these content types as well.

.NET 4 includes a new version of the CLR, and a new .NET 4 specific machine.config file (which is installed side-by-side with the one used by .NET 2, .NET 3 and .NET 3.5).

The new .NET 4 machine.config file now automatically registers all of the ASP.NET tag sections, handlers and modules that we've added over the years, including the functionality for:

.ASP.NET AJAX .ASP.NET Dynamic Data .ASP.NET Routing (which can now be used for both ASP.NET WebForms and ASP.NET MVC) .ASP.NET Chart Control (which now ships built-into ASP.NET V4) What this means is that when you create a new "Empty ASP.NET application" project in VS 2010, you'll find that the new default application-level web.config file is now clean and simple:

Designing new functionality on existing applications can be daunting. There are always differences between the original design and the current implementation.

The new Architecture tools within Visual Studio Team System 2010 help you understand the application you have, design new functionality you need, and validate that your design and your implementation do not deviate.

In Visual Studio 2010, we've made several enhancements to our two most popular languages, Visual Basic and C#, to give programmers all the tools they need to build great software no matter which language they prefer.

The Visual Basic team focused on adding productivity features to the language so developers can get more done in fewer lines of code. The most common customer request for Visual Basic is to remove the underscore ("_") character when breaking a code statement across multiple lines in most cases. Visual Basic 10 introduces implicit line continuation, which removes the need for the underscore character in most cases.

When you first run VS 2010 it prompts you to select an IDE profile to use. The profile you select will configure how tool windows are displayed/docked in the IDE by default and set the default keyboard shortcuts. You can then customize any of these settings by using the Tools->Options menu within the IDE and then override/change them. You can also later reset your profile and pick a different one by choosing the Tools->Import and Export Settings menu command.

VS 2010 and .NET 4 are the next major releases of our developer tools and framework. Together they contain a ton of new functionality and improvements that I think you'll really like, and which make building applications of all types easier, faster and better. The improvements range from nice small tweaks to major, major enhancements - and can be found across the .NET Framework, the languages, and the IDE.

Many exciting changes for ASP.NET are coming in the .NET Framework version 4. This document gives an overview of many of the new features that are included in the Beta 2 release of the .NET Framework 4 and of Visual Studio 2010.

This is a big deal. This isn't ".NET 3.6" - there are a lot of improvements of .NET 4, and it's not just "pile on a bunch of features so you get overwhelmed." I've been working with and talking to many of the teams involved and even though it's a cheesy thing to say, this is a really customer-focused release.

There's a lot of stuff that's new and added in .NET 4, but not in that "overwhelming-I-need-to-relearn-everything" way. More in that, "oh, this is way easier/simpler now" way. Like, moving data around with ADO.NET DataServices is easy, binding with client templates is easy, there's F# if you need it, the "dynamic" keyword if you need it, Silverlight's already installed, oh, and the parallel stuff will freak you out, but in a good way.

As you probably know, Visual Studio 2010 was announced earlier this week and it contains a lot of cool features and project templates for SharePoint developers. Below is a short overview for some of the SharePoint development related features and project templates.

In case there is an exception anywhere in the SharePoint 2010 project (most common place an exception would happen is during deployment of your SharePoint project, custom deployment configuration or custom deployment steps), there's a registry key EnableDiagnostics available for you to use.