servicesengine Forum Rss Feed

New Post: Error during Installation

navneethnaik — Fri, 21 Sep 2012 11:14:34 GMT

Hi,

I am trying to install MSE (Managed Service Engine) on my desktop, but I am getting the below error at the last:

"Microsoft Managed Services Engine December 2009 CTP Setup Wizard ended prematurely"

Microsoft Managed Services Engine December 2009 CTP Setup Wizard ended prematurely becuase of an error. Your system has not been modified. To install this program at a later time, run Setup Wizard again. Click the Finish button to exit the Setup Wizard.

Details of the environment:
Windows Version: Windows 7 Enterprise Edition
MSE Version: MSE_7.5.0.0_x86.msi
SQL SERVER: SQLSERVER EXPRESS 2012

Did any one encountered similar issue or similar kind of issue? How do i know what is the cause of failure.

New Post: SLAs alerts

williamo — Thu, 05 Apr 2012 08:38:51 GMT

Take a look at LinkSpan if you want easy SLA monitoring. It allows you to set up automated test calls that independently validate SLAs on a schedule of your choosing. You can then specify email alerts when your threshold has been passed or the API is unavailable. This is a cloud-based solution that requires zero install and can with with WCF or non-WCF APIs.

New Post: SLAs alerts

aslivker — Fri, 27 Jan 2012 00:23:50 GMT

Nevatech has released Sentinet product (based on Microsoft WCF 4.0) that has capabilities you were looking for (plus more), http://www.nevatech.com/sla.aspx .

New Post: December 2009 CTP is final and last release of MSE

blairsh — Tue, 15 Nov 2011 01:42:38 GMT

We have updated the project home page to reflect the following:

Status & Roadmap

The December 2009 CTP Release was the final release of the MSE. There are variety of Microsoft products that can be leveraged to build loosely coupled applications and this article references many of the approaches, How to Integrate a BizTalk Server Application with Service Bus Queues and Topics.

Thanks for all your comments and suggestions over the past 5 releases of the MSE.

In closing, we want to direct you to section 3.(E) of the License Agreement regarding the support clause. As a CTP release we do not recommend this be used in production or provide support. If you wish to explore additional options for service virtualization, please contact your closest Microsoft Consulting Services office.

New Post: New alternative to MSE

andrewsli — Thu, 03 Nov 2011 18:52:37 GMT

There is a new product on the market developed by Nevatech. It is called Sentinet. It is built entirely on the Microsoft platform on top of .NET 4.0, WCF, WCF Routing Service and WIF. The product is more powerful, intuitive and does not require any custom coding in order to use it, even though it has a lot of WCF standard and custom extensibility points. It also works in Windows Azure and extends AppFabric Service Bus capabilities. See http://www.nevatech.com/overview.aspx

New Post: Problem with MSE universal service tester, urgent

RaSv — Fri, 28 Oct 2011 20:08:14 GMT

hi, I have a problem whit MSE tester when i call a wcf service for silverlight.

Return this message: "Failed to autogenerate Input Message due to Error[Failed to sniff service]. Please provide input message."

i don't know what can be...!

please your help !

thk

Roberto

New Post: Future of MSE

botto — Thu, 29 Sep 2011 20:28:21 GMT

There is no further work being performed on the MSE and the team was unable to release the full source code to the codeplex community; which is not how the team wanted to leave this project.

Windows Azure, AppFabric and BizTalk are the product backed choices from Microsoft to work with and follow.

Cheers.

New Post: Future of MSE

AhmedA — Wed, 28 Sep 2011 09:51:51 GMT

I downloaded MSE and tried it out about a week ago as a step of evaluating different service management systems for our corporate webservices. I must say i really liked the easy way to manage webservices in MSE and it feels like a mature products in many ways, but i am a bit concerned about the future of this product.

There has not been a new release in over a year and there is not so much references or activity about this product in general. When ever im discussing web services with a developer they either referer to Biztalk or Windows Azure and none of theese alternatives seems suitable for our environment.

