SharePoint 2013 Mobile Browser Compatibility

If you realize that under SharePoint 2013, when you check your browser.compat there is no browser available for Iphone browser. This could cause an error when you access your SharePoint mobile from your Iphone and you might end up to start receiving complain from your user and of course you're not gonna want that.

In order to make your SharePoint compatible with mobile browser from your IPhone, you just need to do a simple step. And you are in luck, because I am about to show you how to do it. To be honest this is very easy step to make it happen.

1. First of all, go to directory:
   C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\Browsers

As you can see, there are plenty of browser configuration under MS .Net 4.5 folder

2. Second, just open the file iphone.browser with notepad or other tools supported and copy all the       content

3. Go to C:\inetpub\wwwroot\wss\VirtualDirectories\<port number of your app>\App_Browsers\compat.browser

4. Open it with notepad. and paste the script you just copied into this file (paste it before the tag             </browsers>).

And that's it. Now try to access your SharePoint site from your Iphone browser

Access your Ubuntu Server Remotely from Windows

Based on the title given on this blog, it is very possible to remotely access your Ubuntu server from any kind of windows platform using Remote Desktop Connection (RDC). But unlike any other windows operating system, you cannot directly do the remote desktop to access your Ubuntu. In order to make it happen, you need to install few things in your Ubuntu.

Here, I will show you step by step process in order to allow you access your Ubuntu from Windows platform.

• First of all, you need to install xRDP inside your Ubuntu by running these two commands:

=======================================================================

sudo apt-get update

sudo apt-get install xrdp

=======================================================================

• The next step is you need to install something called XFCE4. To do this, run this following command:

=======================================================================

sudo apt-get install xfce4

=======================================================================

Once you finish installing all stuffs shown above, now what to do little adjustment for your RDC connection inside your Ubuntu. Two simple steps to configure your xrdp and xfce4 you just installed. And here we are the steps:

• To make sure that the xrdp you just installed is using Xfce4, we need to run the following command:

=======================================================================

echo xfce4-session >~/ .xsession

=======================================================================

• Make sure that you get this message after you run the command above

• The next step is that we need to make some changes under the file called startwm.sh:

=======================================================================

sudo nano /etc/xrdp/startwm.sh

=======================================================================

• After you press enter, the contents of startwm.sh file will be opened inside the same terminal with the one you open to run the command. Just add this command on the last line and save your chang:

=======================================================================

startxfc4

=======================================================================

• The final configuration is that you just need to restart the xRDP service by running this following comnand:

=======================================================================

sudo service xrdp restart

=======================================================================

Anddd,,... That will be all. Now what you need to do is just test to run your Remote Desktop Connection and connect your windows to your Ubuntu server as usual. You either connect to your Ubuntu by IP address or the computer name. 

I actually found this solution from the Ubuntu forum. You can completely read this forum for the better understanding, because to be honest, I'm still new with the Linux world. I just want to share this information in case you might end up with the same problem I had before

And again thanks for visiting my blog about this Ubuntu stuff. 

Activating user 'root' @ Ubuntu

Hi guyss,

This is my first time I'm blogging away from Microsoft product D:

Now I am going to share a very simple thing attached inside Ubuntu operating system. FYI, the version of Ubuntu that I used for this example is Ubuntu version 16.04.2.

And in this blog I will show how to activate 'root' user in Ubuntu. Root user can act as an ordinary user in Ubuntu, as it can do a lot of things with the privilege this user has. By default, root user is disabled, meaning that in order to activate this user, you must set a password first and then you will be able to activate the root user afterwards. It is similar like when you first time install Windows operating system (such as Windows 10, 8, 8.1, or Windows Server), if you register another username instead of 'administrator', you need to set the password for user administrator if you want to use this particular user. This thing also happens in Ubuntu. By using terminal provided by Ubuntu, you are allowed to activate the 'root' user with simple command. Below are the steps to do it: 

1. You need to set a password for 'root' user by running this command:

   ======================================================================

   sudo passwd root

  ======================================================================

 

2. Just enter the password for your 'root' user then press enter. Make sure you successfully changed         the password

3. Next, run this following command to make sure the 'root' user has been activated

    ======================================================================

    sudo passwd -u root

    ======================================================================

