博客园_Life is a journey

BizTalk: Database ‘BizTalkMsgBoxDb’ is full

2012-02-08T10:13:00Z

Error:

The transaction log for database ‘BizTalkMsgBoxDb’ is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases (.Net SqlClient Data Provider)

Solution:

sp_helpdb ‘BizTalkMsgBoxDb’

ALTER DATABASE BiztalkMsgBoxDb

SET RECOVERY SIMPLE;

DBCC SHRINKFILE (BiztalkMsgBoxDb_log, 1);

sp_helpdb ‘BizTalkMsgBoxDb’

ALTER DATABASE BiztalkMsgBoxDb

SET RECOVERY FULL

本文链接

Fiddler and Application Proxy setup

2012-01-26T02:39:00Z

Original from: http://www.west-wind.com/weblog/posts/2004/Oct/11/Fiddler-and-Application-Proxy-setup

I’ve been working on a couple of apps that do extensive HTTP and Web Service access over the last few days and Fiddler has been a huge help in debugging some odd problems I’ve been having. This ASP.NET Web app has both .NET and FoxPro clients talking to it and checking out the traffic and difference of the client communication was driving me nuts for a while.

One tool I continue to use all the time when working on any sort of distributed application is Fiddler. If you haven’t used Fiddler before, run, don’t walk and download this awesome little proxy that lets you easily see the content of requests made over HTTP over the network. It works great, but keep in mind it doesn’t work for Localhost (it might with a loopback adapter though – haven’t tried it) or over HTTPS in which case you have to remember to step it down to HTTP for debugging. It’s great for debugging problems in distributed applications, but is also great if you need to debug Web based applications for things like Cookies, custom headers etc. What makes Fiddler nice is that shows both content and headers and lets you easily view all of this diverse content in a somewhat intuitive way – for example, images can be previewed, XML can be viewed as a node list and you can apply viewers to any content sent or returned. If you’re building any kind of Web application sooner or later this functionality will come in REAL handy.

Fiddler works by setting up a proxy on port 8888 and then re-routing Web requests through it. It does this by basically changing IE’s proxy settings on the fly.

If you’re using a .NET client though you will have to configure the client in order for Fiddler to be able to see the communication. By default the .NET HttpWebRequest uses direct connections – meaning it doesn’t check or use for any proxies in the system and will thus not be picked up by Fiddler once it’s started.

If you’re using .NET you have to tell the .NET HTTP clients to use a proxy object. .NET allows you to custom configure a proxy using the Proxy property. The Proxy object is available both on lower level objects like HttpWebRequest as well as on higher level objects like a Web Services proxy.

You can configure a Proxy object manually by creating a new WebProxy object:

WebRequest.Proxy = new WebProxy("127.0.0.1:8888",true);

or probably the better choice: You can use the default proxy which reads the Internet Explorer settings for the current user:

WebRequest.Proxy = WebProxy.GetDefaultProxy();

You can apply the same logic to a Web Service client’s Proxy property as well.

If you’re using the MSSOAP Toolkit, you also have to do some custom configuration. You also need to set the Proxy server using the appropriate ConnectorProperty:

THISFORM.oNet = CREATEOBJECT("MSSOAP.SoapClient30")

THISFORM.oNet.MSSOAPInit(lcWSDLURL)

thisform.oNet.ConnectorProperty("ProxyServer")="<CURRENT_USER>"

…

loNL = thisform.oNet.LoadAuthors("");

If you’re using WinInet you can use a Connection type in Interopen:

hInetConnection=;

InternetOpen(THIS.cUserAgent,;

THIS.nhttpconnecttype,;

THIS.chttpproxyname,THIS.chttpproxybypass,0)

Where the ConnectType is 0 for IE Configuration, 3 for custom proxy, and 1 for direct access. Generally you’ll want to use 0. If you’re using wwHTTP in Visual FoxPro, nHttpConnectType is defaulted to 0 which maps to this WinInet setting.

本文链接

Distinguished Fields and Optional Elements

2011-05-18T10:03:00Z

Thought this might be of interest to a few BizTalk developers out there.

It's quite common practice to use Distinguished Fields in orchestrations, to get/set the value of an element or attribute.

However, if the element you're trying to set/get doesn't exist, then this poses a few problems.

Setting a Distinguished Field
If the element/attribute doesn't exist in the target message, then you'll get an exception, no questions asked – there's no way around this.
Under the covers, the SetDistinguishedField method is called to set the value – and it doesn't check if the element/attribute exists first.
The same thing happens if you use the xpath() function to set a value, and the element/attribute doesn't exist – BizTalk isn't about to modify your message and add the element/attribute for you.

In this case, it's your responsibility to check that the element/attribute exists.
If it's a message that you create, then you have to make sure that the element/attribute is created (do this in a map by mapping an empty Value Mapping functoid to it, or setting the Value property to "<empty>").

Getting a Distinguished Field
This is more interesting.
In a nutshell, if the Distinguished Field is of type string (or any other nullable type) then you'll get null.
Otherwise, you'll get an InvalidCastException.

The reason for this is in the underlying code.

The orchestration calls XSDPart.GetDistinguishedField to get your value:
public override object GetDistinguishedField(string dottedPath)
{
    XsdDistinguishedFieldDefinition dFDef = (XsdDistinguishedFieldDefinition) base.GetDFDef(dottedPath);
    object val = base._getXPath(dFDef.XPath, dFDef.IsDynamic);
    if (val == null)
    {
        return null;
    }
    if (val.GetType() != dFDef.FieldType)
    {
        val = XmlHelpers.ChangeType(val, dFDef.FieldType);
    }
    return val;
}

This method will return null if the element/attribute doesn't exist otherwise it will attempt to convert (cast) the value to the appropriate type.

However, the InvalidCastException arises from your orchestration.
Let's assume you had a Distinguished Field called isSuccessful which is of type boolean.

When you write something like
if (Response.isSuccessful)
in an expression shape, the code generated is this:

if (!((bool) __ctx2__.__Response.part.GetDistinguishedField("isSuccessful")))

Ahah! The orchestration does an explicit cast of the Distinguished Field value to a bool.
And an explicit cast of null to a bool will raise an InvalidCastException.

