As one of the organisers KbWorks will attend the upcoming SharePoint Saturday Holland on 24th of march with over 300 people attending it is going planed to become a great succes.
This year there are even more business tracks than last year.
Keep you posted on news:
Dear all,
I have updated my blog to wordpress. I have done this because we are going to change the site KbWorks.nl. Further i don’t think i should bother end users with SharePoint technical blogs.
I will refer to KbWorks if it is necessary.
I did however delete some content because it was out dated.
If you need anything let me know.
Hope you enjoy reading my renewed blog.
Last few days i have been pretty busy with a big problem. I made a new Website for myself. And off course started with the starter master page of Randy drisgill
After building the whole masterpage and running(anonymous) it worked. Except for the pages where I used (custom)webparts. When I would hit the page and it did go to CreateChildcontrols
It prompted me for Login Credentials and said I had to authenticate. After clicking cancel the code did not stop anywhere anymore. Which was strange since it had to give a exception or so.
When I turned back on the V4.Master the problem was solved. So it had to be something in the Custom Masterpage.
As a lot of dev’s no you place all Content Placeholders in a asp:panel so they are not visible.
“<asp:Panel visible=”false” runat=”server”>”
I started to take out controls of the panel and found out that at one point it started to work again. Only there where now controls on the page that I did not want to see L
So I did find out if you place them in the asppanel as here above. SharePoint can not Render/see the controls.
So what did I do I did the following
<div id=”kbtitlearea”>
<!– page title –>
<asp:ContentPlaceHolder id=”PlaceHolderPageTitleInTitleArea” runat=”server” />
<!– place a table around this to handle funky markup in _Layouts/areacachesettings.aspx (if you want) –>
<asp:ContentPlaceHolder id=”PlaceHolderPageDescription” runat=”server” />
<!– page content loads from the pages and pages layout –>
<asp:ContentPlaceHolder id=”PlaceHolderMain” runat=”server”/>
</div>
Then I create a class
#kbtitlearea
{
visibility:hidden;
}
After doing that It worked fine and the login problem was solved.
But still wanted to know more about this I found this Link
By somebody who had a different problem with these Placeholders.
So there are more problems with this ASP Panel visible false thing.
Hope this helps you solve your problem when you have a login prompting for authentication. On your Custom masterpage.
Still got a list of interesting links thought i just post them online.
Adding IE9 Site Pinning Support To Your Web Sites
Filter a List based on Current Site’s URL
JQuery for Everyone: Total Calculated Columns
Pretty Dangerous Files – why enabling in-browser viewing of PDFs is risky
Best practices on working with documents and SharePoint.
Multiple Authentication (login) Prompts – Office Products with SharePoint
This last week at a customer of mine we were building a custom solution with Javascript.
As a few of you already know I made a JS Class which you can place in a document library.
At the customer we place the scripts in a toplevel site of SharePoint Library.
So what happened and what is the solution.
We created a few ASPX. Webpart pages with content editors in there. We refrenced the code in de document library.
And it seemed to work all fine for them working as Site Admin.
But the client had different permissions viewer permissions only.
But he did not see anything just a empty content editor.
So I had to came in and help them a hand.
I started debugging as administrator first because they told me they migrated to another farm and parts were still on the old farm.
So I thought maybe it is cross site problem which could give lots of issues.
But as a administrator I could see everything fine.
So I started to look at the permissions of the viewers.
The scripting permission was switched of turned that on.
Still de same problem.
Then I started fiddler to see which page where blocking or what was happening exactly.
I could see that every reference to Document Library ended up in not authorized.
That took me a step further the Script they used refrenced to my class which was in the document library.
When I looked in the document library I saw that versioning was turned on and the classes where not published.
This was a good reason why a Admin would see them and a viewer not.
Published the classes and tried again.
Now Everything is working fine.
Hope this helps you in debugging some things with javascript.
Ricardo Schinning / KbWorks B.V. IJmuiden / 28-4-2011/ www.kbworks.nl
After visiting a lot of Microsoft Sessions it was finally D-Day. We received our login for the Office365 Beta portal.
After a period with a lot of positive BPOS migrations and positive feedback from our clients we were looking forward to see what Office365 could offer us. Thanks to the Microsoft Marketing machine we did receive already a lot of posts, blogs, e-learning sessions etc. so we were ready for the launch.
After receiving our Ofiice365 login we have decided to migrate our old intranet portal immediately to this new platform. It was good to see that the migration went very smooth as Microsoft promised us during their presentations. We haven’t had any big problems or showstoppers during the migration. Of course there were some minor problems but after sending an e-mail to Microsoft we received their feedback within a few hours so i would say Thumbs Up for Microsoft !
So far so good so we were ready for the configuration of our mobile devices such as Smartphones, I-Pads and laptops. In the beginning this was a smooth operation as well. The auto discovery of the mail server + mailboxes went very well and configuring our mobile devices was like a walk in the park. BUT !!! The problems started when we were trying to configure one of our Blackberry Enterprise Phones (BES). Since this phone is used in a lot of business environments it was for us very important to see if it was that easy to configure it as well. Unfortunately we got disappointed about the results since it is not possible to connect Blackberry BES to Office365 yet although Microsoft is more than ready for it. The bottleneck is the developer of Blackberry Software, Research in Motion (RIM). Up until now there is no Office connector for Office365 available and it seems that this connector will only be available at the end of 2011 ! see : http://community.office365.com/en-us/b/microsoft_office_365_blog/archive/2011/03/16/office-365-and-blackberry.aspx
After a disappointment like this we started immediately searching for a solution to fix this problem. The solution we were looking for had to be able to synchronize agenda, tasks and of course e-mail. After a good internet search session we found a very nice piece of software called Astrasync. http://www.astrasync.com/. After we installed this software on our Blackberry Torch it was easy to setup an Internet mail server and to connect to our Office365 platform.
Regarding the configuration of Blackberry BIS you can follow the steps as mentioned below.
This article provides instructions to connect your Blackberry Internet Service (BIS) account with Microsoft Online Services. BIS only provides e-mail synchronization with Exchange Online. . This information was created by the Microsoft Online Services Team.
Your Microsoft Online Services e-mail account should now be successfully added to your list of “Valid Email Accounts” for Blackberry Internet Service. A new mailbox will appear on your Blackberry shortly.
The BIS infrastructure is run by Research In Motion and your wireless provider, and these instructions may change as the service is updated. As mentioned previously, BIS provides e-mail connectivity only.
This week is not what i had in mind. Why?
Monday morning when I arrived at the customer there was big panic a site was not doing the things it was expected to.
It was a critical site and sales would be down. After some investigation I found out that the WorkFlow History list had about
2.4 million items and growing hmm strange it does not work anymore…. The guy who originally build it was not aware of the Workflow history List.
So let this be a wise lesson Your Workflow History List will grow and no it will not truncate automatic if you do not have a policy set up.
You don’t want your documents to be deleted after a time passed by default 
Ok so now to the solution I made a windows app which deleted batches of 2000 as 2000 is gives the best performance you can not delete millions of items by hand…
After doing this it had to be restarted by hand so not optimal but the beginning was made. The It Pro told me wow we need a tool like that.
Then I called my manager at the customer he told fine we will go on on Thursday since the SharePoint Connections was coming up.
So Tuesday I went to the SharePoint Connections in The Hague. But right after Steve Fox gave his Keynote my client called me.
You really have to come we have to need a fully auto tool since nobody can do anything anymore….
The list was 2.5 million now. And It affected the whole sitecollection!!!!
This was the moment I thought I make a console app. And I did.
But be aware that the states of your workflow are kept in The Workflow History.
This means if you delete the list or empty the whole list your workflows will not have a state anymore and need to be restarted by hand.
So in my tool I have parameters You give Url listname items to delete and as optional a date field.
The date field is looking at the last modified and selects all records prior to the date.
If you do not enter a date it will delete all items.
The itemstodelete is build in so you can run the tool and let it delete like 500.000 items in batches.
You can find the tool here http://spemptylargelist.codeplex.com/
Please do download it and start to us it.
By the way it does not empty your recycle bin you have to do that by hand.
Or add it in code.