After you ran the last command shown in step 3, you will receive the message "passwd: password expiry information changed". It means that your 'root' user has been activated and you can use this user for your own purpose. 

"Sign in as a Different User" not appeared in My SharePoint Site 2013

One of the coolest feature in SharePoint 2010 is that it provides a menu to directly login with different user account into your SharePoint page. By clicking on the right side on the login username, the small pop up window will appear, and there it is.... Just like the picture shown below:

But once you move on to SharePoint 2013, the menu is by default disappeared

It is somehow making the user difficult the they want to change using another username for signing in to SharePoint page, because they firstly need to sign out and close the browser and re-open to the browser in order to be able to login with another username. That's why I call it as one of the coolest menu in SharePoint 2010 that got left behind in the newer version of SharePoint and your users might be complaining regarding this small feature. But you don't have to worry about that, there is a small simple steps you can follow in order to bring this feature back to life under SharePoint 2013. But before you follow these steps, make sure you can have read/write permission of Program files folder. Once you have that permission, you then can be able to activate the feature for your SharePoint 2013.

Below are the steps to bring the feature back:

1. Login to your SharePoint Server --> go to directory C:\Program Files\Common Files\microsoft       shared\Web Server Extensions\15\TEMPLATE\CONTROLTEMPLATES\

           

2. Open file named welcome.ascs with notepad or other tools supported 

3. Look for tag (most probably starting from line 45) 

                                "<SharePoint:MenuItemTemplate runat="server"    id="ID_SwitchView" MenuGroupId="200" Sequence="200" UseShortId="true"/>"

4. Add this code after the code tag shown in step 3 

<SharePoint:MenuItemTemplate runat="server" ID="ID_LoginAsDifferentUser"
 Text="<%$Resources:wss,personalactions_loginasdifferentuser%>"
 Description="<%$Resources:wss,personalactions_loginasdifferentuserdescription%>"
 MenuGroupId="100"
 Sequence="100"
 UseShortId="true"/>

5. The code should look like this after you do the changes

6. Save and just refresh your SharePoint page and here we go

And those are the steps how to bring back what was hidden under the sea. I don't know why they don't set it as a default feature in SharePoint 2013. It's also not a deprecated feature from the previous version as you can take look at the list of some deprecated feature here. What I can assume is that they do this perhaps for some security reasons. 

I hope this information can help you solving the problem in your SharePoint environment and Thankkk youuu.... 

A potentially dangerous request.path value was detected from the client(%) in SharePoint 2013

If you realize in SharePoint 2010, when you click on username, there is a menu called Sign in as Different User which allows you to use another user to login to the page that you're in directly.

It seems to work pretty well under Microsoft SharePoint 2010 engine. And when you migrate your site from SharePoint 2010 into SharePoint 2013 without performing visual upgrade, your SharePoint site visually will probably look the same, won't it?

