When you sign up to new bookmakers online you get a free bet anything from £10 to £100, all this system is doing is using free bets against free bets to gurantee a positive cash return which you can then withdraw to your current account.

Depending on how many online betting accounts you have already will determine how much you can gurantee to make from this but you’re looking between £250 – £700 with zero risk.

A few of us did similar about 10 years ago and made £150 risk free when there wasn’t as many online bookies around, now you’re looking at tripple or even more on that.

I signed up a couple of days ago & now +£40 off the 1st two offers, Ive already got quite a few online betting accounts so wont make as much but will get about £220, free cash.

It costs a small one off fee which will be comfortably made back on the 1st couple of bets. There really is no risk involved if you place the bets correctly, and it doesn’t take much time as everything is emailed to you.

I know a couple of people who around £475 mark after the 1st 3 weeks.

Note:

- This is not my system but worth sharing as most people could do with some extra $$$$

- This is not gambling, its basic maths using the free bets which are on offer to everybody when they open new betting accounts online.

Read more

Run the below script against a database to return all tables where a particular column name exists

use my_db
SELECT t.name AS table_name,
SCHEMA_NAME(schema_id) AS schema_name,
c.name AS column_name
FROM sys.tables AS t
INNER JOIN sys.columns c ON t.OBJECT_ID = c.OBJECT_ID
WHERE c.name LIKE '<columnname>'
ORDER BY schema_name, table_name;

To total a column of values in a Sharepoint DVWP use:

<xsl:value-of select="sum(/dsQueryResponse/Rows/Row/@TotalHoursWorked)" />

To do something similar in Xpath with formatting:

format-number(sum(/dsQueryResponse/Rows/Row/@TotalHoursWorked), '#,##0.00;-#,##0.00')

How to create a back button in Sharepoint to take you back to the previous page either using a text link or image -

Text link:

<a href="#" onClick="history.go(-1)">Back Link Text</a>

Using a back button image:

<a href="#" onClick="history.go(-1)"><img src="linktobackbuttonimage.gif" alt="Back"/></a>

Note: I have only tested this in Internet Explorer

Statistics show that the initial success for new forex traders is disturbingly low. Over time, this trend tends to improve, but for many, it is too late. After posting a series of losses, many new traders will give-up, believing that forex trading is simply not for them. It does not have to be this way.

1.Lack of Experience
Forex trading – like any new initiative – has a learning curve. However, unlike learning a new skill such as learning to play guitar for instance, you are not risking your entire savings while discovering the difference between a major and minor chord. Learning about the currency markets and basic trading principles solely on a trial and error basis is not a recommended approach for gaining the skills necessary to be a successful forex trader.

Most online forex brokers offer a practice version of their trading platform that offers the very same experience as a live trading application. Typically, once you create a practice account, you are free to trade and deal as you wish risking only the “play” money used to seed your account.

With a forex demo account, you can see how the market reacts to economic forces including news events without actually risking your investment capital. However, you must treat this account seriously if you expect to learn from the experience. If you simply shrug off a loss without understanding why the loss occurred, then you are wasting your time and setting yourself up for disappointment. Take advantage of this unique forex market training tool before committing your money to a real forex trading account.

2.Unreasonable Expectations
First off, stop believing all the “get-rich quick” hype still perpetrated by some forex dealers. Yes, there are those that do get rich trading forex but some people also get rich selling houses. In either case, it does not happen overnight and it might take years to gain the experience and insight to turn forex trading into a full-time, successful occupation.

As a new forex trader, if you manage to stay in the game without losing all your money in the first few months as is all-too-common – then you may be able to learn what is required to be profitable. In other words, don’t quit your day job just yet.

3.Absence of a Sound Trading Plan
Next to having unreasonable expectations with regards to the risks associated with forex trading and the amount of time required to be successful, a common mistake made by new traders is the lack of a forex trading plan. In reality, there are two aspects to this plan; an overall objective for your trading activities and a plan for each trade you make.

Your overall objective should include the currencies that you intend to deal in, the amount of leverage you will use, and the amount of time you intend to devote to your trading activities. Your plan must also include a realistic rate of return you expect to achieve. In addition to your overall objectives plan, you also need an exit strategy plan for each trade you make that includes the upper and lower boundaries of the trade.

In other words, you must identify the level at which you will close positions and take your profits (take-profit order) or in the case of a losing trade, the level at which you are prepared to go before you get out of the trade thus limiting your losses (limit order). We’ll talk more about stop-loss and take-profit instructions later.