However, an explicit cast of null to a string is fine.

So if you had a Distinguished Field called employeeName of type string, then the same code would be:
if (!((string) __ctx2__.__Response.part.GetDistinguishedField("employeeName")))

And no exception would be raised.

Conclusion
If you're using Distinguished Fields with types other than string, and the element/attribute you're referring to is optional then you must check that the element/attribute exists before attempting to set/get a value.

In most cases, you'd do this by using the xpath() function in an orchestration
(e.g. getting a count of the element/attribute, and checking that count > 0)

Just FYI....!

Original from:http://www.bizbert.com/bizbert/2007/11/15/Distinguished+Fields+And+Optional+Elements.aspx

本文链接

Correlations in BizTalk 2004

2011-03-10T03:59:00Z

Correlations form a fundamental concept of BizTalk 2004. They specify how individual messages are related, and are used to tell BizTalk how to process them.

An advise from the heart: take your time to understand the basics of correlations in BizTalk. You will encounter many aspects of correlations when your developments are becoming more complex. With some basic knowledge, you will be able to design a solution that can indeed be realized in BizTalk. When you fail to see the intricacies of correlations, all of your attempts might result in serious error, forcing you into a new attempt for a solution.

First, a short explanation on how the “messaging engine“ of BizTalk works. When you deploy a project, the orchestrations will become available in the runtime environment. When the deployed orchestration is started, it subscribes to messages of a designated type (message type) delivered at a designated location (port). That means that, apart from taking the subscription, nothing really happens until a message arrives. The messaging engine receives the message, and determines the type. Based on this, it fires up an instance of the orchestration that subscribed to it.

So, the subscription information is essential for locating an orchestration that matches the message type when a message comes in. This information is contained in the receive shape and the connected port in an orchestration. The receive shape provides the message type the orchestration expects, the port tells (after binding) where and how messages of this type are expected.

Now, what happens when I require more than one receive shape in my orchestration? Can I receive messages of different types in a single orchestration? What about multiple instances of the same message type? How do we specify a sequence of actions?

For all questions, there is a proper solution in BizTalk. Not all answers will be discussed here. When you plan to use more than one receive shapes in an orchestration, you will have to specify the behavior of your orchestration for incoming messages on each receive shape. In other words: when a message comes in and it can be related to a specific orchestration, the messaging engine should be able to tell whether it should fire up a new instance of the orchestration for this message or it should pass this message as input to an already running orchestration instance (and: which one of the running orchestration instances). This is done using correlations and related settings of the receive shapes.

[example]

Invoice data is sent from system A to system B. The invoice data is sent as soon as it is created in system A. Another user of system A has to check the invoice and approve it. After approval, system A sends approval data to system B. In between systems A and B sits BizTalk. The idea is that BizTalk collects both pieces of information on a single invoice before sending it to system B. We can assume that the invoice data is always sent before the approval. All invoices (invoice data and invoice approval data) are uniquely identified by an invoice number.

The orchestration to do this contains two receive shapes. The first one receives the invoice message. The second one receives the invoice approval message. Only after both have been received, a message is sent out to system B. The receive shape for the invoice message has the “Activate“ property set to true. This means that any invoice message received will cause a new instance of the orchestration to be started. The receive shape for the invoice approval message has the “Activate“ property set to false. This means that the invoice approval message will only be accepted by already running instances of the orchestration. This looks great, but still something is missing. What if invoices 1234 and 1235 are created (and sent to BizTalk), and only approved of later? Two instances of the orchestration are running (one for 1234 and one for 1235) when the approval for 1235 comes in. BizTalk knows (from the “Activate“ property of the receive shape) that the approval should go into an already running orchestration instance. Which one? That is determined by a correlation set, relating the two receive shapes.

The receive shape for the invoice message is set to “initialize“ a correlation set for the invoice number. The receive shape for the invoice approval message is set to “follow“ a correlation set for the invoice number. How does this work? When a new invoice message comes in, a new orchestration is started, the invoice message is read, and the invoice number is taken out and associated with the orchestration instance. The orchestration instance is parked, waiting for the approval message (this is called “ dehydration“). When an invoice approval message comes in, it is also read. With the invoice number form the apprval message, the correct orchestration instance is looked up. This orchestration will proceed (after “rehydration“).

[end of example]

An overview of settings and components required to set up an orchestration using multiple receive shapes:

Promoted properties. In the schemas that define the message types you will be receiving, you can promote properties. This is done to make data (tag values) out of a message instance available in the message context, i.e. accessible to the environment for control. To set up a correlation, you need to promote properties from all schemas involved into a single property schema. The names of the promoted properties don't need to be equal, but ensure that there is exactly one entry in the property schema for each promoted property, no matter how different message types call this property.
Create a correlation type using the promoted property. See the “types“ section of the “orchestration view“ of the orchestration.
Create a correlation set using the correlation type.
For a simple correlation (like the example): determine which receive shape will be activating the orchestration. This will also be the receive shape initializing the correlation set (usually). The other receive shape(s) will be non-activating and will be “following“ the same correlation set.
After you have completed setting up the orchestration, check what BizTalk thinks about this by building the containing project. When you get error messages that point in he direction of multiple receive shapes, correlation sets and property schemas, you have probably created something that conflicts with the basic rule for using multiple receive shapes: BizTalk should always exactly know what to do when an instance of a message type is received. When it can not determine this (at compile time), it will not compile the project.

Please note: the example and the explanation of terms below describe a very simple correlation scenario, in which two messages are received in a fixed sequence. There are numerous other possibilities to combine multiple messages in a single orchestration. Please refer to documentation and other resources on the topic of “convoys“, as this is the way to solve the more complex problems.

本文链接

The terminal server has exceeded the maximum number of allowed connections

2011-03-04T10:04:00Z

When a user tries to connect to a machine using Remote Desktop connection, they might come across this error message.

“The terminal server has exceeded the maximum number of allowed connections“

This is because Windows Server only allows two connections through RDP, and you’ve either got two people already logged on to that machine, or you’ve got disconnected sessions that still thinks they are active. If a user simply closes the remote desktop window when they’re finished, that user will still remain logged on, unless there is a time out configured in Terminal Services Configuration as follows