But once you finished migrating your site from SharePoint 2010 into SharePoint 2013 and you want to check this feature, has it occurred to you (lets say you're on the list page) that in some particular page when you click this menu "Sign in as Different User", after you login using different username, the page shows you an error page like the screenshot here:

Or in some cases, the error page shows like this: 

I am not really sure if this is a bug from the SharePoint or not, but if you realize that this occurred because of the double encode that happens if your page/list/document contains a space in the name. Based on my situation here, I am in the middle of accessing the list named "My First List" which contains a blank space in between. 

And if you look at the URL displayed inside the browser, the blank spaces between the word in the list name are replaced with %20. So when I open the list called My First List, the URL will show you the name like: My%20First%20List%20. And what if you try to sign in as a different user from the list that contains a blank space inside its name like the one I have here???

The answer will go like the image below here:

Step 1. click the menu

Step 2. Login with another username

Step 3. Here we go...

You might wonder what actually went wrong in this page. If you take a closer look towards the URL, it shows you different URL format with the one before you sign in as a different user.

You can see from the image above, there is double encode occurred when the page tries to re-login with another username. The first encode is %25 while the second one is %20. This the one that causes the error page appeared on your screen browser. When I look for the solution through the internet, some suggested to install SharePoint Cumulative Update September 2014 or higher, but  still did not work out. 

This problem was totally bugging my head for days. I tried a lot of trial suggested from the google starting from re-configure the web.config of the SharePoint web app I created until by adding some feature in IIS manager and config that particular feature, but still no luck and no clue what was happening. Until I finally found one miracle blog that shows how to which I would like to call it as a trick this problem rather than a permanent solution, but I am totally sorry for not sharing the originate blog that I found because I forgot to bookmark the link :(

Long story short, the author of that blog guided me to add one java script inside the closeconnection.aspx file that is placed under C:\Program Files\Common Files\microsoft shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\

The script that you need to add under this file is like the one below:

========================================================================

if (pageUrl.match(/%2520/)) pageUrl = pageUrl.replace(/%2520/g,"%20");

========================================================================

Just place the script after "ageUrl = pageUrl.replace("_layouts/closeConnection.aspx", "_layouts/accessdenied.aspx");" and before "window.location = pageUrl;", 

So the file will look like this after you make the changes:

After adding that java script, just save the file, and try again (you don't need to do IIS reset on command prompt). This should work fine in your SharePoint.

Hope this blog will bright your day a little :D

thanks for visiting my blog

Downloading subtitle from Pluralshight

For those IT engineer

Have you ever heard web named Pluralsight.com?
If you like to watch many tutorial related to IT software application whether or not the software is open source or licensed, pluralsight might be your first video tutorial priority that you go into. The web has a bunch of videos tutorial such as how one wants to be a good programmer or maybe how to configure some particular application such as Windows Server, SharePoint, or other apps that you would like to practice.

The problem when you sign up to Pluralsight is that you need to pay for either monthly or yearly subscription before fully accessing the video you look for. But thankfully to Microsoft visual studio dev-essential you can have 3 months subscription for free by only joining the community with your Microsoft email account such as hotmail or outlook.

But in this blog I am not going to tell you how to do the registration to Microsoft visual studio dev-essential to get free 3 months subscription to pluralsight. At this blog I am going to tell you how to download a subtitle from Pluralsight using Youtube-dl.

• First of all, you go to https://rg3.github.io/youtube-dl/ to downlaod the youtube-dl.exe and just click Windows executable

• Once you already download the file, just open the command prompt and go to the directory where you saved your youtube-dl.exe

• Type this command to download only subtitle from the pluralshight (just change the blue font color with your account and video you're watching):
• youtube-dl.exe --username <Username> --password <password> --all-subs "<URL of the video>" --skip-download

• Just wait for few seconds until the download is done and you're good to watch the pluralsight video offline with the subtitle provided :D 

• Here I show the example how to run it using command prompt

• This will be the output after you finish downloading the subtitle

Many thanks to this forum for giving me this brilliant information about collecting .srt file from pluralsight and thanks a lot to you too guys for visiting my blog :) 

Getting Error When Receiving Incoming Message in BizTalk Server 2013 R2

Getting this error when you open Windows Event Viewer regarding BizTalk solution you just deploy?

And this error message is followed by another error message like this:

When you carefully read the error message, it is saying there is an orchestration that has not been enlisted whether to receive port or send port. And when you check your application you just deployed through BizTalk Administration Console you find that all orchestration has been enlisted into both send port and receive port. 

What is the Root Cause???

One of the most possibility reason is because you have exactly root name or node name in one of your schema in your BizTalk solution.

But when you check on your schema, you did not find any similar schema root name between one and another and that sounds weird doesn't it?

Especially in my case, I only have two schemas and I am totally giving the different for both of my schemas like these pictures below

Apparently I realised that I have another BizTalk solution deployed long before I deployed my recent solution and I found out that I had the schema root name exactly similar with the one I just created. The point is that I have similar schema root name in different BizTalk Solution

If you look the picture below, it has different solution but with the same root name with the previous picture above

What's the Solution then?

As been mentioned in many blogs explaining about this error, what you need to do is just change one of your schema root name and based on the problem I faced, I finally knew that you cannot give the same schema root name in your BizTalk application as long as you deploy into the same BizTalk Server (even though you deploy into different BizTalk Application you create in BizTalk Administration Console) and That will be it. When you re-deploy your solution it should be working as you expected. 

Well, hope this can help you out with the same problem

And happy trying :D