Anything And Everything by Keith McGuinness

Enable Windows Authentication on ASPX page allowing all users without login

Celtic_Guy — Tue, 13 Nov 2012 18:07:39 GMT

Simple config which is obvious when you remember and dont forge :-) This allows all users access your website but also allows you to check via your code or other custom authentication their right to access it.

<authenticationmode="Windows">

</authentication>

<allowusers="*" />

<denyusers="?" />

</authorization>

<anonymousIdentificationenabled="false" />

You will get the username etc and will be able to take actions you desire.

Hopefully might come in handy for someone who forgets!

Azure: Windows 7 VM, Hyper-V enabled Azure VMs

Celtic_Guy — Tue, 08 May 2012 14:15:00 GMT

If you are trying or wondering if Windows Azure supports Windows 7, Windows 8 or other OS via a Hyper-V on a 2008 VM image uplodaed to Azure you will realise you cant do this.

The operating system that is installed can be one of the following:

Windows Server 2008 R2 Enterprise (English only)
Windows Server 2008 R2 Standard (English only)

Hyper-V cannot currently be enabled on the VM images to allow you to install operating systems like Windows 7 or something else.

Your scenario:

Upload Win2008R2 Image to Azure
Enable Hyper-V on uploaded Azure image

You will fail on step 2.

You will get something like this:

The processor on this computer is not compatible with hyper-v .........

The official Resource from MSDN is here:

Strong name validation failed. (Exception from HRESULT: 0x8013141A)

Celtic_Guy — Tue, 20 Mar 2012 15:34:00 GMT

If you come across this error:

{"Could not load file or assembly 'TheAssemblyYouHaveReferenced' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)":"TheAssemblyYouHaveReferenced'}

And you meet the following criteria

You are referencing a Delay Signed Dll in your project
Your OS is Win7 x64 or Vista x64
You have the messages mentioned above.

You can create a "MyDisableRegistryFile.reg" file with something like below:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\StrongName\Verification\*,58845dcd9090cc91]
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\StrongName\Verification\*,58845dcd9090cc91]

Where 58845dcd9090cc91(Fictious Value :-)) is the PublicKeyToken. If you create this file you can run it on each deployment or machine as part of your install process.

It should be pointed out that disabling SN verification isnt very secure but you may have your own reasons.

Also beaware your dll thats causing the error may have referenced other dlls that may have the same problem, so you may have to do this multiple times.

Quick fix use C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin\x64\sn.exe if on X64 and combine with -Vr <dllpath> if you want to disable verification too(-Vr is case sensitive). This is basically because sn.exe is 32bit and always returns success even in failure.

If you dont have the SDK installed for SN then get it here: http://www.microsoft.com/en-us/download/details.aspx?id=8279

This blog has some more information too -> http://blogs.msdn.com/b/shitals/archive/2008/05/01/8446582.aspx

Cannot find the X.509 certificate , load cert WCF

Celtic_Guy — Tue, 15 Nov 2011 15:28:11 GMT

I just had an interesting problem trying to load a cert for my WCF service. The cert was installed perfectly into both the Local machine and current user store.

No matter what I could do I couldnt get the WCF service to load the aqppropriate client certificate using its thumprint. It always just couldnt find it. It turns out that its actually quite easy and that I was making one silly mistake that I didnt see anywhere else online. The certs thumbprint requires you to remove all the spaces.

WSHttpBinding sampleBinding= new WSHttpBinding();

sampleBinding.Security.Mode = SecurityMode.Transport;

sampleBinding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Certificate;

EndpointAddress ea = new EndpointAddress(" https://myerviceaddress.svc");

WsClient wsClient = new WsClient(sampleBinding, ea);

wsClient.ClientCredentials.ClientCertificate.SetCertificate(StoreLocation.LocalMachine,StoreName.My, X509FindType.FindByThumbprint, "6827A9E09EEE24C6290C808ACEDD000FFC825345");

If you want the certs properties so that you can just get them as it expects you could also just load them like below and print to intermediate window or look them up through the locals and copy the values in..

X509Certificate2 actualCert = new X509Certificate2(@"C:\Certpath\cert.pfx", "password");