Terminal Services Configuration

If the Session time out is not configured, or the logged on users are not available, you wont be able to logon to the machine. To overcome this limitation, follow the steps as below.

open a command prompt or type in the RUN prompt

mstsc /v:[00.00.00.00/SERVERNAME] /f -console

eg: mstsc /v:192.168.1.10 /f -console
mstsc /v:ADSURF /f -console

This will connect to the physical console session on the server (also known as “session zero”). You will then be prompted with the login box and provide the administrator details. Then you will be connected to the Console Session on the server. Now you can reset the disconnected user sessions from Terminal Services Manager. Please note that if you get disconnected from this console session, you will have to go physically to the machine.

More info on mstsc at Technet

UPDATE:
If you have Windows Vista with SP1 or Server 2008, use the following syntax:

mstsc /admin

If you use the old switch “/console”, it will just ignore that and proceed connecting. In Windows Server 2008, the /console switch doesn’t exist anymore because “session 0″ is a non-interactive session that is reserved for services. Difference between admin and console swtich are here.

Another workaround:

You can also query the sessions on the remote machine as an administrator of that machine. Open a command prompt as a domain administrator that the remote machine is set to or map a drive of that remote machine.

Then in the command prompt, type as below:

query session /server:servername

Replace servername with the remote machine name or IP address.

Now we have the information of all the users/sessions that are active/disconnected on the remote machine. We can now reset one of the session with the following command.

reset session [ID] /server:servername

Replace [ID] with the number from the prevoius output and servername with the remote machine name or IP address. This will reset the session and now you can login using Remote Desktop connection.

本文链接

Stay Hungry, Stay Foolish

2011-01-28T08:15:00Z

Last week, Steve Jobs and Apple launched the new and eagerly anticipated iPad. Over the years I have admired Apple for their branding, product launches and product innovation.

This post is a more personal glimpse at a much-respected and innovative thinker. I thought I’d share with you a speech by Steve Jobs where he shares three very powerful stories. It never fails to inspire me.

Steve Jobs’ 2005 Stanford Commencement Address

I am honored to be with you today at your commencement from one of the finest universities in the world. I never graduated from college. Truth be told, this is the closest I’ve ever gotten to a college graduation. Today I want to tell you three stories from my life. That’s it. No big deal. Just three stories.

The first story is about connecting the dots.

I dropped out of Reed College after the first 6 months, but then stayed around as a drop-in for another 18 months or so before I really quit. So why did I drop out?

It started before I was born. My biological mother was a young, unwed college graduate student, and she decided to put me up for adoption. She felt very strongly that I should be adopted by college graduates, so everything was all set for me to be adopted at birth by a lawyer and his wife. Except that when I popped out they decided at the last minute that they really wanted a girl. So my parents, who were on a waiting list, got a call in the middle of the night asking: “We have an unexpected baby boy; do you want him?” They said: “Of course.” My biological mother later found out that my mother had never graduated from college and that my father had never graduated from high school. She refused to sign the final adoption papers. She only relented a few months later when my parents promised that I would someday go to college.

And 17 years later I did go to college. But I naively chose a college that was almost as expensive as Stanford, and all of my working-class parents’ savings were being spent on my college tuition. After six months, I couldn’t see the value in it. I had no idea what I wanted to do with my life and no idea how college was going to help me figure it out. And here I was spending all of the money my parents had saved their entire life. So I decided to drop out and trust that it would all work out OK. It was pretty scary at the time, but looking back it was one of the best decisions I ever made. The minute I dropped out I could stop taking the required classes that didn’t interest me, and begin dropping in on the ones that looked interesting.

It wasn’t all romantic. I didn’t have a dorm room, so I slept on the floor in friends’ rooms, I returned coke bottles for the 5¢ deposits to buy food with, and I would walk the 7 miles across town every Sunday night to get one good meal a week at the Hare Krishna temple. I loved it. And much of what I stumbled into by following my curiosity and intuition turned out to be priceless later on. Let me give you one example:

Reed College at that time offered perhaps the best calligraphy instruction in the country. Throughout the campus every poster, every label on every drawer, was beautifully hand calligraphed. Because I had dropped out and didn’t have to take the normal classes, I decided to take a calligraphy class to learn how to do this. I learned about serif and san serif typefaces, about varying the amount of space between different letter combinations, about what makes great typography great. It was beautiful, historical, artistically subtle in a way that science can’t capture, and I found it fascinating.

None of this had even a hope of any practical application in my life. But ten years later, when we were designing the first Macintosh computer, it all came back to me. And we designed it all into the Mac. It was the first computer with beautiful typography. If I had never dropped in on that single course in college, the Mac would have never had multiple typefaces or proportionally spaced fonts. And since Windows just copied the Mac, its likely that no personal computer would have them. If I had never dropped out, I would have never dropped in on this calligraphy class, and personal computers might not have the wonderful typography that they do. Of course it was impossible to connect the dots looking forward when I was in college. But it was very, very clear looking backwards ten years later.

Again, you can’t connect the dots looking forward; you can only connect them looking backwards. So you have to trust that the dots will somehow connect in your future. You have to trust in something – your gut, destiny, life, karma, whatever. This approach has never let me down, and it has made all the difference in my life.

My second story is about love and loss.

I was lucky I found what I loved to do early in life. Woz and I started Apple in my parents garage when I was 20. We worked hard, and in 10 years Apple had grown from just the two of us in a garage into a $2 billion company with over 4000 employees. We had just released our finest creation – the Macintosh – a year earlier, and I had just turned 30. And then I got fired. How can you get fired from a company you started? Well, as Apple grew we hired someone who I thought was very talented to run the company with me, and for the first year or so things went well. But then our visions of the future began to diverge and eventually we had a falling out. When we did, our Board of Directors sided with him. So at 30 I was out. And very publicly out. What had been the focus of my entire adult life was gone, and it was devastating.

I really didn’t know what to do for a few months. I felt that I had let the previous generation of entrepreneurs down – that I had dropped the baton as it was being passed to me. I met with David Packard and Bob Noyce and tried to apologize for screwing up so badly. I was a very public failure, and I even thought about running away from the valley. But something slowly began to dawn on me I still loved what I did. The turn of events at Apple had not changed that one bit. I had been rejected, but I was still in love. And so I decided to start over.