4.Lack of Discipline
A plan is only of value if you actually have the patience and the discipline to follow it. While this can be difficult, it is necessary if you expect to be successful, and it is this very reason why developing a plan prior to the trade is so fundamental. As rates fluctuate, you can easily get caught up in the market and it is only human nature that you will begin to second-guess your actions. If, for instance, the rate moves up surpassing your original take profit point, you may be tempted to hold out for an even higher return; alternatively, if the price drops below your limit level but you believe there is a big rebound just around the corner, you may be tempted to keep the order open on the hopes of a reversal.

But does either scenario really make sense? If before you entered the trade you had a sound reason for establishing both your take profit and your loss limit levels, how likely is it that conditions have changed so much that now you are prepared to throw your previous assessments out the window in the heat of the battle? Can you be sure that you are not acting on emotion rather than sound analysis?

This is why a plan is so important – it allows you to avoid the emotion that is bound to arise during times of volatility.

Now this is not to say that a trading plan can never be revised – in fact, your overall objectives should be re-examined every few months or even more frequently if required. As well, it may be necessary sometimes to abandon a plan mid-trade if market conditions warrant but this should be the exception and not the norm.

And yes, sometimes the market can be so volatile that no amount of planning will produce positive results. In this case, maybe the best option is simply not to trade until you can get a better handle on things. Never allow yourself to fall into the “I have to do something” trap – sometimes the best plan is to do nothing.

5.Failure to Include Stop-Loss and Take Profit Instructions
When you place a market order and leave it open – that is, enter a trade at the market price without instructions to close the order – you are in effect, gambling with the total value of your account. For this reason, you should consider adding stop-loss instructions to all open positions.

For instance, if you are holding a long GBP/USD position, you can include a stop-loss instruction that automatically sells your long position if the rate falls to a certain level. In this way, you can limit the amount that you could lose on any given trade – even if you are unable to constantly monitor your account.

Take-profit orders are similar in that they allow you to establish the rate at which you want open positions closed in order to lock-in profits. Again, you simply need to identify the rate at which to take the profits, and the trading system closes the position without further intervention on your part.

6.Excessive Leverage
Depending on your experience level, trade leverage can be a powerful tool to help you maximize returns, or it can be the cause of your downfall. It is not something to be taken lightly and if you do not understand how it works, don’t trade until you do understand.

7.Holding Too Many Open Trades
Fighter pilots call it “helmet fire” and it happens when too much is happening around you too quickly for you to react. In the cockpit of a jet fighter, it can get you killed – as a forex trader, you may not end up dead but you will probably end up broke.

8.Holding Losing Positions Too Long
One of the things that really separates seasoned forex traders from those just starting out is their ability to determine when a losing trade is not going to reverse the trend. Rather than “hold and hope”, disciplined traders will take the loss and get out much more quickly.

This is another reason to set protective stops on all your trades; if you include effective stops when you submit a new trade, you can at least limit your losses without having to spend too much time “babysitting” the order. If the trade hits the stop, you will lose the amount committed but you also protect the bulk of your capital, leaving you with funds to move into something else that, hopefully, will be more profitable.

Sometimes, you just have to treat these things as life lessons – learn and move on.

9.Ignoring Rate Spread Fluctuations and the Impact Spreads Have on Profitability
Exchange rate spreads – the difference between the bid and the ask price – are of utmost importance and directly affect the profitability of each trade. You need to be aware that spread differentials can fluctuate wildly during the day – sometimes to the point of turning a profitable trade into a loosing one.

You also need to understand that forex spreads will widen during off-market hours when volumes and liquidity are lower. In addition, spreads tend to widen ahead of important news such as an impending interest rate decision or the latest employment results.

10.Thinking About the “Big Win” More Than Effective Cash Management (AKA Greed)
This one is pretty straight-forward – greed; or more correctly, how greed can cause you to enter into ridiculous trades. This must be the same gene that causes some people to keep “doubling-down” even when the odds are so against them that it make no sense at all. If you want to gamble, go to Vegas.

“Sharepoint 2010 Secure Store: An error occurred during the “Generate Key” process. Please try again or contact your administrator”

Things to check:

– Ensure the logged in user is a member of the farm administrators group

– In my case the ‘Sharepoint Webservices Root’ application pool had stopped on one of my app servers

In the relevant template section in itemstyle.xsl add a line something like (replacing the column name with the your column containing the URL):