The certmanager does this but I find this easier when your programming it exactly as it should expect

SilverLight Get user or Windows Credentials

Celtic_Guy — Sat, 11 Dec 2010 14:48:00 GMT

SilverLight hosted in ASPX with WCF integration to retrieve user Credentials:

First Setup IIS correctly:

1:Create a new AppPool in IIS and give it an identity with suitable privileges - Ill call it “NewAppPool”

2: In IIS add a new application “Example”

3. Edit the Basic Settings so your new app uses the “NewAppPool”

4. In Authentication –

· Disable Anonymous access

· Enable Windows Access

This example assumes you have an ASPX site hosting your SilverlightApplication and the ASPX Site also exposes a WCF service that you are using to get\send some data which requires some form of user authentication

In your WCF Config make sure you have your authentication scheme set to Negotiate. Windows or NTLM will not work when deployed on IIS. NTLM will only work on your ASP.NET Development server when you press F5.

</binding>

</customBinding>

Now Configure your WCF service\Silverlight to work on IIS.

Wcf First and then ASPX binding’s:

In your binding in the web.config, comment out the IMetaDataExchange. This causes the infamous error “Security settings for this service require ‘Anonymous authentication but it is not enabled for the IIS application ….. ”. This endpoint forces your service to use Anonymous bindings, so remove it or change it..

<endpoint address="" binding="customBinding" bindingConfiguration="MyApsxWebSite.MyService.customBinding0"

contract="MyApsxWebSite.MyService" />

</service>

The system.web should be like below– Select Windows:

<system.web>

</authentication>

</system.web>

· Now build\save and publish to your IIS location. I have intentionally not mentioned SL app yet.

· Once published and setup correctly in ISS Open your SL app in Visual Studio.

· If you had an existing service reference to this service delete it.

· Now add a new Service Reference and point it at http://MyMachineName/Myservice.svc

· Compile\Build the SL App

· Locate it in the ClientBin folder of your ASPX build location

· Copy it to your published ClientBin folder where IIS accesses it and replace the one that is there with this one.

· Run your service and you should be able to access user credentials by passing them to the SL app via InitParms(Not secure) in your aspx page hosting the SL app.

In SL retrieve them by

private void Application_Startup(object sender, StartupEventArgs e)

{

string UserID = e.InitParams["UserAccount"];

}

Or in WCF use the HttpContext to do as you require and limit windows access.

You should have your SL app running and retrieving the user credentials you require.

Really hope this helps!

Thanks

Keith

Silverlight cant communicate with WCF in certain config situations - solution

Celtic_Guy — Mon, 29 Nov 2010 22:28:00 GMT

Sample Error piece: Check InnerException for exception details. at System.ComponentModel.AsyncCompletedEventArgs.RaiseExceptionIfNecessary()

This problem manifests for me in the following situation.

Silverlight App hosted in a ASPX site
The Silverlight app is a data-consumer and requires data via a WCF service also hosted in the ASPX Page

Everything works fantastic when you run it via F5 in VS. Once published to IIS it stops communicating with WCF.

Two problems cause this:

The Silverlight app is defaulting to the http://localhost:25775/servicename.svc
1. Get rid of the port number as it thinks your trying to communicate across domain http://localhost/servicename.svc
2. Note this wont work via VS when you change it
If you have that fixed but the silverlight app reverts to being unable to communicate with the WCF service again when called remotely you need to do the following(works for me anyway):
1. Publish the Website with all pieces, SIlverlight, WCF etc to your IIS publish location
2. Go back tot he Silverlight App and open your web reference to the service in VS
3. Change it to point at the newly deployed web service location
4. Change LocalHost to your server name or what ever your setup is. ie http://MyServer/servicename.svc
5. Press OK in the configure service and build the silverlight app
6. Copy the newly compiled .xap file from the clientbin folder
7. Overwrite the deployed .xap file in the location where you published your service
8. Open up the silverlight app\Website from the published location

This should now communicate fine under the http://MyServer/servicename.svc but will not under http://localhost/servicename.svc as it will look for the servername and not localhost

Ideally it really should figure this out for itself in a perfect world ;-)

Really hope this helps!

