We currently have an application that works with Outlook 2003. In order to get the owner of a shared contact folder, we simply call:
Redemption.RDOSessionClass.GetFolderFromID() and then took that folder and got the RDOFolder.Store.Name property.
However, when trying this with a shared contact folder in Outlook 2007, the RDOFolder.Store.Name is null.
Everything still works fine for normal contacts and for contacts in "Additional Mailboxes" that I've added to my account.
The approach mentioned in http://blogs.msdn.com/mstehle/archive/2006/09/07/744798.aspx appears to work, but I would prefer to not release a new version of our application unless I have to.
Basically I want to understand why this is working differently and what I can do, if anything, to fix this from the server end.
Edited comment : see http://msdn.microsoft.com/en-us/library/bb147715.aspx
Some thoughts...
Do you have Download Shared Folders (enabled by default in Outlook 2007) turned on in your profile? My initial guess is that the shared contact folder contents are being cached in your local store and the store name property is no longer valid.
Does it actually return null or throw an exception?
Do you have Outlook Spy? Invaluable tool for sleuthing this kind of issue, especially if using Redemption.
Have you posted to the Outlook Programming discussion group?
"There is nothing you can do, this is just how the Exchange provider is
implemented." -Dmitry Streblechenko (MVP)
Related
This is the error I get
The rest of the description:
There were some changes made on the mobile version of the app,
adfs was installed and set to ifd claim base authentication,
There were also changes on site map.
Thank you
Most likely you corrupted your site map (or whoever made the edits corrupted your site map).
The only way I know how to fix this particular error is through XRM Toolbox, Sitemap Editor plugin.
You will need to get the Sitemap XML from a different CRM instance that has all of the same customizations and MSFT solutions installed (Dev or Test should suffice). Once you have that Site Map XML, copy and paste it into your "Corrupt" sitemap XML, and save/publish the changes from XRMTB. You should be back in business.
For some time, I get an error when I try to log into my Microsoft account from Visual Studio for my Azure subscription.
My Microsoft account is associated to : Outlook.com (obviously), Office 365, Azure and a Windows Developer.
I ignored this message until now, because I could connect to my database, my websites functioning, etc.
But now I need to publish an application in the Windows Store. When I try to generate my Windows app packages, I found the same error:
We could not refresh the credentials for the account
AADSTS50059: No tenant-identifying information found in either the request or implied by any provided credentials.
Trace ID: eaf34263-377e-41d3-8f72-177827315914
Correlation ID: 15bbcfe8-8bc9-4a83-aa02-288a54e50dd5
Timestamp: 2016-09-19 11:27:20Z
I have already try to clean up cookies, temporary files, another Windows developer account, ...
UPDATES
I have try to download Azure AD Application Proxy Connector.
I had this same problem again on Visual Studio 2017 (15.1).
Solution found:
You have to go to REGEDIT.
Navigate to "Computer\HKEY_CURRENT_USER\Software\Microsoft\VSCommon\ConnectedUser"
And empty all the values, except EnableAzureRMIdentity (change to true if isn't) :
To :
It seems that you’re trying to sign in through a Microsoft account and not a domain that is part of the organization ID of the directory you are trying to access.
So please make sure that the admin is part of the same domain name as the tenant domain.
For example, if your Azure AD domain is contoso.com, the admin should be admin#contoso.com.
You could refer to Troubleshoot Application Proxy.
Moreover, this thread might be helpful to you. Please also try the answer provided by Rich.
I followed some of the advice for this error, including modifying my registry key, however the error changed. And it seems that the #Andrés Talavera is also using a sovereign cloud like I am.
I deleted my Environment Picker JSON file and that is when I got this error when I restart Visual Studio.
After deleting the JSON file, located here: %localappdata%\.IdentityService\AadConfigurations\AadProvider.Configuration.json, I restarted VS17 and I got this error. The JSON file seemed to reappear after the restart. The next time, after I deleted the Registry Key, and removed the JSON file again, SSO worked great.
Note: It seems to be associated to the Environment Picker and pointing to the Sovereign cloud AAD.
I'm using tfs and when I try to request a code review I get the error in the image bellow. I am able to perform check-ins and shelves.
The other users from the team that I am in are able to request a code review from the same user and in the same path that I am using.
If all of your team users except you works well. I was wondering if it is related to your VS.
For this issue, you can try below methods to see if you can fix it:
Repair your VS
Try to delete TFS cache by going into default C:\ {User Profile
Folder}\AppData\Local\Microsoft\Team Foundation\x.0\Cache and VS
cache in Appdata folder.
Try to use your account on another computer or use another account
on your computer to request a code review.(Make sure your account of
permissions without any problem)
We have a an ASP NET MVC website solution which only one out of three devs on the team is able to publish to the live server. When I, and another colleague, attempt to publish the site from VS 2010, the output window will display an error:
Unable to create the Web site
'\blah'. The path '\blah' does not
exist or you do not have access. The
specified path is invalid.
This points to a logon issue which my account, but the developer who can publish the site is a member of all the same user groups as me. As a long-shot, we gave Everyone full access to the folder, but this did not resolve the problem.
Can anyone suggest a more detailed way to try and figure out why we cannot publish the site? There must be a permission set somewhere that is allowing my colleague to publish the site from Visual Studio.
I had this problem and racked my brain trying to resolve it so I wouldn't have to copy the publish files to a remote server manually. I spent a great deal of time actively trying to get this to work.
Here's how I solved the problem: I went to File>Open in Visual Studio 2010 Express and navigated to the remote server (\\255.255.255.255\folder1\folder2\folder3 and so on). Right away I was challenged for a User Name an Password. I entered the credentials for the REMOTE server, checked the box to 'Remember my credentials'. I immediately tried to publish and voilá - it worked like a charm.
I hope this saves a lot of people a lot of time.
I had this issue - certain members of our team were able to publish directly from VS2010, whereas for some reason I was always getting permission denied errors, even though we were all able to connect to the server we were trying to deploy to. I fixed it in the following way:
Go to "Server Explorer".
Right click "Servers" and go to "Add server..."
Type in the name of the server you are trying to connect to, and then click on "Connect using a different user name..." - put the credentials for logging into the server in here.
Click OK and wait for it to add the server.
Now try and publish to that server and it should be ok...
Not sure why I needed to do this and others were able to deploy without adding the server in this way... remains unexplained.
According to the comments below:
You may need to restart Visual Studio in order for this to take effect.
This should also work for newer versions of Visual Studio
Faced the same problem today. In my situation I had to close VS2010 and open it NOT as an admin and it worked without any problems.
This got me for a long time...Go to Project - Properties and select the Package/Publish Web tab. Under the header "Web Deployment Package Settings", there's a ellipsis button that you can use to map to the location you want to publish. You will be asked for your credentials during that process.
Are you using web deploy (right click and choose Publish)?
Have you tried copying the ProjectName.Publish.xml file from the one machine where you can publish to the other two machines? The login credentials for publishing are saved in this file.
In IIS can you check to see that all users/groups are listed under Management Service Delegation in IIS Manager? It is listed under the Server node in IIS. Alternatively you can give all administrators access by clicking on Edit Features from the side-menu and checking Allow Administrators to bypass rules.
You could also check under IIS Manager Permissions for the individual site to see if the person that can publish is listed under there and you are not.
I just recently setup MSDeploy access on my server and found the following two tutorials helpful:
http://william.jerla.me/post/2010/03/20/Configuring-MSDeploy-in-IIS-7.aspx
http://code-inside.de/blog-in/2011/04/03/howto-setup-of-webdeploy-msdeploy/
I have also found that mapping a drive to the UNC location can be a work around.
#soupy1976's solution has also worked for me.
I can not explain why one day it will work and one day it won't
Frustrating....
I am trying to deploy an application using ClickOnce. The problem is, I am saving user generated files in the application's working directory. Now when the user installs the next version of the application, his old files will no longer be available to him. What is the best workaround for this problem - or does this mean I have to roll my own installer!
thanks!
Look into using isolated storage rather than the application's working directory.
This post should help you out.
When Windows Vista came out and developers could no longer store data in Program Files, Microsoft recommended using LocalApplicationData. We store a lot of cached data there, under a folder with our application's name. I wrote a blog entry showing exactly how to do this if you're interested. I call it Where do I put my data to keep it safe from ClickOnce updates?