LiveView: <a href="{substring-before(@Live_x005F_x0020_View, ',')}">Click here</a>

When creating a a process portal or trying to access certain sections of a process portal in K2 Blackpearl or Blackpoint & you get the following error:

“Parser Error Message: The base type ’SourceCode.SharePoint.ProcessPortal.UI.PortalWebPartPage’ is not allowed for this page. The type is not registered as safe.

Source Error:

Assembly Name=”SourceCode.SharePoint.ProcessPortal, Version=4.0.0.0, Culture=neutral, PublicKeyToken=16a2c5aaaa1b130d

Page Language=”C#” MasterPageFile=”~masterurl/default.master” Inherits=”SourceCode.SharePoint.ProcessPortal.UI.PortalWebPartPage

Register TagPrefix=”SharePoint” Namespace=”Microsoft.SharePoint.WebControls

/k2/default.aspx Line: 3

Version Information: Microsoft .NET Framework Version:2.0.50727.4927; ASP.NET Version:2.0.50727.4927″

Check your web.config & if the below lines dont exist add them & your problem should be fixed:

<SafeControl Assembly="SourceCode.SharePoint.ProcessPortal, Version=4.0.0.0, Culture=neutral, PublicKeyToken=16a2c5aaaa1b130d" Namespace="SourceCode.SharePoint.ProcessPortal.UI" TypeName="*" Safe="True" SafeAgainstScript="True" /> 

<SafeControl Assembly="SourceCode.SharePoint.ProcessPortal, Version=4.0.0.0, Culture=neutral, PublicKeyToken=16a2c5aaaa1b130d" Namespace="SourceCode.SharePoint.ApplicationPages" TypeName="*" Safe="True" SafeAgainstScript="True" />

Edit your masterpage file, In the tag add a link to your custom CSS file just above the content place holder named “PlaceHolderAdditonalPageHead” ie.

<link href="/Style%20Library/mystyle.css" rel="stylesheet" type="text/css" />

When deploying a new smartobject you get the following error in K2 Blackpoint / Blackpearl:

“Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ”

You need to increase the timeout for K2 Smartobjects by doing the following –

1) Open the following file – [InstallDir]K2 blackpearl\Host Server\Bin\SourceCode.SmartObjects.Runtime.config

2) Add a key “commandtimeout” & set the value to 120

3) Save the file and restart the K2 service

Note: If you still get the error, try increasing the timeout ie. 160, 200 etc

Some columns once added to a content type dont allow you to remove them, you dont got a delete button. To delete one such column from your cotent type you can use the following Sharepoint Powershell Script:

#Attach to the web and content type
$web = Get-SPWeb http://fldev003/sites/pjstest/
$ct = $web.ContentTypes["Post"]

#Get link to the columnn from the web
$spFieldLink = New-Object Microsoft.SharePoint.SPFieldLink ($web.Fields["Page Image"])

#Remove the column from the content type and update
$ct.FieldLinks.Delete($spFieldLink.Id)
$ct.Update()

#Dispose of the web object
$web.Dispose()

When in K2 Blackpoint or K2 Blackpearl you are using a Infopath Integration Wizard and when you try to specify the Infopath form template you get the error:

“The solution has not been opened. The following error occurred on opening: Value cannot be null.
Parameter name: adapter”

Delete your submit data connection in your Infopath form, you should then be able to add your Infopath form template to your K2 process with no error.

If you need to find a Sharepoint feature by its GUID because you are getting the error:

Error: The site template requires that the feature *GUID* be activated in the site collection

1) Site Actions -> Site Settings -> Site Collection Features

2) Right click on the features page and select ‘View Source’

3) Now do a search/find for the GUID & you will find the one in question (if its still installed on the farm)

Sharepoint Site collection administrators lose their permissions.

An odd problem where I would login to Sharepoint with my normal Sharepoint Site Collection Administrator account & I would only have basic permissons & various OK buttons were greyed out.

This seems to be caused by having multiple jobs running against your Sharepoint databases at the same time, Sharepoint puts the site collection/database into Read Only mode.

To unlock the Sharepoint site / site collection either use Central Admin:

http://SharepointServer/_admin/sitequota.aspx

or use Stsadm:

stsadm -o -setsitelock -url http://servername/sitename/ -lock None

Sharepoint 2010 Powershell Backup Scripts

Backup a Sharepoint 2010 Farm:

Backup-SPFarm -BackupMethod Full -Directory "Destination directory" -BackupThreads 5