I didn’t see it then, but it turned out that getting fired from Apple was the best thing that could have ever happened to me. The heaviness of being successful was replaced by the lightness of being a beginner again, less sure about everything. It freed me to enter one of the most creative periods of my life.

During the next five years, I started a company named NeXT, another company named Pixar, and fell in love with an amazing woman who would become my wife. Pixar went on to create the worlds first computer animated feature film, Toy Story, and is now the most successful animation studio in the world. In a remarkable turn of events, Apple bought NeXT, I retuned to Apple, and the technology we developed at NeXT is at the heart of Apple’s current renaissance. And Laurene and I have a wonderful family together.

I’m pretty sure none of this would have happened if I hadn’t been fired from Apple. It was awful tasting medicine, but I guess the patient needed it. Sometimes life hits you in the head with a brick. Don’t lose faith. I’m convinced that the only thing that kept me going was that I loved what I did. You’ve got to find what you love. And that is as true for your work as it is for your lovers. Your work is going to fill a large part of your life, and the only way to be truly satisfied is to do what you believe is great work. And the only way to do great work is to love what you do. If you haven’t found it yet, keep looking. Don’t settle. As with all matters of the heart, you’ll know when you find it. And, like any great relationship, it just gets better and better as the years roll on. So keep looking until you find it. Don’t settle.

My third story is about death.

When I was 17, I read a quote that went something like: “If you live each day as if it was your last, someday you’ll most certainly be right.” It made an impression on me, and since then, for the past 33 years, I have looked in the mirror every morning and asked myself: “If today were the last day of my life, would I want to do what I am about to do today?” And whenever the answer has been “No” for too many days in a row, I know I need to change something.

Remembering that I’ll be dead soon is the most important tool I’ve ever encountered to help me make the big choices in life. Because almost everything all external expectations, all pride, all fear of embarrassment or failure – these things just fall away in the face of death, leaving only what is truly important. Remembering that you are going to die is the best way I know to avoid the trap of thinking you have something to lose. You are already naked. There is no reason not to follow your heart.

About a year ago I was diagnosed with cancer. I had a scan at 7:30 in the morning, and it clearly showed a tumor on my pancreas. I didn’t even know what a pancreas was. The doctors told me this was almost certainly a type of cancer that is incurable, and that I should expect to live no longer than three to six months. My doctor advised me to go home and get my affairs in order, which is doctor’s code for prepare to die. It means to try to tell your kids everything you thought you’d have the next 10 years to tell them in just a few months. It means to make sure everything is buttoned up so that it will be as easy as possible for your family. It means to say your goodbyes.

I lived with that diagnosis all day. Later that evening I had a biopsy, where they stuck an endoscope down my throat, through my stomach and into my intestines, put a needle into my pancreas and got a few cells from the tumor. I was sedated, but my wife, who was there, told me that when they viewed the cells under a microscope the doctors started crying because it turned out to be a very rare form of pancreatic cancer that is curable with surgery. I had the surgery and I’m fine now.

This was the closest I’ve been to facing death, and I hope its the closest I get for a few more decades. Having lived through it, I can now say this to you with a bit more certainty than when death was a useful but purely intellectual concept:

No one wants to die. Even people who want to go to heaven don’t want to die to get there. And yet death is the destination we all share. No one has ever escaped it. And that is as it should be, because Death is very likely the single best invention of Life. It is Life’s change agent. It clears out the old to make way for the new. Right now the new is you, but someday not too long from now, you will gradually become the old and be cleared away. Sorry to be so dramatic, but it is quite true.

Your time is limited, so don’t waste it living someone else’s life. Don’t be trapped by dogma – which is living with the results of other people’s thinking. Don’t let the noise of other’s opinions drown out your own inner voice. And most important, have the courage to follow your heart and intuition. They somehow already know what you truly want to become. Everything else is secondary.

When I was young, there was an amazing publication called The Whole Earth Catalog, which was one of the bibles of my generation. It was created by a fellow named Stewart Brand not far from here in Menlo Park, and he brought it to life with his poetic touch. This was in the late 1960’s, before personal computers and desktop publishing, so it was all made with typewriters, scissors, and polaroid cameras. It was sort of like Google in paperback form, 35 years before Google came along: it was idealistic, and overflowing with neat tools and great notions.

Stewart and his team put out several issues of The Whole Earth Catalog, and then when it had run its course, they put out a final issue. It was the mid-1970s, and I was your age. On the back cover of their final issue was a photograph of an early morning country road, the kind you might find yourself hitchhiking on if you were so adventurous. Beneath it were the words: “Stay Hungry. Stay Foolish.” It was their farewell message as they signed off. Stay Hungry. Stay Foolish. And I have always wished that for myself. And now, as you graduate to begin anew, I wish that for you.

Stay Hungry. Stay Foolish.

Thank you all very much.

Steve Jobs, CEO Apple Computer

本文链接

How can I use Fiddler to debug BizTalk messages?

2011-01-27T06:02:00Z

When using HTTP, SOAP or WCF send ports it can be incredibly useful to view the content of messages that are sent on the wire. This allows you to inspect the headers (SOAP or HTTP). Fiddler is a simple but fantastic tool to allow you to do this.

By default, Fiddler will not trace any messages sent to endpoints by BizTalk as it does not use WinInet. However, BizTalk send ports can be configured to use a proxy allowing Fiddler to intercept them. On the Send Port tick the Use Proxy checkbox and set the Server to 127.0.0.1 and the port to 8888. For dynamic ports, set the following properties (as applicable to the adapter being used)

// Debug via fiddler
msgSendRequest(SOAP.UseProxy) = true;
msgSendRequest(SOAP.ProxyAddress) = "127.0.0.1";
msgSendRequest(SOAP.ProxyPort) = 8888;

Note that this needs to be removed when Fiddler is not running since traffic directed to the proxy will not be received by anything.

// Set Fidder as proxy for .NET application

<system.net>
<defaultProxy> <proxy usesystemdefault="False" bypassonlocal="True"
proxyaddress="http://127.0.0.1:8888"/> </defaultProxy>
</system.net>