Does anyone know if the development of this product has stagnated?
Is there a replacement for this product and if so. Where can i find it?
Does anyone know if there are any similar products like MSE, except Biztalk which is to large for our corporate needs?

I really apreciate if you can help me with my questions.

Thanks in advance.

/Ahmed

New Post: Same method name in two different services

Venu12 — Mon, 23 May 2011 14:55:36 GMT

I have the same operation name in two totally independent services. When I import the wsdl using 'Virtualize Service Operations', how can I keep the same 'operation' name without making it another version of the existing operation which is the defautl MSE behavior. The reason for this is we are already calling our WCF services and don't want to rewrite the client code using new operation names. We just want to configure the client service reference to point to the service in the MSE repository. Thank you.

New Post: The Next Step

sirclaudio — Mon, 16 May 2011 10:47:41 GMT

How about posting the entire source code and leave the project for the community?

New Post: Consuming the Created Virtual Service In Client

praveenspp — Mon, 07 Feb 2011 13:30:13 GMT

Hi,
Im new to MSE, i had virtualised one of my wcf service using MSE model viewer. Its worked well when tested using MSE Service Tester, but when i consumed the virtual service
in a custom test client by AddService Reference Tab, the reference.cs file of the service reference does not contain the definitions for the data contract available in that wcf service, but all
data contract definitions are found when the virtual service viewed via Browser(svcutil.exe).
Anyone please help me out in this context.

Thanks in Advance
Praveen

New Post: Error while loading a web service published in a Jaguar Server

malrousan — Thu, 03 Feb 2011 07:20:43 GMT

Dear All

am also facing this problem when importing the below WSDL received from a customer

<?xml version="1.0" encoding="UTF-8" ?>

- <definitions xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="urn:smsprowsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:smsprowsdl">

- <types>

- <xsd:schema targetNamespace="urn:smsprowsdl">

<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />

<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />

</xsd:schema>

</types>

- <message name="sendsmsRequest">

</message>

- <message name="sendsmsResponse">

</message>

- <portType name="smsprowsdlPortType">

- <operation name="sendsms">

<documentation>SMSPRO SendSMS web service Parameters: - mobile(M): Mobile number of the subscriber to whom the SMS has to be delivered. mobile number should be in the international format, example 96279999999 - message (M): SMS text that has to be delivered to the specified subscriber. - username(M): The login name to authenticate the usage of the service. - password(M): The password for the login to authenticate the usage of the service. - sender(M): sender name, English only, maximum size allowed is 11 chars. space and special characters are not allowed. - charset(Optional): Character set, should be windows-1256 or UTF-8 only.</documentation>

</operation>

</portType>

- <binding name="smsprowsdlBinding" type="tns:smsprowsdlPortType">

<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />

- <operation name="sendsms">

<soap:operation soapAction="urn:smsprowsdl#sendsms" style="rpc" />

- <input>

<soap:body use="encoded" namespace="urn:smsprowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />

</input>

- <output>

<soap:body use="encoded" namespace="urn:smsprowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />

</output>

</operation>

</binding>

- <service name="smsprowsdl">

- <port name="smsprowsdlPort" binding="tns:smsprowsdlBinding">

<soap:address location="http://172.24.13.4/soap/sendsms.php" />

</port>

</service>

is </definitions>

is it aplicable on the MSE ???

New Post: The Next Step

exuviae — Tue, 21 Dec 2010 21:33:49 GMT

actually the code in the source repository won't compile, however the compiled version seems to run if you are ok with no support, no source, and no updates.

New Post: The Next Step

nesteruk — Fri, 17 Dec 2010 13:10:10 GMT

So hold on, is the MSE posted here usable? I realize there won't be any support, just curious if it's production-ready or just a beta

New Post: The Next Step

kennyboy — Wed, 01 Dec 2010 10:33:57 GMT