List all items included the Sharepoint 2010 Farm backup:

Backup-SPFarm –ShowTree

Backup a Sharepoint 2010 Site Collection:

Backup-SPSite -Identity "http://MySharepointServer/SC1/" -Path "Path and Filename"

When Microsoft Forefront Security for SharePoint is installed on a SharePoint server, non-SharePoint sites may have problems accessing the Internet Server API (ISAPI) filter that is installed by Forefront Security.

On Internet Information Services (IIS) 7, users who browse to these sites may receive the following error message:

HTTP Error 500.0 – Internal Server Error

Calling LoadLibraryEx on ISAPI filter “D:\Program Files\Microsoft Forefront Protection for SharePoint\FSSPUsernameFilter.dll” failed

On IIS 6, users who browse to non-SharePoint sites may receive the following error message:

Service Unavailable

Internet Information Services 7 (IIS 7)

- In IIS Manager, navigate to a non-SharePoint Web site that is experiencing this issue.
- Select the Web site, and then double-click ISAPI filters.
- In the Filter pane, select FSSP Username Filter.
- In the Actions pane, click Remove.
- In the confirmation dialog box, click Yes.

Test the site to determine whether the issue is resolved. If the issue is not resolved, an IIS restart of the Web site may be necessary. You can do this through the IIS administrator.

Internet Information Services 6 (IIS 6)

To determine whether issue that is described in this article is the same issue that you are experiencing, examine in the Application Event Viewer. If if the ISAPI filter is causing this issue, the following error will be logged:

Type: Error

Event ID: 2214

The HTTP Filter DLL C:\\Program Files\Microsoft Forefront Protection for SharePoint\FSSPUsernameFilter.dll failed to load. The data is the error.

On IIS 6 servers, the ISAPI filter is not exposed at the individual site level. To resolve the issue, add the account that the non-SharePoint site is running as to the ISS_WPG and WSS_WPG security groups. On these servers, look up the account that the non-SharePoint site is running as. You can do this by looking at the credentials on the application pool that the site is running under. After you have the account that the non-SharePoint site is running as, follow these steps to resolve the problem:

- Add the account that the non-SharePoint site is running as to the ISS_WPG and WSS_WPG security groups.

- This makes sure that the Web site has permissions to load the ISAPI filter in the Forefront for SharePoint directory.

- For the changes to take effect, you must run an IISReset. To do this, open a command prompt, and then type IISReset. This shuts down and restarts all IIS services.

Making Sharepoint 2010 available externally using MS UAG 2010 you would think would be fairly straightforward however our experience is at best its very flakey! This is kind of backed up by the fact numerous blog posts & guides from Microsoft & 3rd party’s contradict each other, these are just my notes for how I managed to get it to work.

2 x WFE Windows Server NLB IP: 192.168.1.100

Public Host Name – extranet.abccorp.co.uk

Sharepoint Webapp: docs.abccorp.local
DNS: docs.abccorp.local –> 192.168.1.100

1) Making configuration changes on the UAG published application config – our experience was that if you create a new web application config in the UAG from scratch compared to editting an existing one to the same config you would quite often get different results. So when applying any config changes we always deleted the trunk & the published app config and recreated them from scratch with the required new config, this was the only way we felt we we’re getting the ‘true’ result of the config change.

2) The Application Server addresses & the application url – In order to get the UAG Sharepoint web application to work we had the following config:

HTTPS Trunk:
Public Hostname – extranet.abccorp.co.uk

Sharepoint UAG App:
Web Servers (Addresses tab) – docs.abccorp.local (DNS points the the NLB WFE IP Address)
Public Host Name (Addresses tab) – extranet.abccorp.co.uk
Application URL (Portal Link tab) – http://docs.abccorp.local

Notes on above –
# The address we put in for the web servers & application URL had to be the same, if they weren’t the same it seems the UAG didn’t encode the application URL correctly on the client side.

# We used Windows Server NLB as opposed to using the UAG to do the Load Balancing

Sample CSS to customise the ‘Site Actions’ buttons in Sharepoint 2010

/* Site Actions Menu */
.ms-siteactionsmenu{
border:1px solid transparent;
background-color:#F2F2F4;
}
.ms-siteactionsmenu .ms-menu-a span{
color:#000000;
}
.ms-siteactionsmenu .ms-siteactionsmenuhover {
background-color:#FFFFFF;
color:#ffffff;
}

More From pstilgoe

