We are seeing an odd behavior where we update a manifest in production (basically remove the old one, add the new one) through EAC, however it takes more than an hour to take effect. My understanding is that the admin-defined manifests are stored in a particular System Mailbox, so I am confused why there should be a lengthy delay. Is there way to troubleshoot this, and (2 for 1) is there a general way to troubleshoot an Outlook App not showing up in, say, Outlook 2013.
This is the expected behavior, it can take upto 4 hours to get the latest manifest if deployed via EAC. Please have a look at comment made in this post via Sreeram https://techcommunity.microsoft.com/t5/Outlook-Blog/Centralized-Deployment-for-Outlook-add-ins-will-now-be-generally/ba-p/161164
Related
We created an application with SCIM support over two year ago now and it always worked fine. However recently we have been getting reports from customers that users were no longer deleted/disabled from the target enterprise application.
I already saw there was another question like this one a few years back but that seems resolved and this seems like another issue.
We did a little research on our own and noticed that azure is not sending any requests at all when we remove a user from the assigned user list. We checked the incoming logs from our application and IIS logging and both do not show any requests are sent our way. (we do get logs from POST/GET/PUT of other provisioning related tasks, like creating a user).
In azure audit logs we do see the following:
Remove app role assignment from user
Add a deletion-marked app role assignment grant to user as part of link removal
Which seems to me that azure is doing something, it's just not sending it to the targeted application
Current situation:
We have user A that was created in azure ad and is assigned to our application. Provisioning configuration was done by means of SCIM in azure. And the user is also created in our application, so the connection seems fine.
When I remove the user from the assigned user list in our enterprise application, I expected that counts as a softdelete, causing Azure to sent a PATCH or a PUT to set the active property of the user to false. In case I would delete them entirely from AD I expected them to be removed with the DELETE. I read that it takes up to 30 days which is no problem, but the problem is that user that are no longer assigned are still active in the target application, which is no good.
I have some basic properties mapped on the user and the one thing that might be involved with this issue would be the Not([IsSoftDeleted]) mapping which is mapped to our active property. I don't see how that is wrong, but that's all I can think of at this point.
Anyone that can has any idea what is going here?
Thanks!
I have had contact with Microsoft regarding this issue and it seems to be a bug on their end which they are currently correcting. It is part of a larger set of bugfixes all regarding similar issues so they could not give me a specific time when this specific issue was resolved, but they think around the 10th of July (2020).
In any case, as this was a bug due to changes pushed by MS this is no longer an issue to be solved.
Update:
I have received some replies that a few bugs were fixed connected to this issue but not all. I'm currently on vacation so i'm not sure if the main issue is fixed as well. They did promise a fix fast though.
For now all I can give you is a workaround. The issue happens when the only change that is happening is the unassignment of users, it simple won't execute this until at least 1 property from an assigned user is also changed. When anything is changed, it will fix all unassignments and disable them all, even if the unassignment was in a different sync cycle. So until the actual fix is pushed, that might be helpful to know.
I will keep this thread updated if I get more information.
Ps: The Azure team requested that if anyone else also ran into this issue they report it through Azure. Their dev team will see if your problem matches up with my issue or if it's something new. So please do that as well.
I'm fairly new to SharePoint but I'm learning fast. However, I've encountered a confounding issue that has me completely stumped, and the internet hasn't been able to provide anything useful as of yet...
I'm running SharePoint 2010 in a VM, and I am getting a repeated issue with libraries spontaneously disappearing from the GAC. This is happening on average about once a day at the moment, but at different times of day and with no apparent trigger. The VM I am running (and the source code thereon) are identical to my colleagues', yet I am the only one to have encountered this issue. I have rebuilt my environment several times and thought I'd cracked it with this latest one, but the issue has just reoccurred. Since it happens at different times of day I don't think it can be a timer job, and it can happen spontaneously with no user input (no changes to code, settings, environment, anything).
I can provide more details of the libraries affected if required, although it seems to be a mixture of proprietary libraries specific to the project, and standard Microsoft assemblies.
Any help or pointers would be gratefully received!
Had the same issue. I fixed it by recompiling one the conflicting dll files with a different version number and some different number. Then i made sure that every webpart that uses this dll had this dll in their individual sharepoint package, then i deployed the webparts again and this time they didnt disappear.
I also found out that disappearing was not random and was the result after another webpart was being installed. Pretty weird.
I'm experiencing problems when trying to deactivate a custom feature through the GUI. When I press the 'deactivate' button I'm, as expected, redirected to the warning page which asks if I'm sure I want to deactivate.
Upon confirming, the page starts loading.
The feature in question should normally be activated very fast, however on this occasion the page loads for more than 5 minutes without anything happening.
After concluding that the page seems to be stuck in an eternal loading cycle, I had to refresh the page to see if there had been any changes, but no, the feature remains active.
Any ideas?
Details:
The site I'm working is a previously existing office365 site. I've just made some changes to my custom solution (modifying one feature and adding another)deactivated the old solution and uploaded the new solution, so I'm trying to deactivate and reactivate the feature which I've modified.
It depends what's happening during deactivation - 5 minutes might not be very long if the deactivation has to perform a lot of updates (e.g. removing columns from lists in lots of subsites). I did once have a feature deactivation that took 45 minutes (?) to run.
I guess another possibility is that you've got C# code that contains an infinite loop? Though that seems a bit of a long shot.
Otherwise, Office 365 is very hard to debug; I'd suggest raising a support call with Microsoft through the O365 portal to see if they can see any logs.
When the feature is removed are you trying to remove items like CT's or anything that is dependant on another thing?
I've seen features get glitchy when this occurs on our test enviroment and make sure this is ironed out before deploying to live.
Theres a feature checker somewhere on codeplex but i'm not sure if this will connect to the office365 site. It's called something like FeatureAdmin.exe This might help you in removing the feature and clearing out left over stuff from the feature however it will not remove whatever your feature is struggling to remove(if it is of course!)
When the original feature was deployed did you test it could be deactivated cleanly?
I have a customer using the Access 97 runtime to support part of their product. Ideally, given the budget to do so, I would have replaced that dinosaur by this point, but that isn't an option today. I am not the system's original author, but am attempting to provide ongoing support.
To distribute this to their customers, they bought the Office 97 Developer Edition Tools, and once every few years they go through its Setup Wizard to package a new distribution.
This time, the Setup Wizard appears to reach a point where it wants to do something with AXDIST.EXE, and instead puts up a dialog box saying only "Path not found". The only reference I've located on the web is a tantalizing glimpse of a page from a domain that no longer exists, where Google has purged the cache retaining only the sentence that appears with the search result. It isn't enough of a hint to help me...
(Edit: Aside from lots of reported issues caused by AXDIST.EXE itself, or installations that are trying to use AXDIST.EXE in some way, that is. Our issue is a problem during the creation of a setup package using the ODE setup wizard. Its own documentation only references AXDIST in one place, and does not contain the text "path not found" at all.)
(Edit 2: Further investigation reveals that AXDIST.EXE itself is not the culprit. Removing that file from the setup wizard's list caused the wizard to stop on the next file in the list. There does not appear to be any significant differences between the description of the file on which it stopped, and the dozen or so files listed above it that were successfully processed. I'm guessing at this point that the resolution is going to be manually recreating the template from scratch, which would be a lot easier if it weren't trapped inside a horrible UI and stored in the form of an Access database containing a bunch of undocumented tables.)
My question is this: What mistake did we make this time with the setup wizard, and how can we fix it?
The issue turned out to be related to a feature of the Access run time that was explicitly listed in the setup wizard, but should have been left for the wizard to infer.
My general advice to anyone also stuck with dealing with the wizard would be to go back to the start and review all the settings carefully and methodically.
We are using an infopath form that when submitted is supposed to fire off a custom .NET workflow. Basically, the information within the form is used to create a new sharepoint site. What I am seeing happen is that the first time the workflow runs (which is automatic after the form is submitted), the workflow errors out. When I run the workflow manually immediately after it fails, the workflow runs fine.
this.workflowProperties.Item["Client Name"]
I've debugged the issue down to the above line where workflowProperties is of type Microsoft.SharePoint.Workflow.SPWorkflowActivationProperties. The first time the workflow runs, the property listed above (and all others) are null. The second time it is run the client name property is as it should be (populated from the infopath form).
Another important piece of information is that this workflow was working fine for over a year and suddenly started not working correctly a few weeks ago for no particular reason. We were having some permissions issues the past month but I cannot see how that could be related to the workflow issue. The user I am logged in as is a site collection administrator. I use the same user to kick the workflow off manually (which succeeds). I do not think that the workflow runs as the user that is logged in though (when it is run automatically on form submission).
Another interesting wrinkle to the whole situation: there are a total of 3 custom workflows that the application uses. 2 were made in visual studio - one of these works fine and other is displaying the behavior described above. The last was made in sharepoint designer and is failing.
I'm willing to try just about anything at this point. I am on a dev server (which displays the exact symptoms as production) so I can try just about anything.
I'm guessing this has to do with the workflow being fired asynchronously from the commit operation that sets the fields values. Can you try and fetch the item explictly from the list instead of using the Item from the workflow properties. something like the following:
SPListItem l_item =
workflowProperties.Item.List.Items.GetItemById(
workflowProperties.Item.Id
);
i'm not certain, but it may be worth a try.
The other thing to keep in mind is the SPContext.Current object will be null if being called from an EventReceiver, but will be valid if called manually. It doesn't sound like this is the issue, but its something to be aware of nonetheless.
If the InfoPath forms are submitted from a Vista or Win 7 machine, you might face this issue of getting a NULL value for the fields in the InfoPath form. Try adding a delay activity with around 10seconds and see if your are able to get the value of the fields from InfoPath.
Refer to this link for more details: Why does my SharePoint workflow fail when the client is running Vista or Windows 7?
Try looking in your SharePoint Logs.
They are located under the 12-Hive in the LOGS folder - open up the latest and look for something with 'Workflow infrastructure' in it, maybe that can point you in the right direction.
The "solution" was to do an export and transfer to a new server. Basically just use STSADM to do the export operation and then import the same file on the new server.
SEE:
http://sharepointdogs.wordpress.com/2008/07/30/content-migration-or-backuprestore-in-moss-2007/
I was on the phone with Microsoft Support for hours on this issue - transferring to a new server would be my recommendation for anyone else that might encounter this problem.