I'm interested in those things.... had a quick look - good luck to the boys but I can't see a product described anywhere?

New Post: The Next Step

williamo — Tue, 16 Nov 2010 00:23:58 GMT

For those of you that are interested in versioning, protocol mapping, service modeling and some of the other core features of the MSE, you might want to check out http://www.opusgrid.com/blog/post/2010/11/08/The-Next-Step.aspx. The original people behind the MSE have left Microsoft to launch a startup that you might find interesting.

New Post: Setup MSE as a trusted subsystem

Styvie — Mon, 15 Nov 2010 13:29:40 GMT

Hi,

I have a similar scenario to the one listed here http://servicesengine.codeplex.com/Thread/View.aspx?ThreadId=18743

I have a WCF service that requires Windows Authentication. I want to setup MSE as a Trusted Subsystem as mentioned in many of the documents. I don't have the ability to change the Authentication (it's Microsoft Dynamics NAV Webservices), and the calling application we can't get to specify Windows Auth credentials (long story).

A trusted subsystem scenario would work for me:

Here are the steps I have followed to try and test this:

Install MSE with a domain account that has permissions to the WCF services.
Tools->Load Resources->Web Services Metadata
Fill in the location of my WSDL, and follow the prompts to completion.
The binding that is defined in the import BasicHttpBinding
I create a New Endpoint, drag the Operation over. (This is where I am confused - which Binding should I use ?) , I selected WsHttp(12)
Edit the LocalRS and drag then EndPoint over.

Browse to my endpoint and I can see it fine.

I open the MSE Service Tester, discover my WSDL, double click the operation.

I then try and test it, and get the following :

The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'Negotiate'.

I tried to test the MSE service using WCFStormLite and get the same error. (In WCFStormLite i set "Windows Auth" and "Impersonation")

I add the original WCF service to WCFStorm and I can execute the service.

My binding in the MSE Service Tester is

And that is where I get stuck.

Is there any documentation to show how to setup the trusted subsystem ? And which Bindings should be set at which point ?

Any suggestions help would be appreciated ?

Thanks,

Steve

New Post: Future of MSE

mjaplin — Wed, 10 Nov 2010 01:47:36 GMT

We've implemented the MSE on a limited basis and based on in-house conversations with Microsoft reps MSE will go away and be absorbed by other "Product" technologies, specifically the Windows Server platform. Based on what I've read of AppFabric and WCF, there will only be a small portion of functionality in the MSE not covered by other supported technologies. When and how this all comes together, not sure. Understood that this is Codeplex/MS Consulting release, but I've been disappointed with the guidance and lack of anything resembling a product roadmap. Especially since this software has been featured in Microsoft publications. I never really got the "use at your own risk" vibe from this one until recently.

New Post: Future of MSE

sahridhayan — Tue, 02 Nov 2010 05:19:20 GMT

we also waiting for some insights on the above points,

also we have some connecting parts in our architecture to BizTalk 2009 ( we know that from this link http://msdn.microsoft.com/en-us/magazine/dd727511.aspx) BizTalk 2006 integration is possible)

any one can point out any issues since UDDI become part of BizTalk and BizTalk 2009 integration ?

Thank you

sahridhayan

New Post: A Policy implement IOperationBehavior does not working correctly!

quanxj — Wed, 27 Oct 2010 08:20:54 GMT

I implement a class implement IOperationInvoker named CacheOperationInvoker, and I want to use it by my IOperationBehavior called CacheOperationBehavior.

in CacheOperationBehavior code likes:

public class CacheOperationBehavior:IOperationBehavior

{

...

       public void ApplyDispatchBehavior(OperationDescription operationDescription,
            DispatchOperation dispatchOperation)
        {
            dispatchOperation.Invoker = new CacheOperationInvoker(dispatchOperation.Invoker,dispatchOperation.Action);
        }

...

}

I make a policy called cachingPolicy which used on OpeVersion, but it does not work?

why?

Thanks for your reply and time!