本文链接

How to clean up BizTalk Message Box

2010-12-09T07:49:00Z

It is usually a very important task to clean up a BizTalk mseeage box during stress testing with large amount of messages. Below are the steps to clean up the message box in order to prepare for the new test.

1. Stop all BizTalk services

2. Type “iisreset” at command line to recycle IIS service

3. Execute the stored procedure “bts_CleanupMsgbox” on your message box database

4. Execute the stroed procedure “bts_PurgeSubscriptions” on your message box database

(if the above stored procedures can't be found, go to your BizTalk installation directory, under “Schema” folder, you can find all original scripts of these stored procedures)

5. Clean up the message box log by running the backup statement similar to below

backup log msgBoxDb to disk = “yourbackupdirectory\yourbackupfile.bak' with init, stats = 5

6. Restart BizTalk services

本文链接

男子英文名大全，来历、释义

2010-11-10T07:56:00Z

AARON
(希伯来)启发的意思，AARON被描绘为不高但英俊的男人，诚实刻苦具有责任感，是个有效率个性沉靜的领导者。

ABEL
(希伯来)"呼吸"的意思，为ABELARD的简写，大部份的人认为ABEL是高大，强壮的运动员，能干，独立，又聪明。有些人则认为ABEL是瘦小，温顺的男孩。

ABRAHAM
原为希伯来文，意为"民族之父"。后来，它演变成"物之父"的意思。大多万数人將ABRAHAM形容为高大壮硕留着胡子的领袖，诚实，庄严，聪明，像亚伯拉翰林肯总统一样

ADAM
(希伯来)，红土制造的意思。据说上帝用红土造人，而亚当是他造出的第一个人。 ADAM被形容是高大，黝黑，英俊，肌肉强健的男人，沉稳，聪明。

ADRIAN
(拉丁文)黑色的意思。人们将ADRIAN描绘为迷人，阴柔的男子，敏感，体贴，可爱，富有。

ALVA
希伯来名，给人的感觉是很崇高、庄严的，圣经上写着ALVA 是一个地名和种族名字。

ALEX
为ALEXａｎｄER的简写，人们认为ALEX是身强体健有着希腊血统的男子，聪明，和善，令人喜爱。

ALAN
据传，英国有一位诗人，叫Alawn(阿伦)，很近似于Alan，它的意思，但后来，这个名字常形为Eilian、Allan、Ailin、A＇lon等等。Alan的发音近似于撒格逊语Aylwyn或Alwyn(熟悉的朋友)的意思)。所以它在英国很为人所欢迎。

ALBERT
(老式英语)崇高，聪明之意。ALBERT引人联想起三种形象；肥胖、笨重、缓慢，如Fat Albert；聪明，行为古怪，如Albert Einstein：或是正式， ALFRED(古式英语)，睿智的参謀\。ALFRED给人两种截然不同的印象：一种是超重的智者，所谓智者就是有智慧的老人家，行事谨慎，另一种是文弱的书呆子。

Andy
为ANDREW的简写，ANDREW在希腊文裡形容有男子气概、雄壮、勇敢。
Andy被人形容为高高的，金发的，童心未泯的普通男子，快乐，随和老实憨厚。

ANGUS
唯一的选择。ANGUS被视作行为怪异，惹麻烦的傻瓜。

ANTHONY
(拉丁)无价的意思，人们认为ANTHONY是高壮黝黑的意大利男人，聪明强壮并坚忍。

ARTHUR
(凯尔特语)"贵族"，(威尔斯)英雄。Arthur有两个不同的意思：一生充满故事喜欢受注目的有趣老人;或是沉靜，与众不同，信守承诺的智者。

AUSTIN
同August，Augustine.AUSTIN被视为聪明，坦诚有礼的大男孩--或者是恃才傲物的富家公子。

BEN
(希伯来)儿子的意思；所有BEN开头名字的简写。Ben被描述为高大，强壮的黑发男子，沉靜、可爱，随和，温柔。

BENSON
(希伯来英文)"Son of Benjamin"班杰明的儿子。感谢电视上Benson Dubois，给人的印象，Benson被形容是机智的黑人管家，聪明，体贴又有趣。

BRANT
古德语，意为妖精。这里所谓妖精，可不是你我心想的贬义词，而是古代德国人对神仙的一般称呼。

BRENT
代表山顶或者避暑胜地。

BRIAN
(爱尔兰语)"力量，美德"，大部份人把Brian看做是爱尔兰男子，聪明，喜欢运动，并擅于社交。有些人则认为Brian是无聊喜欢黏着妈妈的孩子。

BRUCE
来自一个地名Bruis或Braose，它是法国瑟堡(Cherbourg)附近的村庄。据说，村里有一个庄主，取名叫Bruis，当诺尔曼人征服英国时，他们的子孙征服者来到英国，并把这姓名也传入英国。后来，苏格兰出现了一位民族英雄，叫罗伯特·布鲁斯，据说就是由法轩去的布鲁斯家族的后代。

