Mark Rhodes

Pingback from  stsadm runs slowy « Point Deep

I am using the following query myself to look for pending approvals:

SELECT

AllUserData.tp_DirName,

'http://SiteName/' + AllUserData.tp_DirName,

AllUserData.tp_LeafName,

case

when AllUserData.tp_ContentType = 'Item' then

'http://SiteName/' + AllUserData.tp_DirName + '/DispForm.aspx?ID=' + AllUserData.tp_LeafName

else

'http://SiteName/' + AllUserData.tp_DirName + '/' + AllUserData.tp_LeafName

end as Link,

AllUserData.tp_ContentType,

AllUserData.nvarchar1,

AllUserData.nvarchar2,

AllUserData.tp_ModerationStatus,

AllUserData.tp_DeleteTransactionId,

AllUserData.tp_IsCurrent

FROM

WSS_Content_2d87952795724429861dc3a8b7a4b24c.dbo.AllUserData AllUserData

WHERE

(AllUserData.tp_ModerationStatus=2)

AND (AllUserData.tp_DeleteTransactionId=0x0)

AND (AllUserData.tp_IsCurrent=1)

ORDER

BY AllUserData.tp_DirName,

AllUserData.tp_LeafName">

I have this on a hidden page on my site.  This gives me the URL to the list and the item requiring Approvals

Audit Log Reporting seems to be one of those topics within SharePoint that is still a little misunderstood

A long while ago I put together an article after having a hell of a time getting Project 2007 and SQL

check out this for a solution to the problem :)

blogs.iis.net/.../workaround-running-asp-net-1-1-on-vista-sp2-ws08-sp2.aspx

Hey Mark:

Big Fan....and thank you for the great post! You saved me a couple hours of research and potentially a head-ache. I ran into a similar issue as you described above the other day.  The only difference I determined was that the environment in which I was seeing this happen in was slightly different.  Their are no Roll-Up's applied, and only two of the four lines of code were missing. I added the two lines to the Web.Config, IISRESET, and we were back to Publishing Workflows!

Thanks!

- Mark Walczak

Pingback from  SharePoint file size limit | rapid-DEV.net

Pingback from  Maximum upload limit on SharePoint Size? | SharePoint Perth

Thanks Mark on this post.

The word ExecutionTimeOut should be typed  as "executionTimeout":

 <location path="upload.aspx">

   <system.web>

     <httpRuntime maxRequestLength="2097151" executionTimeout="999999"/>

   </system.web>

 </location>

Pingback from  Work, You Stupid Thing &raquo; MS CRM 4.0 Unable to Publish Workflows

I've been struggling with this very issue last weekend. I finally pulled it of, but I had to roam throug numerous google search results, MS KB articles, and more.

I've gathered all the info I found in a (long) blog entry: therealboerke.spaces.live.com/.../cns!EE6469678100A3EE!167.entry

Thank you Mark.  Great post! Saved me a few hours today.  

Thank you!  Saved me a couple hours as well.

For pages pending approval, I just use a Content Query Web Part and set the parameters to look for all sites within my site collection for document types within document libraries where the Approval column = "Pending", also on a hidden page on my site.

Welldone!  I was having such issues with this one after resoring a site collection from an SSO Authentication provider to an NTLM.

Welldone you really helped me out alot!

I have a theory on this, and let me start by saying that this is a mostly uneducated guess based upon semi-related information I have learned from others:

Today I experienced the same issue, and the only missing line was the System.Globalization line.  While this was similar to what you reported, I have not installed any updates recently.  That being said, making the changes fixed it.  An IISReset alone would not.  This got me thinking back to what a coworker once suggested about IISReset, how clearing out the temporary files wouldn't always happen, but making even the smallest change to web.config would.  Is this really an issue of those references being missing, or is this just purging out some bad data from temporary files / cache?

Again, I know barely anything about IIS, just something I thought of based upon second-hand information.

Great! you're right, I got the same problem and your solution resolve the problem.

Thanks!

Recompiling, that was it.  That's what was necessary for my workflow to publish.  I'm not entirely sure what happened to cause it to fail in the first place, however the recompiling worked.

What I would still need to try is removing the line from web.config that I had added, running IIS Reset again, and testing to see if I could still publish workflows.  If that's the case, then I guess something just compiled incorrectly at one point and needed to be recompiled.

Thanks for the article Mark. It saved us a lot of time. We are at UR2 and moving to UR8 this week. The problem showed up as soon as we put UR8 on our test system. We were only missing the last line (CultureInfo) but that was enough to trigger the problem for us in moving past UR2. Adding the missing line and iisreset fixed it immediately. Thanks again for blogging about it.

Thanks for the article!  Had the same issues, even moved up to Rollup 9 and I still had to add the "CultureInfo" to web.config to fix the problem. Could this only be an issue if you have multiple MUI installed? Thanks for blogging about this, saved me hours of work!