The Actual errors

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Timestamp: Mon, 29 Nov 2010 21:43:41 UTC

Message: Unhandled Error in Silverlight Application An exception occurred during the operation, making the result invalid. Check InnerException for exception details.   at System.ComponentModel.AsyncCompletedEventArgs.RaiseExceptionIfNecessary()
   at MyService.GetMyJobsCompletedEventArgs.get_Result()
   at MyService.MainPage.t_GetMyJobsCompleted(Object sender, GetMyJobsCompletedEventArgs e)
   at MyService.MyClient.OnGetMyJobsCompleted(Object state)

An exception occurred during the operation, making the result invalid. Check InnerException for exception details.

[ExceptionOccurred]
Arguments:
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=4.0.50917.0&File=System.dll&Key=Async_ExceptionOccurred

Installutil Windows Service - Not installing - Where is it? ;-) Service missing!

Celtic_Guy — Tue, 23 Nov 2010 18:17:00 GMT

Windows Service – Not installing .Net 4 VS2010 - Where is it? ;-)

This is only relevant if your service installs perfect but you can find it – Where is it? It should be identifiable in the services.msc but its not there??

InstallUtil doesn’t complain during install so whats the problem.. ??

Simple & obvious when you know why – in VS2010 when you add your serviceInstaller and your serviceProcessInstaller the parent property doesn’t get set automatically like in previous versions of VS.

To Fix:

Goto your ServiceInstaller and set the Parent property from none to your ProjectInstaller

OR IN THE CASE WHERE YOU HAVE RENAMED THE PROJECTINSTALLER CHANGE THE SETTIGN THERE!

Should work like a gem ;-)

Keith

WCF - Error 500.21 Handler "svc-Integrated" has a bad module "ManagedPipelineHandler" in its module list"

Celtic_Guy — Mon, 08 Nov 2010 12:21:00 GMT

WCF - Error 500.21 Handler "svc-Integrated" has a bad module "ManagedPipelineHandler" in its module list"

If you see this error you havent installed the prerequistes for ASP.NET 4.

Try this

Open Visual Studio Command Prompt
Type the following:
1. aspnet_regiis.exe -i
Run the command
Try your service again...
Happy Face - it should be working :-)

This basically installs the necessary ASP pieces to get your service up and working!

Enjoy..

Keith

IIS 7 Change DefaultAppPool to Network Service for this error 'System.DirectoryServices.DirectoryServicesCOMException’

Celtic_Guy — Tue, 13 Oct 2009 14:09:00 GMT

You may need to do this when your running you web component WCF service or whatever and you receive unusual errors like ‘System.DirectoryServices.DirectoryServicesCOMException’ when using directory services.

This is due to the fact that by default IIS7 runs as ‘IIS APPPOOL\\DefaultAppPool’ and doesn’t have enough permission. Change to Network service and it should be fine!

Quite simple to do it, just in case your more used to IIS6 :-)

1. Start->Run-> Type 'inetmgr'

2. Expand the server name on the left connections panel and you will see Application Pools

3. Click ‘DefaultAppPool’

4. Click ‘Advanced Settings’

5. Goto ‘Process Model’ Section

6. Select 'Identity' = 'Network Service'

Hope that helps!

Keith

HTTP could not register URL http://+ . Another application has already registered this URL with HTTP.SYS

Celtic_Guy — Mon, 10 Aug 2009 18:45:00 GMT

Have you come across this issue HTTP could not register URL http://+ . Another application has already registered this URL with HTTP.SYS

Are you self hosting a WCF library service inside a console or windows forms application? Then the most likely cause of this problem is that you have the library project contained within your same solution.

The problem happens because the WCF Service Host running at the same time as your custom host application. You run or debug your app and when your host initialises the WCF stack, you will see an AddressAlreadyInUseException as in the above pic. This is happening because the WCF Service Host in Visual studio is already listening on the same address...

Basically remove the wcf lib from the solution and reference it. When you run the host you should now be able to open it.

ServiceHost host = new ServiceHost(typeof(ClientHost));

Host.Open();

Now there should be no errorJ!

