We have been going through the cycle of submission, refinement, submission. Normally we get a very detailed report with the findings. However, our most recent response from the team was a generic:
We’re sorry, but we encountered an error while processing your app and
need your help to continue. Please submit your app for approval again,
and we will continue the validation process.
How can we get feedback on what this means, what was the root cause, and what we can do to ensure this doesn't happen. Our team wasn't notified of this issue, and only noticed it by checking the status several times a day.
When issues like this arise, is there a way to triage the issue faster or at least set it up so that we receive notifications proactively rather than passively?
Microsoft is in the process of modernizing a lot of the infrastructure that processes add-in submissions (to fix the issues such as the one that affected your add-in submission) - when we complete this work in forthcoming months, you should not encounter these issues any more. It was not caused by something you did wrong during submission time.
Until our updated services are released, I'd encourage you to check the email you used when registering with AppSource/the Office Store. Checking the Seller Dashboard site will also show you the status information.
If you have further questions, please provide the name of your add-in submission and we can contact you directly.
Thanks,
David Mowatt
Office Store Program Management
Related
I have a couple of months using Google Chrome Web Developer dashboard. Everything was very normal, publishing an updated version was taking around 30-40 mins, now that I added a few elements to my extension such as popmotion.js it keeps requiring manual revisions and my extension gets into "Pending for Review" state for so long.
My question is: Is this caused by something I could have done in the code? Is it possible to get rid of this condition that keeps telling Google's services that my extension needs to be manually reviewed?
Thanks in advance!
According to this link, Pending review means the Chrome Web Store automated systems have flagged your item for manual review.
Some of the reasons an item could be flagged for manual review include:
The item may have an NPAPI plugin, which requires a signed agreement from you. Check your email account associated with the item for an agreement notification from our abuse team.
The item is suspected to contain or to be distributed by malware or unwanted software.
The item is suspected to violate one of the developer program policies.
The item may have already been previously removed for a legal or policy violation, and has been resubmitted.
The item requests powerful permissions that require in-depth review.
Let me start off by saying that I am not a SharePoint guru, nor an administrator for this site. I have enough rights to build my site. I have taken on the task of creating a site at work to make things better since it has gone through several people's hands and I take it as a challenge that I can do it.
So I have a workflow I created in SPD 2010 to send an email out based on an kickoff action in List A that references email addresses in List B since I am sending this email to people outside the organization. I have even tried to make a simple workflow to send an email to my name in the To: field and TEST in the Subject and Body. No Luck.
The issue lies in the fact that when I try to publish the workflow to the site, after checking for any errors (none I might add), I get back a "Workflow Error" that says "Errors were found when compiling the workflow. The workflow files were saved but cannot be run" and if I hit the Advanced button it says "Unexpected error on server associating the workflow."
I am looking to this forum to determine if this error is related in some way to an incorrect setting in the SharePoint Server that I don't know about, if it has anything to do with a lack of permissions from the overall SharePoint Server administrator to upload workflows or something else that I know nothing about.
I have asked the SharePoint administrator and he won't be able to get back to me until next week as he is at a conference, but I would like to try the workflow out and see if it works or I need to go back and work on it more.
If the consensus is I need more rights and I will have to wait until next week, is there a way to run the workflow in SPD or can I download my site as a sandbox and just play with it there?
Any and all help is gratefully appreciated.
For others who have this issue, it was a rights issue. The company did not install SPD as an admin, hence I could not create work flows.
I have a request of a customer who wants his dashboards to be send weekly/daily to him via E-mail (PDF or IMAGE). I have searched for hours to find a decent solution, but I can’t seem to find one. This should work on “CRM Online” and on “IFD”.
I have found some code that can take a snapshot of a Webpage, but there I have the “Log-In” problems. Each time you execute the page, you see a page with the “MICROSOFT PASSPORT” or “ADFS” sign in box. I tried the “wkhtmltopdf”-method and “WebBrowser”-method and 3rd party tools.
There is also no “JavaScript” or “JQuery” that is able to generate screenshots from the current page. I’ve created a Webresource in CRM 2011 with an iFrame and in that iFrame I’m able to show the “Dashboard”. If I would be able to take a snapshot of that page, I could create an attachment and put in the CRM.
I think I’m on the right way of doing this, but I can’t seem to get over the last difficulties. I hope someone here on the forum already has done something like that. I’m almost sure it must be possible, because a partner of us was able to take a screenshot of the Dashboard and put it in their application. Of course they don’t want to share that piece of code with me.
I don't believe there is a way to possibly implement the functionality requested with out some major "hacks" that would be brittle and most likely break with any type of CRM/Browser update. I would work with the customer and advise them that what they are asking really doesn't make sense from a cost / maintenance standpoint. I'd try to see if they'd be willing to live with these work arounds:
Send a weekly e-mail with a link to CRM. Downside is the user has to be able to have rights to login and see the data, but it would be super easy.
Create custom reports that recreate the dashboard data. You should be able to schedule e-mails for this through SSRS
Good luck!
I am very new to Sharepoint world, and learning online and from some books to get as much as possible.
I am making this demo to understand workflow better, but can't progress much.
My situation is, lets say I request to buy some product, my manager sees it and can reject or approves it. If he approves, my request should go to finance team, and they can proceed it onwards, from finance team to logistics team and I get my product.
Till now, using Approval Workflow, I am able to send request from me till my manager, but I don't how can he now forward it to Finance team ? Do I need to design another workflow for this ? Or should I program Workflow for this purpose ?
I also have got an option to see what is the status of the request ? When I first start this request, it is Open. When manager approves it is Approved. Now when he change Open to Approved, I want to trigger workflow from Manager to Finance, how can this be done ?
A little tip that can help me get going with this Workflow would be very useful.
Or if you have some suggestions for nice workflow tutorial for beginners, that would be very helpful too.
Thanks.
Do I need to design another workflow for this
Sorry, but yes, absolutely.
You can try first with SharePoint Designer. From your description it sounds feasible.
If not, you will end up coding it with visual Studio. In this case, good luck, it can be a bit difficult to construct your first workflow.
You can definitely construct such a workflow using SharePoint Designer 2007, which is a free download from Microsoft's web site. In particular, you can pause the workflow until the approving manager approves or disapproves the request. Then depending on the manager's response, you can have the workflow "send" your request on to the next department.
We have a long standing issue in our bug tracking system about the dreaded "ERROR: request not found in the TrackedRequests. We might be creating and closing webs on different threads." message in SharePoint's trace log.
As we develop Workflow software for the SharePoint market, we look into this issue from time to time to make sure it is not caused by our products. I have personally come to the conclusion that this is a problem in SharePoint, but perhaps someone else can prove me wrong.
Here is what I know:
According to the hundreds of search results returned by Google on this topic, this issue appears to be mainly related to SharePoint Workflows, both SharePoint Designer and Visual Studio based workflows.
Assuming ULS logging is set to Monitorable, the easiest way to reproduce this problem is to create a new SharePoint Designer Workflow, attach it to a document library, set it to auto start on add/update, don't add any actions, save the workflow and upload a file to the document library.
The error is only visible in the SharePoint trace log, it does not appear to impact the execution of the workflow at hand.
I have verified that the problem occurs on 32 bit as well as 64 bit systems, Win2K3 and 2K8, WSS and MOSS with SharePoint versions up to the December 2009 Cumulative Update (6524).
The problem does not occur when a workflow is started manually.
There are dozens of related posts on MSDN Forums, hundreds on Google, one on StackOverflow and none on SharePoint Overflow. There appears to be no answer.
Does anyone have any idea about what is going on, what is causing this and if we should worry or file this under 'Red Herrings'.
Update: Microsoft has confirmed this is a known issue that can be safely ignored. It will not be fixed in SP2007, but is no longer a problem in SP2010.
File it under Red Herrings. You say "The error is only visible in the SharePoint trace log, it does not appear to impact the execution of the workflow at hand." There are so many errors logged in the ULS Log that are beyond our control and do not immediately impact our environment. If you want to improve the product you could attempt a support call that may be non-incremented as a bug. However, what if it's not a bug, but just a verbose ULS Log message?
In fact, this verbosity isn't limited to just the ULS Logs. Have you seen the Microsoft Office SharePoint Server 2007 Management Pack for System Center Operations Manager 2007? It filters out the noise events from the Event Logs on your farm so you can concentrate on the events that flag an actual problem.
This is a really good question and I'm starving to see good responses to this. I've seen this error in my workflows in very different contexts.
For instance, In my case it happens in a home-baked custom activity when I catch the "task created" event and try to "breakroleinheritance" of the SPListItem (the new task).
My custom activity gets workflow context through a property wfActProps which is of type SPWorkflowActivationProperties. Then I typically use wfActProps.Web to access the web object.
The first thought I had that maybe it's a bad tone to pass SPWorkflowActivationProperties between different activities, however I have not found any different way yet.
I'm setting "community wiki" to my answer since this is not an actual answer, rather an example of a situation where this error can be seen.
When I look at the stacktrace (I'm assuming the person who posted that message is referring to the same error), it looks like an OOTB event receiver (Microsoft.SharePoint.Workflow.SPWorkflowAutostartEventReceiver) which is responsible for autostarting workflows is disposing an SPSite that may not have been created by the event receiver code.
Unfortunately the AutoStartWorkflow() method is obfuscated so I can't really see in Reflector which SPSite is being disposed. You could experiment writing your own EventReceiver that disposes any existing SPSite it can get it's hands on and see if that causes the same error to be logged.