• Sharepoint 2010: How to hide the quick launch menu
• Sharepoint 2010 CQWP: Make the CQWP portable by using tokens to point to the current site instead of static URL
• How to delete a corrupted Sharepoint list

Ask pstilgoe To Recommend Your Posts

An example XSL template to display document details in a content query webpart:

<xsl:template name="DocumentsDetails" match="Row[@Style='DocumentsDetails']" mode="itemstyle">
       <xsl:variable name="SafeLinkUrl">
            <xsl:call-template name="OuterTemplate.GetSafeLink">
                 <xsl:with-param name="UrlColumnName" select="'LinkUrl'"/>
            </xsl:call-template>
       </xsl:variable>
       <xsl:variable name="DisplayTitle">
            <xsl:call-template name="OuterTemplate.GetTitle">
                <xsl:with-param name="Title" select="''"/>
                <xsl:with-param name="UrlColumnName" select="'LinkUrl'"/>
                <xsl:with-param name="UseFileName" select="1"/>
            </xsl:call-template>
       </xsl:variable>
	   <xsl:variable name="DisplayAuthor">
     <xsl:call-template name="OuterTemplate.GetTitle">
         <xsl:with-param name="Title" select="''"/>
         <xsl:with-param name="UrlColumnName" select="'LinkUrl'"/>
         <xsl:with-param name="UseFileName" select="1"/>
     </xsl:call-template>
</xsl:variable>
         <div class="item link-item">
         <xsl:if test="string-length(@DocumentIconImageUrl) != 0">
             <div class="image-area-left"> 

		<a href="{$SafeLinkUrl}" title="{@LinkToolTip}">
<xsl:if test="$ItemsHaveStreams = 'True'">
                   <xsl:attribute name="onclick">
                     <xsl:value-of select="@OnClickForWebRendering"/>
                   </xsl:attribute>
                 </xsl:if>
                 <xsl:if test="$ItemsHaveStreams != 'True' and @OpenInNewWindow = 'True'">
                   <xsl:attribute name="onclick">
                     <xsl:value-of disable-output-escaping="yes" select="$OnClickTargetAttribute"/>
                   </xsl:attribute>
                 </xsl:if> 

                 <img class="image" src="{@DocumentIconImageUrl}" title="" />
				 </a>
             </div>
         </xsl:if>
         <div class="link-item">
         <div style="color: black; font-family: Arial, Helvetica, sans-serif; line-height: -2%">
             <xsl:call-template name="OuterTemplate.CallPresenceStatusIconTemplate"/>
             <a href="{$SafeLinkUrl}" title="{@LinkToolTip}">
                 <xsl:if test="$ItemsHaveStreams = 'True'">
                   <xsl:attribute name="onclick">
                     <xsl:value-of select="@OnClickForWebRendering"/>
                   </xsl:attribute>
                 </xsl:if>
                 <xsl:if test="$ItemsHaveStreams != 'True' and @OpenInNewWindow = 'True'">
                   <xsl:attribute name="onclick">
                     <xsl:value-of disable-output-escaping="yes" select="$OnClickTargetAttribute"/>
                   </xsl:attribute>
                 </xsl:if>
                 <xsl:value-of select="$DisplayTitle"/> 

               </a>   |   <xsl:value-of select="@Author" />   |   <xsl:value-of disable-output-escaping="no" select="ddwrt:FormatDate(string(@Description), 2057, 5)" />
 	</div>
           </div>
       </div>
  </xsl:template>

A returned file in the CQWP will display:

Plan 36 | xxxxxx\StilgoeP | 01/06/2011 09:35

Doc Icon (links to doc) – Doc Title (links to doc) – Author – Modified Date & Time

More From pstilgoe

• Sharepoint 2010: How to hide the quick launch menu
• Sharepoint 2010 CQWP: Make the CQWP portable by using tokens to point to the current site instead of static URL
• Modifying an Open XML Document in a SharePoint Document Library

Ask pstilgoe To Recommend Your Posts

STSADM -o backup -directory: Error Cannot open backup device Operating system error 5 (error not found)

Ensure the SQL service account is a domain account and it has permissions to
the Shared folder.

Also ensure the account used to execute the backup command has the correct rights on the DB’s as per MS recommendations ie. Owner, creator etc.

More From pstilgoe

• Error: Cannot retrieve the information for application credential key
• Sharepoint list error <!– #RENDER FAILED –>
• Error (Exception from HRESULT: 0×80004004 (E_ABORT))

Ask pstilgoe To Recommend Your Posts