Every morning at 2:00am (or when ever all the pivots finish building) I run a vb.net program to upload all the pivots to a specified shared documents folder inside of SharePoint. Sunday through Friday the script runs perfectly but on Saturday morning it fails to connect via webdav.
"The specified network name is no longer available"
This is strange because we even put a 30 second delay in there if it receives such an error to give the site time to wake up if that is the case. There is nothing strange showing up in the event viewer on the Pivot Server or on the SharePoint server.
I have a few other programs/scripts running during the day that work flawlessly every single day.
PowerShell script to upload all users from Active Directory into 410 various groups
PowerShell script to set the permissions of the Pivot folders so only the right people see their pivots (This runs at 3:00am and works fine)
And a few others
I can't seem to track down this one.
there are some powershell "sharepoint warmup" scripts to be found on the interwebs, that basically loop through all site collections and makes a request, firing up all web apps, maybe you could give that a try, have it run say every day at 6 in the morning?
Related
Recently I have started working with Excel Online within the organization I´m working. Currently as a team we are using the online feature of Excel and work together simultaneously in the same sheet. In order to avoid many, daily, actions, I created so-called Flows to either group or ungroup certain data and have less (= group data) or more (= ungroup data). When I discovered the option to automate certain flows (via Power-Automate) I tried making an automated Flow that basically executes on a daily bases one of the Flows (group data) in order to start the day with an organized and neat workfile.
I created the following Flow;
Recurrence:
Interval: 1
Frequency: Day
Run script:
Location: OneDrive for Business
Document Library: OneDrive
File: File location
Script: Script name
Connection in use: Excel Online (Business)
Owner: Myself (both of file and flow)
What I have tried is the following:
When I am just executing the flow manually within Excel Online, it works good. Without
problems. It takes like 20 seconds and never had any issues.
I have played with the settings of the flow to see if it has any impact
(interval, frequency, other location, etc), without succes. After
like 20 minutes of runtime it returns a "Failed error" and the script
does not get executed (Error = BadGateway).
Additionally, I read somewhere online someone who had the same problem and it got solved by
indicating a Timeout limit (tried PT30S,
makes no difference other than the Failed error pops-up sooner).
I checked the subscriptions linked to my account and, amoung others, supposedly I have the
following; "Power Apps for Office 365" & "Power Automate for Office 365" licenses. Reviewing the
"Power Platform Licensing Guide - June 2022 (2)" I am assuming I do have the correct licenses
in order to be able to execute these kind of flows (see below).
However, I cannot seem to make it work. Is there anyone out there experienced with the Power Automate (online) functions within the Office 365 online environment who can identify what problem I am dealing with here and how to solve it?
We have a Dev server in which we then move the solution across to Live to apply any updates that we have done.
We created workflow that sends an email on a trigger of a field change about a year ago. Since then we have made various changes to they way the email works and have been through several solution moves to live.
The last one we did however is now firing two workflows on the trigger, one being the most recent workflow we have updated and the other is the same workflow but about 10 versions back.
I have restarted the Async Processing Service, rebooted the server a couple of times and deactivated then reactivated the workflow.
We are currently using Dynamics 2013 On-Prem.
Any Ideas?
I have created a SSRS report in SharePoint and its uploaded in to the SharePoint library. While running, its working fine. It taking less than 10 seconds to load the report. But If I kept the report in idle mode for the next 5 minutes, then I tried to enter the text in search box in report tool and then clicked find. But instead of displaying the result, it loads the report again. And If I pass the search criteria, it will works. So My assumption is that, it would be the problem of time out. So can you guys advise me where can I update the time out value to avoid this issue?
If this is SSRS SharePoint integrated mode I guess something should be available in Central Admin to which usually developers might not be having acces atleast in prod environment. Check with the administrators who manage your farm.
I'm in the process of writing code to pull my own Outlook calendar, as well as some shared calendars into an MS Excel spreadsheet. However, I'm finding that my script is running very slowly. I've found that it takes about 1-2 minutes to load a months worth of events from my own calendar and about 10-20 minutes to load events from the same time period from a shared calendar.
I've noticed that my script can load my personal calendar both when I'm on and offline. However, I will get a run-time error at the when I call ".GetSharedDefaultFolder" if I am not connected to the internet. In addition, if I disconnect my internet while looping through items in a shared calendar, I will also get a run-time error. My best guess at the moment is that the majority of my speed issues are due to the fact that Outlook is checking the exchange server for each item, one at a time (I'm pretty sure this is happening).
Does anybody have a good idea of how to solve this problem? I'd like to speed up my code so it doesn't take ~45 minutes to run my script. I have a hard time believing that Outlook does not store the most recent version of a shared calendar on my laptop. I also don't see why I shouldn't be able to call some function to download the entire calendar and then loop through the items without needing to separately request each item from the server.
Thanks!
I actually managed to fix the problem by enabling the "Download shared folders" property in MS Outlook. This reduced program execution time from 45 minutes down to 7 minutes.
Directions on how to enable the "Download shared folders" property:
http://www.msoutlook.info/question/414
Note: To find the Account Settings button in Outlook 2013, you have to navigate to the "File" menu.
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.