Rick Rainey's suggested a fix to the config file which doesn’t work for me, but may for somebody else which prevents removing it from the project. http://blogs.msdn.com/rickrain/archive/2008/02/14/Preventing-the-WCF-Service-Host-from-launching-in-Visual-Studio-2008.aspx

I have not seen if this bug exists in 2010 yet.. I will update when I check it..

WCF library in Windows service common error

Celtic_Guy — Tue, 07 Jul 2009 18:23:00 GMT

Service '<ServiceName>' has zero application (non-infrastructure) endpoints. This might be because no configuration file was found for your application, or because no service element matching the service name could be found in the configuration file, or because no endpoints were defined in the service element.
   at System.ServiceModel.Description.DispatcherBuilder.EnsureThereAreNonMexEndpoints(ServiceDescription description)
   at System.ServiceModel.Description.DispatcherBuilder.InitializeServiceHost(ServiceDescription description, ServiceHostBase serviceHost)
   at System.ServiceModel.ServiceHostBase.InitializeRuntime()
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at <ServiceName>.Service1.OnStart(String[] args) in

This problem is for when you have a WCF library and your integrating it into a Windows service.

Ok check the following. When you added your app.config file from the WCF library into your windows service did you alter the name?

What I mean is:

<Service name=”Namespace” + “Type” ....

When you copied it over it had the old namespace and type from the WCF library. In your windows service alter the app.config to match your service as per example below.

namespace TestServiceNamespace

{

class TestTypeService: ServiceBase

{

}

The service name would be testNamespace in the windows servioce

<Service name=” TestServiceNamespace.TestTypeService” ....

Hopefully this saves you a piece of time..

WCF - Debugging not enabled on server

Celtic_Guy — Fri, 15 May 2009 20:29:00 GMT

Have you a WCF service and you are trying to Debug it?

Are you unable to step into the code from you test application... And is this the first time running your WCF service on your server or local dev machine?

Well if you have set the web config file correctly - <compilation debug="true'/> AND <serviceDebug includeExceptionDetailInFaults="true"/>

then try this - Reboot your machine!

Sounds obvious but I would have liked someone to call out this most obvious fact! It would have saved me 2 or 3 hours.. I obviously had some IIS issue.. possibly iisreset may work too:-)

x64 Unit Tests in Visual Studio 2008(Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll)

Celtic_Guy — Thu, 02 Apr 2009 13:32:00 GMT

Are you in the following scenario:

Your requirement is to compile your managed application as x64
Your requirement is for your application to consume or communicate with unmanaged COM x64 components
During development you want to follow a TDD\ agile approach or you want to build a suite of unit tests for your managed app in Visual Studio Team System 2008.

Well if this is you, then you realise you may be in a bit of trouble. The Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll is x86 and there is no x64 version. If your trawling the internet looking for the x64 version you wont find it. Compling your tests as 'Any Cpu' and using it against your x64 component you are consuming will not work as intended. You will receive Bad Format exceptions like below..

Error: System.BadImageFormatException: Attempted to load a 64-bit assembly on a 32-bit platform. Use ReflectionOnlyLoad() instead if trying to load for reflection purposes.

if you complie as x64 and if you dont the unmanaged component cannot be expected to work correctly(And it wont)

This wont cause issues if your system your developing is all managed, but if it isnt then be aware.

The good and bad news is that its fixed in VS2010 and the fix and should be available in the latest CTP.

Set DNS server Addresses Progamatically

Celtic_Guy — Mon, 16 Mar 2009 16:45:00 GMT

To just read quickly individual DNS and Network configuration properties you can use the System.Net.NetworkInformation to help.

Create your NW information class.

NetworkInterface[] nw = NetworkInterface.GetAllNetworkInterfaces();

This returns the first DNS entry as a string.-> nw[0].GetIPProperties().DnsAddresses[0].ToString().

You can obviously expand massively on this, just refer to MSDN.

If you need to set The DNS entries programtically you should use WMI(You have loads of functionality for reading and setting Im just showing the DNS piece here). An example below should help you do this. This method makes sure the device it finds is an IP enabled device and matches the NIC. Apologies for the formatting i cant get it right but you get the idea! it sets both DNS IP addresses's to the fictitious(111.11.11.12 & 111.11.11.11)

public void SetDnsConfig()