CARL
(老式德语）”农人”同CHARLES。大部份的人认为CARL是个直率的人--照顾人，有礼的紳士，聪明稳重又沉靜。而有些对CARL印象不那么好的人则认为，他是个自以为是而且脾气暴躁的人。

CARY,
Carey(威尔斯)"来自城堡的"，(同Kerry)人们认为Cary是个适合电影明星的名字，温和，友善，无忧无虑的人，有些人则认为这个名字听起来相当女性化。

CASPAR
人们对Caspar有两种印象。友善，害羞乐于助人的，就像鬼马小精灵一样。或是年长,有着忠实信仰，就像圣经里Caspar一样. CHARLES(古德文)有男人气概，强壮。CHARLES不是被看做辛勤，忠实的朋友与领导者就是被认做是聪明，自大的吹毛求疵者。

CHENEY
采尼，法语意为『橡樹林的人』。 CHRIS为CHRISTIAN,CHRISTOPHER的简写。CHRIS给人的印象是外表清爽，标致的美国男孩，聪明，可爱又有趣。

COLIN
(爱尔兰迦略克)"孩子"的意思；同NICHOLAS人们将COLIN描绘为富有，金发的调情者，白天是聪明学有专精的人，夜晚是个迷人的花花公子。

COSMO
希腊字，意为『宇宙』或者『秩序井然』。此名常见于苏格兰人。

DANIEL
(希伯来)"上帝为我们的裁決者".Daniel被形容为英俊强壮的美国童子军，喜好运动勇敢，友善，值得信赖，教养良好，聪明且随和的人。 DARRYL(古英语)意为『亲爱的』。

DEREK
(老式德语)"统治者"的意思。DEREK5被视为高壮，英俊，有男子气慨的运动员，个性为强悍，沉靜，个性害羞。

DOUGLAS
(苏格兰语)"从深水而来"。人们說Douglas是个强壮英俊的男子，不是聪明，敏感安靜的类型，就是勇敢，外向常招惹一堆麻烦的人。

DAVID
(希伯来）挚爱的意思。人们形容DAVID是强壮，英俊，聪明的男人善良，幽默又独立。

DENNY
所有以DEN开头的名字的简称，DENNY这个名字让人聊想到课堂上的笑蛋-爱玩友善极度幽默的年轻男孩，脑袋却不太灵光。

EDGAR
(老式英语)"幸运的战士"。原英格鲁萨克逊语为Eadgar。Ead-这个前缀词表示『富有』,『幸福』。

英国历史上，有一位人人皆知的国王Edgar the Peaceful(安详的埃德加)，创建了英国的海军部队，並联合了八个小国王，使英国国力有所增强。十九世世美国诗人兼小说家阿兰·波(Edgar Allan Poe)就是叫Edgar，昵称Ed。

EDWARD
(古英语)，幸福的保护人。人们认EDWARD这名字非常适合拘谨的书虫，衣冠楚楚的作家或生意人。

EDWIN
(老式英语)"富有的朋友"人们将EDWIN描绘为年长足智多谋的人。但对某些人来讲，EDWIN也有其阴森邪恶的一面。

ELLIOTT
是个时髦的英文名字，源于Elijah。Elliott这个名字给人两种感觉，一是吸引人自视颇高的专业人士，聪明有主见。另一则是四眼田鸡，做事一板一眼的书呆子。

ELVIS
(老式挪斯语)"全能的"同Elwin。Elvis Presley是这个名字的代表人物。人们将Elvis描绘为英俊大方，唱蓝调的南方摇滚巨星 EVAN(威尔斯)"年轻的战士"，JOHN的威尔斯型式。人们形容Evan是文质彬彬的年轻人有着男孩般俊俏面容，聪明的能够完成医学院的学业，才气纵横的足够出书。

ERIC
(挪威)永远的領导者，永远的力量，也是FREDERICK的简称。ERIC被敘述为受欢迎的斯甘地拉维亚人有自信，聪明而且心地善良。

FRANCIS
(拉丁)法国人。FRANCIS这个名字令人联想到稳重的学者或是极度依赖宗教缺乏自信心的人。 FRANK 是FRANCIS,FRANKLIN的简称，人们对FRANK有两种截然不同的印象:辛勤工作的年长男人，独立，友善，并且温柔。不然就是又高又壮的蓝領阶级，懶惰，不受欢迎，又粗心。

FRED
所有含"FRED"名字的简称。FRED被形容为善良，风趣。人们口中的FRED不是矮小，肥胖，笨重那型就是优雅的舞者，如Fred Astaire。

GABY
为Gabriel的昵称，原为希伯来文，意为『上帝的人』。据<圣经>说，天使Gabriel是上帝派来的使者，由他来宣布约翰和耶稣的出生。

GARFIELD
(老式英语)战场之意。很多人都认为GARFIELD就像那只卡通猫一样-肥肥，爱惹麻烦的毛球。其他的人则认为GARFIELD具有领袖的特质-精明，世故，又乏味。

GARY
"先锋"的意思。是Gerald的简称。人们认为Gary是长长得高高壮壮的普通男人，平易近人，和善又有趣。

GAVIN
古德语，意为"白鹰"或"战鹰"。在古威尔士语中，Gawain或Gawen是『小鹰』的意思。『鹰』一直成为古代德国、英国等国家人民崇奉的对象。他们把『鹰』看做『战门』的象徵，是他们心目中的战友。 GIBSON古德语，意为"光明磊落的誓约"。据说，此名表达家长们希望自己的子女继承其祖先财物及传统的愿望。

GINO
为Ambrogino,:Luigino。人们口中的Gino是矮小，黝黑，满身肌肉的意大利人，友善，活力充沛，而且风趣。

GLEN
(爱尔兰迦略克)"山谷"的意思。为GLENDON的简称。GLEN不是被看做善良，单纯，踏实的中阶男子就是勇敢，聪明有创造力的富家子弟。 HARRISONHARRISON (古英语)，亨利之子。HARRISON被形容为英俊，富有的男子，优雅，傲慢或是敏感脾气温和的人。

HUGOHUGH
的拉丁型式。大部份人眼中的HUGO是圆润的男子(有点胖的)，个性温和，独具特色，有时间观念。

HUNK
大个儿，大块头。在人们印象中HUNK是个辛勤工作，心思单纯，自动自发的年轻人且活泼外向。

HOWARD
(老式英语)看守人。Howard形容的不是乏味的中等阶级就是富有掌权之人。 HENRY(老式德语)庄园的领主。HENRY这个名字给人数种不同的看法。懦弱的四眼书虫，野心勃勃，独立自主的专业人士，或是强壮，随和的家夫。

IGNATIVS
(拉丁)意为，"如火如荼的"，其变形为IGNACE、IGNATZ。

IVAN
男子名，John的俄语形式。大部份人认为Ivan是勇敢的俄国男子，强悍，冷酷，而且霸道。 ISAAC(希伯來)来"他笑了"的意思。人们认为ISAAC是聪明体贴的学者型男人，通常不是犹太人就是黑人。

JACK
同JOHN,JACOB;是JACKSON的简称，大部份的人认为Jack是个具威望力的人-体魄健壮，阳刚，强壮，自负，聪明。也有人认为Jack可爱，有趣喜欢追求快乐的家伙。

JAMES
为JACOB的英文形式，JAMES被描绘为大块头，强壮的英俊男人，聪明，严谨，诚实个性依赖。有些人则认为JAMES是粗鲁，自负的贵族。

JASON
被认做可爱，喜好运动的金发男孩，但人们却对Jason的人格有争议。他可能是主观，风趣受欢迎，固执，不受束缚，调皮，或沉静，害羞，常自省的人。 JEFFERYJEFFERY被形容为孩子气，黑发，俊朗的男子。有些人则说JEFFERY是聪明的万事通，有钱又自大的小子，还有人说他是个中等男子，可靠，迟钝又单调。

JEROME
(拉丁)圣洁的名字，在人们印象中，Jerome是个传统的名字，它让人联想到的是有趣，聪明，又体贴的男孩。

JERRY
是GERALD，JEREMIAH，JEROME的简称，大部份的人认为Jerry是高挑，友善，好玩性格极佳的人。有的人则认为Jerry是个喜欢帶着金链子的大块头。

JESSE
(希伯来)"上帝存在"。JESSE给人支配者的印象--一个坚韧，狂放不拘的不法之徒，可说是个坏胚子。

JIM
James的简称，JIM被认为是好看运动员般的金发男人，友善，安靜静的平凡男人。

JIMMY
JAMES的简称。JIMMY不是被描绘为友善单纯的男孩就是邻家的大个子。

JOE
JOSEPH的简称。JOE被看做一般的美国男孩-强壮，英俊的男子，体贴容易相处。

JOHNNY
同JOHN。JOHNNY被看做黑发，高壮，稚气未脫的美国男孩，通常不是安静赖着妈妈的男孩就是静不下来的捣蛋鬼。 JOHN (希伯来)"上帝是慈悲的"。John，一个带着圣经浓厚色彩的名字，让人联想到清爽聪明的男子，个性坚强独立。 JOSHUA (希伯来）意为获得上帝帮助的人。JOSHUA被视作英俊的男子，羞涩，聪明，独立，忠实的信徒。 JUSTIN (拉丁）"品格端正"。Justin被形容作可爱，棕发，爱玩，稚气未脫的男子，喜欢钓鱼及溜狗。人们说Justin可能成为富有的专业人士，公正，受人敬重，可靠的公民。

KEN
是KEN结尾的字的简称，KEN被描繪绘成高挑英俊的金发男人，受欢迎，又风趣。

KENNY
是Kenneth的简称，人们把kenny当做是一般的美国男孩，年轻的足球英雄而且心地善良，成年后也是个肯为家庭投注心力的好男人。

KEVIN
(爱尔兰)温和，可爱的，KEVIN被描绘为年轻喜好运动的美国男孩，心地好，有点固執。

LANCE
(老式德语)"大地"，Lance被形容为爱情小说中的英雄人物--英俊，有男子气慨，富有，也是厉害的花花公子。

LARRY
LAWRENCE的简称。大部份人认为LARRY是随和友善的-所到之处无不充满笑声。有人则认为LARRY是吃人不吐骨头的奸商。

LEE
(古英语)来自牧场之人。LEE这个名字结合了两大形象：一是强壮，肌肉强健，充满自信的牛仔或是文静，保守的世故者。

LEO
(拉丁)"狮子"，为Leander，Leonard，Leopold的简称。大部份人认为Leo是强壮且温和的。他被形容为热情的背叛者，总以一付艺术家或捍卫和平的面貌出現。

LORI
源为拉丁文Laurentium，是从Laurentium(荣誉之城)或(月桂樹之域)变來的。虽然，这个字的词根『Laurel』『月桂』是很吸引人的。因为在古代，『月桂』是作为胜利和『荣誉』的象徵。同Lauren、Laurent、Loren、Lorin、Larry、Laurence、Lorry。

LUKE
"路加尼亚的人"同LUCIUS LUKE不是被看做强壮，结实，忠实實，愚蠢，就是风趣，友善，吵闹的人。 MARCUS同MARK，MARCUS给人的印象是高大强壮英俊的运动员或单纯乏味的生意人。

MARK
(拉丁)好战的意思。好战的?一点也不会!人们說Mark是爱好运动，非常英俊的男人，风趣爱好自由，而且是个细心的朋友。

MARS
出自拉丁文，为古罗马『战神』之名。同MARKS,MARTIN,MARCY. MICHAEL(希伯来)像主的人，MICHAEL被描绘为强壮，英俊的男人，聪明成功的刻苦工作者，随和，快乐的居家男人。

NEIL，
Neal(爱尔兰迦略克)"冠军"之意。大部份人把Neil看做陪明有才能的人，成就极高个性温和。有人则觉得Neil是固执的人。

NICHOLAS
(希腊)"胜利的人"。感谢圣者Nicholas，大部份的人认为Nicholas是可爱，肥胖，快乐，大方的。有些人则认为Nicholas是个被宠坏难以捉摸的小恶魔。

OLIVER
(拉丁)，"橄榄树"。(斯堪地拉维亚)"温和亲爱的"。OLIVER给人好几种印象。脏兮兮無无忧虑的乡下小孩；好学用功的书虫；热心奉献的人；或者愚蠢有趣的漫书人物。

OSCAR
(斯堪地那维亚)"神圣的持枪者"。人们心目中的Oscar不是风趣，懶散，无忧无虑的冒失鬼就是讨厌固执，经常抱怨的人。

PAUL
(拉丁)"小"的意思。大部份人认为PAUL是庄严，稳重坚定的人，但有人认为他有魅力，创造力又和善。 PATRICK(拉丁名)，意为『高贵的』、『贵族的』。在爱尔兰和苏格兰，此名较为流行。

PETER
(希腊)岩石。人们认PETER是个不做作，诚实，开放的人。有些人则认为PETER是个充满野心和爆发力的。

PHILIP
Philip这个名字给人几种不同的印象：一个有朝气的军官；自大的王子；有钱的商人，聪明內向的人。

PHOEBE
聪明，闪亮。理所当然人们心中的Phoebe是个性爽朗，带给大家欢笑的开心男孩。

Randy
为Randall,Randolph的简称。Randy被看做高瘦，讨喜的男孩，若不是安靜静，聪明努力的人不然就是擅长运动，爱玩幽默的乡村男孩。

REX
(拉丁)帝王的意思。谢谢HENARY HIGGINS做的REX HARRISON的雕像，人们对REX的印象是强壮庄严相当有自我风格的人，但別人眼中却稍嫌莽撞。有些人却认为REX是个独来独往的死硬派-有可能是飞行员或小偷。REX也是个适合小狗的名字。(当然也适合恐龙!)

RICHARD
RICHARD在古德文中意谓着"掌理大权的统治者"，这个名字给人两种形象；一个是英俊强壮，擅长运动的美国男孩：另一个是诚实，严肃，但敬来乐群的男人。

RICHIE
原为盎格鲁撒克逊语Ricehard，意为『统治得很稳固』。在古德语中，也有相应的名字Ricohard，意为『严厉的统治』。同Rick、Ricky、Ritchie。

ROBERT
(老式英语)"光辉和着名的"。ROBERT给人两种不同的印象：英俊，强壮的运动员，风趣外向；粗壮的普通人，安静保守。

ROBINSON
同ROBERT的；简称为ROBIN。ROBINSON给人两种不同的印象：一种是安靜静勤奋的工作者或是活泼外放的喜剧演员如Robin Williams.

ROCK
(老式英语)源于石头，为Rochester,Rockwell的简称。Rock用来形容头脑四肢发达的人-大块头，满是肌肉的运动员，强壮，驽钝，就像石头一样硬。

ROGER
(古德语)着名的槍枪手。ROGER被视作英俊的男子，友善，讨人喜欢充满乐趣。

RYAN
(爱尔兰)"小国王"。 Ryan被形容为强壮，活跃的男子，长得很英俊却很害羞。

SAM
为SAMSON，SAMUEL的简称。人们印象中的SAM是个强壮的，温和，忠实脚踏实地的人，而且是可以交心的朋友。代表人物是人人皆知的UNCLE SAM

SAMUEL
(希伯來文)，schama(意为『听』)和El(意为『上帝』)连成的。其完整意思为"被上帝听到的人"。这和圣经中的传说有关。圣经说预言家Samuel的母亲把他的降生看作是上帝对她的祷告的报。

SEAN
为John的爱尔兰形式。

SHAWN
被形容为阴晴不定独來独往的人如西恩潘，或是英挺，刺激，上流社会的英国人，如史恩康納萊。 SHAWN为John,Sean的爱尔兰形式。 SHAWN被形容为英俊的年轻人，活泼，受欢迎，温和。

SIDNEY
(法文)由圣者丹尼士衍生出。SIDNEY这个名字令人联想到学有专长的专家英俊又善良。虽然有人认为SIDNEY是反传统且不按牌理出牌之人。

SIMON
希伯来文，意为听者。SIMON被视作强壮魁梧的男子，若非有着安静样的个性就是聪明而富创造力。

SOLOMON
希伯来文，意为平静的小人。令人联想到矮小，禿头犹太教师或先知，强壮温和，又睿智。

SPARK
(美国)"闪闪发光"，SPARK被人们描绘为充满活力的人-反反灵敏，生气蓬勃并为人们帶来快东的人。

SPENCER
来自法语，意为仓库保管人或粮食分配者。人们对他的印象直接来自SPENCER TRACY。人们想像中的SPENCER是灰发的年长男子，极为幽默。

SPIKE
又长又重的钉子。SPIKE被描绘为独立强悍的街头老大，可能是莽夫或拳击手。有些人则以为这个名字很适合狗；我就认识一只叫SPIKE的狗。

STANLEY
(古式英文)来自牧草地。STANLEY这个名字给人两种印象：安静，年长蓝领劳工或是瘦骨如柴的怪人。

STEVEN
同Stephen。人们心目中的Steven是高壮，英俊的男子，沉静，斯文有礼，性格和善。

STUART
原为苏格兰语，看管家畜的人，有时可解释成看管物业的人。给人两种印象：雄壮威武的高手或是聪明教养良好的绅士。

TERRENCE
(拉丁语)"光滑"，TERENCE这个名字让人们联想到活泼，高挑的黑人或是黑发，温和的男孩。

TERRY
为TERENCE的简写，TERRY是个喜欢追求乐趣的男孩，喜欢运动，善良，而且充满欢笑。

TIMOTHY
原希腊语TIMOTHEOS，意为光荣的上帝。大部份人将提摩西想成是羞涩甜美的可爱小孩。

TOMMY
为THOMAS的简写，TOMMY给人邻家男孩的感觉，长相清秀，可爱的金发小男孩。

TOM
为THOMAS的简写，TOM可说是一般典型美国人的代表，无所不在，自信，讨人喜欢而且做人实在。

THOMAS
古亚拉姆语，意为双胞胎。THOMAS被认为是聪明，可靠，教养良好有机智的男子。

TONY
为ANTHONY的简写。人们眼中的TONY是善良，强壮的运动员，冷静能自理的男孩。

TYLER
古英语，瓦匠。TYLER给人两种印像：富有自大或者肥硕善良无忧无虑的生意人。

VAN
(荷兰)"贵族后裔"，为许多荷兰名字的姓。 VERNVernon的简写。Vern有着两个差异颇頗大的意义：呆板，单调的怪老头或英俊黑发的年轻男子，勇敢，有着橫扫千军的气魄。

VINCENT
(拉丁语)"征服"。大部份的人认为Vincent是沉靜，如艺术品般的男人。稳重善解人意。然而有人认为Vincent是邪恶的罪人。

WARREN
(古德语)"保卫者"，WARREN这个名字给人两种印象：英俊诡诈，老是与麻烦脫不了关系的人；或是努力工作的会计，聪明但乏味。

WESLEY
(老式英语）来自西方草原。WESLEY这个名字给人两种印象：一种是被宠坏，甜美自大的娘娘腔。另一种则是年轻有着顽皮个性的专业人士。

本文链接

Install or Uninstall a Windows Service

2010-11-09T08:24:00Z

Install

cd d:\cps\bin\backend
installUtil Batch.Monitor.Service.exe

Uninstall

cd d:\cps\bin\backend

installUtil -u Batch.Monitor.Service.exe

本文链接