{

ManagementClass mc = new ManagementClass("Win32_NetworkAdapterConfiguration");

ManagementObjectCollection moc = mc.GetInstances();

string nic = string.Empty;

foreach (ManagementObject mo in moc)

{

if ((bool)mo["ipEnabled"])

{

nic = mo["Caption"].ToString();

if ((bool)mo["IPEnabled"])

{

if (mo["Caption"].Equals(nic))

{

ManagementBaseObject DnsEntry = mo.GetMethodParameters("SetDNSServerSearchOrder");

DnsEntry["DNSServerSearchOrder"] = "111.11.11.11,111.11.11.11".Split(',');//Two ip addresses you want to set

ManagementBaseObject DnsMbo = mo.InvokeMethod("SetDNSServerSearchOrder", DnsEntry, null);

int returnCode = int.Parse(DnsMbo ["returnvalue"].ToString));//This will give you the return code you can use to evaluate if its not working

break;

}

Hope this helps:-)

Exchange 07: Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC)

Celtic_Guy — Tue, 06 Jan 2009 20:58:00 GMT

Environment for this issue: Exchg 2007 Win2008 SP1 & 2 Domain controllers Win2003 SP2

If your exchange installation was working and then suddenly stopped working with the error below.( Try this if your having an installation issue to, allthough this specific issue appeared after it was working fine for a few months).

(Some services won’t start ??)

Microsoft Exchange Active Directory Topology Service

Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=3268). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.

Goto Active directory on your domain Controller and add your exchange server as a 'Computer' on the 'Domain Admins Group'. Thanks to cchalmer on this aswell.

This worked fantastically for me with a reboot.

Also you can ref:

http://forums.microsoft.com/technet/showpost.aspx?postid=599509&siteid=17&sb=0&d=1&at=7&ft=11&tf=0&pageid=0

Please use this at your discretion as its not an official solution only a different suggestion to address your problem and not ideal from a privacy point of view. I have other alternatives in this blog which may address your problem without going down this road.

Exchange 07 - WIN2008: IPV6 is installed but Service 'MsExchangeTransport' failed to reach status 'Running' on this server.

Celtic_Guy — Tue, 04 Nov 2008 20:25:00 GMT

On Win2008 server setup of Exchange07 SP1 you may still have the error above if you have IPV6 installed and is not your current problem.

The most likely cause of these errors are

You may not have met the prerequisites

The exchange team Blog site has made a group of XML files available which help to install all the Exchg07 with 2008 issues. These Files are available here and are used with ServerManagerCmd

http://msexchangeteam.com/files/12/attachments/entry448276.aspx

a good blog article here will walk you through the setup

http://www.petri.co.il/installing-exchange-2007-prerequisites-on-windows-server-2008.htm

Microsoft's Official link to install the prerequisites is

http://technet.microsoft.com/en-us/library/bb691354(EXCHG.80).aspx

Remember you will need to extend Active Directory on your domain controllers using setup.com before you install Exchange too. To do this do the following

http://technet.microsoft.com/en-us/library/bb125224(EXCHG.80).aspx

Once complete it should work BUT - did you have previous failed installs? if you did expect

"The Exchange server is in an inconsistent state. Only server recovery mode is available."

to fix this follow this article and its suggested fix - do this on the domain controller

MS Fix -> http://technet.microsoft.com/en-us/library/cc411332(EXCHG.80).aspx

And forum Fix - basically the same..

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1186078&SiteID=17

"This problem seems to relate back to the AD. If you have installed Exchange 2k7 previous then the AD contains information about the Exchange server that must be removed. I deleted the 2 MS Exchange containers in the AD Users and Settings.

Then found a folder ExchangeSetupLogs and a file in there should be Exchange Setup.log. Opening this file you should see line like

Exchange Configuration Container for the Organization is....
Exchange Organization Container for the Organization is.....

This means it found it's self in the AD. I then went to the Domain Controller and ran ADSIEDIT.MSC.

Under Configuration --> CN=Configuration -->CN=Services

You should see CN=Microsoft Exchange. All I did was remove this entire entry and everything underneath it. The install works fine now."

Exchange 07 - WIN2008: Service 'MsExchangeTransport' failed to reach status 'Running' on this server.

Celtic_Guy — Thu, 16 Oct 2008 15:34:00 GMT

If you have seen this error "Service 'MsExchangeTransport' failed to reach status 'Running' on this server" during exchange installation setup on Win 2008 check to see if you have done the following.

Check both of these:

By default you may have turned off IPv6 as you may have thought you didn’t require it during the installation of Win2008 or at a later stage. Also it is standard procedure to turn off unused features. Previous versions of exchange were fine with IPv4
You may have done nothing and assumed correctly that IPv6 is installed by default on Win2008.

Well if you have either situation then this is the likely cause of your problem.

If IPv6 in not installed -> reinstall it
Doing this from the command prompt may be easier -> "netsh interface ipv6 install" or

If you have the default install goto Start->Network(Right Click)->Properties->Mange network connections->(right click relevant connection)->Select Internet Protocol Version 6-> Click Install-> Add the relevant Service\Protocol\Client features.

Doing this from the command prompt may be easier

Trying to kill the service and do anything manually to it doesnt make a difference..

Reboot the machine and reinitiate the setup

Fingers crossed and this does the trick - hopefully it helps ;-)

If not there is a transport forum available from Microsoft at http://forums.microsoft.com/TechNet/ShowForum.aspx?ForumID=844&SiteID=17

update 19/01/09 if this fails ref my blog item. this will work

Exchange 07: Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC)

195

WCF - Getting your web Service to work on XP & VS2005 & VS2008

Celtic_Guy — Fri, 03 Oct 2008 18:10:00 GMT

If you are having trouble getting your WCF service running on winxp and eveything seems like it "should" work but doesnt!! It seems like the service is just not getting recognized. Try these tips and see if they help. Im assuming ASP.NET version 2 installed and configured aswell as .NET3.0 & 3.5 and VS2005 as IDE.

First check to see if you have a mapping for the ".svc" extension in IIS.

Goto IIS->Properties(Of the service)-> Virtual Directory->Coniguration->Mappings
Look for the .svc in the mappings
If its not there add it.

Executable: (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll)
Extension: .svc
Verbs: All verbs -> Click OK

Next you probably havent registered WCF service model with IIS.
Open VS Command prompt and map to C:\WINDOWS\Microsoft.Net\Framework\v3.0\Windows Communication Foundation
Install the ServiceModelReg exe using the command prompt -> ServiceModelReg.exe -i
This fixes the registry and config files etc
Try bowse the service in IIS.. It probably will work but now try it in the browser - it wont!!
Getting there though :-) Next go back to basics and uninstall ASP.NET and reinstall it
In the command prompt do the following in order:

aspnet_regiis -ua
aspnet_regiis -i
iisreset

Now try agian in the browser after Publishing! It should work..

For Vista and VS2008

Its allot easier.. Just goto Control Panel->Program and features->Turn Windows Features On and Off->Microsoft .Net Framwork 3.0 and then tick all the WCF boxes and install the components.. it should work a treat..

Groove Data Bridge - Create a GFS Space

Celtic_Guy — Mon, 13 Aug 2007 18:56:00 GMT

Create a Groove File Share using the Groove Data Bridge and invite people in using the GDB.

To do this you must have the contacts Vcards of the people you are trying to share files with.

First goto http://www.codeplex.com/GWSV12Helpers and install the Groove Web Service Helpers. You can take the code or the binaries.

These are web Service helpers that enable you to perform all the functionality of the Groove client using the GDB

Create a config file(Install it anywhere - It saves you reentering data all the time):

You can get all these values from GrooveDir /? for all the values except the RequestKey( Search for LocalRequestKey)

You will need to make sure the webservices are activated in the GDB management console first too

To Create the GFS do the following:

Open the command Prompt and map to GrooveCreateSpace
GrooveCreateSpace /x=c:\config.txt /GFSPath=C:\GFS\Test /Name=Test

To then invite someone into your new GFS

1. GrooveDir /f to get the URI of the new new GFS you created
Enter the new URI in the Config file.
GrooveInviteToSpace /x=C:\Config.txt
The user should now get a invite to a shared GFS on the GDB.

Thats it, you should be up an running