در حال ارتقا برنامه شرکت از نسخه ۲۰۰۵ به ۲۰۰۸ ، مشکلاتی پیش آمد که بعضی از آنها راقبلا  در اینجا آوردم. اما بعضی مکلات بصورت پنهان باقی مانده بود و زیاد خودنمایی نمی کرد، چون اصلا کسی به سمت آن هم نرفته بود . مثلا برنامه ما بدون هیچ مشکلی در IIS 6.0 اجرا میشد و پس از ارتقای نسخه هم هیچ مشکلی پیش نیامد. به تازگی روی یکی از سیستمهای شرکت ویندوز ویستا را به جهت تست یکسری موارد ارزیابی نشده نصب کردیم و خواستیم تا برنامه شرکت را روی IIS 7.0 نصب و اجرا کنیم.

خود من به شخصه قبلا خیلی کم از IIS استفاده کردم و در راهبری IIS قوی نیستم، اما در شرکت افرادی هستند که خیلی خوب روی IIS کار کرده اند به همین دلیل هیچ وقت فکر نمی کردیم که به مشکلی هم بر بخوریم . اولین باری که من برنامه را روی IIS 7.0 ( که روی ویستا هست ) نصب کردم اصلا برنامه اجرا نشد و بخاطر ضعف دانشی که از IIS داشتم مشکل را با کسی مطرح نکردم و خواستم تا مشکل را با یک جستجوی ساده روی اینترنت حل کنم. بخاطر کمبود وقتت بررسی مشکل به فراموشی سپرده شد تا اینکه بنا به دلایلی محبور به اجرای برنامه روی IIS 7.0 شدیم.

تا پیش از این (‌نسخه II 7.0 به قبل ) همه وب سایت ها و برنامه ها در یک WebSite مادر با نام Default Web Site نصب و اجرا میشد و این محدودیت های بسیاری را ایجاد می کرد ( مثلا شما نمی توانید در آن واحد بیش از یک اینستنس را اجرا کنید و مشکلات مشابه ) در IIS 7.0 این مشلات برطرف شده و شما می توانید تعداد متعددی از وب سایت های وادر را داشته باشید و وب سایت های مشتریان را نسبت به نوع یا میزان دسترسی و یا چه و چه در وب سایت های مختلف قرار بدهید .

پنجره ایجاد یک WebApplication در IIS 7.0

یکی از مزایای IIS 7.0 استفاده از یک Application Pool یکپارچه است به این مفهوم که برنامه یا وب سایت نصب شده بصورت یکپارچه از این Application Pool استفاده می کند . با این که این خاصیت مزیت بزرگی محسوب می شود بیشتر برنامه ها و یا وب سایت هایی که در Visual Studio 2005 ایجاد شده اند نمی توانند بصورت یکپارچه از Application Pool استفاده کنند . برای همین باید از Application Pool قدیمی که در نسخه IIS 6.0 به قبل بود استفاده کنند . که بصورت کاملا جداگانه از خود IIS به برنامه دسترسی داشت .

به همین دلیل بیشتر برنامه هایی که ما در شرکت تولید کرده بودیم روی IIS 7.0 اجرا نمیشد . برای حل این مشکل و اجرای صحیح برنامه ها و وب سایت هایی که در نسخه های قبلی IIS بخوبی اجرا می‌شدند باید Application Pool دیگری برای وب سایت استفاده کنید . برای رفع این مشکل بصورت زیر عمل کنید .

     ۱-     بر روی Web Site مادری که می خواهید برنامه تان در آن اجرا شود کلیک راست کرده و گزینه Add Application را انتخاب کنید . ( مثلا روی Default Web Site )

     ۲-     از پنجره ای که باز می شود یک نام ( Alias ) برای برنامه تان انتخاب کرده و در قسمت روبریی بر روی Select کلیک کنید تا پنجره  Select Application Pool باز شود

     ۳-     بعد از باز شدن این پنجره از منوی پایین افتادنی بر روی Classic .net AppPool کلیک کنید تا انتخاب شود و پس از انتخاب بر روی OK کلیک کنید .

پنجره تغییر Default ApplicationPool به Classic .net ApplicationPool

     ۴-     مسیر برنامه تان را روی هارد مشخص کرده و بر روی OK کلیک کنید .

با اتمام این مراحل اگر مشکل دیگری نداشته باشید برنامه شما باید بصورت صحیح اجرا شود .

Este artigo demonstra de maneira simples e rápida como enviar uma mensagem usando o CDOSYS, modificando o host para envio de e-mail, o remetente, o destinatário e por fim o texto no corpo do e-mail….

Observações:

mail.exemplo.com = Servidor smtp que será usado para envio da mensagem

destino@exemplo.com = Endereço de e-mail que será alcançado pela mensagem

origem@exemplo.com = Endereço de e-mail autorizado pelo servidor SMTP para envio deste mensagem

Subject = Título do E-mail

HTMLBody= Texto que vai no corpo do e-mail

‘—

‘Cria Objetos
Dim objMessage, objConfig
Set objMessage = Server.createObject(“CDO.Message”)
Set objConfig = Server.createObject(“CDO.Configuration”)

‘Cria Configuração
with objConfig.Fields
.Item(“http://schemas.microsoft.com/cdo/configuration/sendusing”) = 2
.Item(“http://schemas.microsoft.com/cdo/configuration/smtpserver”) = “mail.exemplo.com”
.Item(“http://schemas.microsoft.com/cdo/configuration/smtpconnectiontimeout”) = 10
.Update()
End with

‘Envia E-mail
with objMessage
.Configuration = objConfig
.to = “destino@exemplo.com”
.From = “origem@exemplo.com”
.Subject = “E-mail de teste”
.HTMLBody = “E-mail de teste com CDOSYS”
.Send()
End with

‘Destroi objetos
Set objMessage = Nothing
Set objConfig = Nothing

[]´s

RolfBoard

Erro:

Unable to bind to the underlying transport for x.x.x.x. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.

Este erro ocorre normalmente quando uma interface, ou o ip do server em questão foi alterado, prejudicando o controle do bind que gravou em registro este dado e não conseguiu dinâmicamente alterar. Este erro também é comum em casos de 2 aplicações que tentam fazer bind no mesmo serviço, exemplo um Apache com um IIS na mesma máquina.. veja isso é um exemplo…

Para que volte ao normal é necessário forçar o bind usando o httpcfg, uma ferramenta de edição do http.sys, que controla a lista de ip´s permitidos no bind.

• Primeiro execute a remoção do ip ou dos ip´s antigos da máquina com o seguinte comando:

httpcfg delete iplisten -i x.x.x.x, onde “x” é o endereço antigo

• Depois adicione o endereço “0.0.0.0″, significando de qualquer origem para qualquer destino

httpcfg set iplisten -i 0.0.0.0

Após este procedimento, execute os seguintes comandos:

net stop http

net start http

iisreset

Verifique se a porta desejada subiu corretamente através do comando:

netstat -na | findstr 80

[]´s

Rodolfo

]]> http://debasishpramanik.wordpress.com/2008/08/27/setting-aspnet-state-service-on-remote-machine/ Wed, 27 Aug 2008 08:52:39 +0000 debasishpramanik http://debasishpramanik.wordpress.com/2008/08/27/setting-aspnet-state-service-on-remote-machine/

ASP.NET does allow to set the ASP.NET State Service on a separate machine. This is done through the appropriate setting on the web.config file.

But this is not the only change that we need to do we have set the registry settings on the machine where ASP.NET State Service is running.

We need to do change the the following key

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\aspnet_state\Parameters

and change the value of AllowRemoteConnection to 1 instead of 0.

Update: This application will help you track down which applications are using which ports on Windows – very helpful for debugging if the steps below don’t solve your problem, or if IIS is not the only application answering on port 80: http://winnetstat.zapto.org/

Also, if you don’t specifically need all the features of XAMPP, but would like to run PHP/MySQL applications through IIS, give Web Platform Installer a try. Through WPI, you can choose to install PHP directly within IIS (so that IIS can serve both ASP.NET and PHP applications on port 80, for example) and you can also have a ton of applications installed and configured automatically for you, such as Drupal, WordPress, and Moodle (among many others). However, if you are still looking to run XAMPP specifically, or just run an Apache instance along with IIS, check out the instructions below. Thanks for visiting!

Original Post:

Found out the hard way that the default XAMPP install for Windows will attempt to install Apache as a service configured to run on Port 80 (no surprise, and probably good default behavior). But, if you’re like me, and have IIS already installed and running, for whatever reason, you’ll probably want to configure XAMPP to run Apache on a different port.

I initially tried merely modifying the httpd.conf file located (on my system) at C:\xampp\apache\conf, but the service would still not run. So, through a bit of searching on the interwebs, I found out what exactly needs to be changed to allow XAMPP to co-exist with IIS configured to run on Port 80, and Apache (in my case) to run on Port 8080 (and SSL running on Port 4499):

C:\xampp\apache\conf\httpd.conf:

• Search for “Listen 80″, change to “Listen 8080″
• Search for “ServerName localhost:80″, change to “ServerName localhost:8080″

C:\xampp\apache\conf\extra\httpd-ssl.conf

• Search for “Listen 443″, change to “Listen 4499″
• Search for “<VirtualHost _default_:443>”, change to “<VirtualHost _default_:4499>”
• Search for “ServerName localhost:443″, change to “ServerName localhost:4499″

Then, you should be able to start Apache successfully through the XAMPP control panel.

Let me know if this works for you; I’m just starting to mess with XAMPP on Windows (I’ve been using it on Linux for a while).

For the past few years while interacting with developers in the .NET community I have seen that they are very much conversant with language (C#) and ASP.NET features.But very few of them has a clear idea about idea about how IIS works and the ASP.NET Request Pipeline.So in this blog and subsequent blogs I will covering some key aspects of II6.0 and ASP.NET Request processing model.

IIS Web Site

The first important unit of IIS 6.0 Infrastructure is the IIS Web Site.A IIS Web Site is configured to listen to incoming HTTP requests

• Directed to a particular IP address or port number(http://127.0.01:7018 )
• Directed using a specific host header(e.g. http://xyz.com)

By default IIS created an web site named Default Website and configured to listen on port 80.Additional sites can be configured using the IIS Administration tool.

IIS Virtual Directory

Every IIS Website maps to a physical folder in the server.The Default Website maps to C:\Inetpub\wwwroot folder by default.A virtual directory within a site is a container of files and defines a child URL space within the website e.g. If we create a virtual directory called Chat within the website www.xyz.com then it can be accessed as http://www.xyz.com/Sales .We can map this virtual directory to a physical folder named D:\Chat in the server.

IIS Application or Virtual Application

In IIS 6.0 the terms application and virtual directory is bit confusing and is found to be used interchangeably in many tech articles.An application can be considered as a virtual directory with a additional properties like Application Name,Application Root(Starting Point),Application Pool ID.The Web Site by default is associated with an application even if the above mentioned properties are not specfically set.An application should have at least one virtual directory.It can also have more than one virtual directories.e.g The WebSite www.xyz.com can contain a virtual directory as well as application named Chat (www.xyz.com/Chat) and within the application Chat there can be another virtual directory Messages (http://www.xyz.com/Chat/Messages).  This virtual directory may not be an application .

 Application Pool

An application pool is a mechanism to group and isolate a set of web applications hosted by the IIS server.Each web application is assigned to one application pool.Each application pool runs in the different instance of the worker process(w3wp.exe).e.g. there is WebApp A assigned to AppPool AP1 and WebApp B assigned to App Pool AP2 then WebApp A and B runs in two seperate processes executing different instances of w3wp.exe.This ensures better application isolation and protection i.e. failure of any one the applications will not hamper the execution of the other.Application Pool identity is the identity under which the application pool worker process executes.By default this is the network service account.This can be changed and configured using the IIS Admin Tool.The other important configurations include the application pool health monitoring and worker process recycling.The details are provided in IIS documentation http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/f05a7c2b-36b0-4b6e-ac7c-662700081f25.mspx?mfr=true

The installation platform includes Windows Server 2008, TFS 2008, VS 2008, SQL Server 2005 with SP2 and Sharepoint Services 3.0. Windows Server 2008, TFS 2008, VS 2008, SQL Server 2005 were present on one system while the SharePoint Services 3.0 installed on other system such that Team portal for any Team project would be hosted on one system (remote system) and Reports would be published on another (host system). To configure remote system having Sharepoint server you would need to install WSS Extensions on it. You would need to run the TFS Server set up on remote machine and choose the last option (Install WSS Extensions).

TFS setup includes Server setup, TFS Server proxy, TFS Build, Team Explorer (or client setup) and WSS Extensions. For installation on Windows Server 2008 you would need to enable IIS 6.0 compatibility. Go to Server Manager and then Roles. Click add roles and select Web Server (IIS), locate IIS 6.0 from the list and select all the options. Continue and wizard will install IIS 6.0 compatibility components. I will write another post explaininig installation issues we faced and there solutions. There is one really cool feature of this setup which saves a lot of time during installation failure scenario. Before installing the components it looks for potential installation risks and compatibily check. It gives complete error message alerting you about what might cause an installation failure so that it can fixed before proceeding. One the check passes you are sure that installation success ratio would be very high.

TFS or Team Foundation Server serves as an integrated solution for a product development team including Bug Management System, Build Management System, Source Code Control and a Common Team Portal for Overall project management.

Once the TFS Server is setup and a team project has been created then you would need to create a solution\project and add that to source control.

Team needs to install TFS Client which comes as part of TFS Setup (just install Team Explorer which is TFS Client). Once Team Explorer is installed on your system VS will start showing Team Project in new\open project option. Open a Team project by connecting to your TFS Server and then you would be able to see the Team project. For the first time users, you would need to first add TFS Server by clicking Team project and then in the wizard click Add Server. In Visual Studio IDE on the right end you will now see Team Explorer window along with Solution explorer and other windows.

Go to Team Explorer click on the Team project you are going to work on (You will presented with the Team projects where you have been given access by the Team Project Administrators). You would need to check if you have permision to view team portal and report site (right click team project name and reports folder for this). You should be able to view both of these. Team Site can typically be found at http://[WSS_Server]/Sites/[TeamProject and report site at http://[Report_Server]/Reports/Pages/Folder.aspx?ItemPath=/[Team_Project]. If not, check with project admins for giving you permission in reports server and share point team site both. There are different roles which decide what all you can do on these portals.

Second task would be to add a solution from source control.

1) Check that your Source Control Provider is TFS.
2) If not, then go to Tools -> Options -> Source Control and change current value to TFS on the right pane.
3) Once you have TFS selected as your Source Control provider go to File Menu -> Source Control -> Open from Source Control and then you would be shown the projects in Source Control.
4) Select the one you are going to work on and then select a local directory. All files will be copied to your local directory and then you can open the solution from your local directory. You will be able to see the same in solution explorer.
5) Team explorer will help you with overall project management, your work items and tasks, build requests and check-in controls where as Solution explorer will help you with working on the project or project development.

Please try to play both with Team Explorer and Solution here and see what new options you find with respect to Source Control and Team portal. I have found some issues and scope of improvement regarding source control which I will be mentioning in one of my future blogs. Till then keep testing TFS, Team Explorer, Build, Test support and Source Control

bye for now.
my team @ http://india.rampgroup.com

Erros encontrados no Log de eventos para este problema:

Event Type: Message
Event Source: Active Server Pages
Event Category: None
Event ID: 5
Date: Date
Time: Time
User: N/A
Computer: Computer_Name
Description:
Error: The Template Persistent Cache initialization failed for Application Pool ‘Application_Pool_Name’ because of the following error: Could not create a Disk Cache Sub-directory for the Application Pool. The data may have additional error codes

————-

Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1009
Date: Date
Time: Time
User: N/A
Computer: Computer_Name
Description:
A process serving application pool ‘Application_Pool_Name’ terminated unexpectedly. The process id was ‘5288′. The process exit code was ‘0xffffffff’

——————

Estes erros ocorrem normalmente quando um membro de domínio é promovido para controlador de domínio, durante o processo de instalação as permissões do %systemroot% são reiniciadas e reordenadas .

Para contornar este problema será necessário setar manualmente as permissões dos seguintes diretórios:

• systemroot\Help\IISHelp\Common
• systemroot\System32\Inetsrv\ASP Compiled Templates
• systemroot\IIS Temporary Compressed Files

Da seguinte forma:

%systemroot%\Help\IISHelp

Para este diretório adicione o grupo IIS_WPG, e coloque as seguintes permissões:

- Read and Execute
- List Folder Contents
- Read

%systemroot%\system32\inetsrv

Para este diretório adicione o grupo IIS_WPG, e coloque a seguinte permissão:

- Full Control

%systemroot%

Para este diretório adicione o grupo IIS_WPG, e coloque a seguinte permissão:

- Full Control

%systemroot%\Help\iishelp

Para este diretório adicione o grupo IIS_WPG, e coloque as seguintes permissões:

- Read and Execute
- List Folder Contents
- Read

obs.: Procure evitar a replicação de objetos (herança) durante o processo de configuração a não ser que você tenha certeza do que está fazendo, se não todo o trabalho acima será em vão e outros problemas surgirão em seu Server.

Realizado todos estes passos, realize um restart do seu webserver e verifique nos logs, após navegação do conteúdo, se o problema persiste.

Segue link com um artigo da microsoft contendo informações a respeito de um problema similar.

http://support.microsoft.com/kb/332097/

that’s all…

Rodolfo

‘******************************************************************************************************************************
‘*** Script Name: sendmail.vbs
‘*** Criado e Revisado por Rodolfo Angelino Rodrigues
‘*** Data:  08/04/2008
‘******************************************************************************************************************************

Option Explicit
On Error Resume Next

Dim objSendMail, oArgs, ArgNum
Dim strTo, strFrom, strSubject, strBody

Set oArgs = WScript.Arguments
ArgNum = 0

While ArgNum < oArgs.Count
Select Case LCase(oArgs(ArgNum))
Case “-to”,”-t”:
ArgNum = ArgNum + 1
strTo = oArgs(ArgNum)
Case “-from”,”-f”:
ArgNum = ArgNum + 1
strFrom = oArgs(ArgNum)
Case “-subject”,”-s”:
ArgNum = ArgNum + 1
strSubject = oArgs(ArgNum)
Case “-body”,”-b”:
ArgNum = ArgNum + 1
strBody = oArgs(ArgNum)
Case “-help”,”-?”:
Call DisplayUsage
Case Else:
Call DisplayUsage
End Select
ArgNum = ArgNum + 1
Wend

If oArgs.Count=0 Or strTo=”" Or strFrom=”" Or _
strSubject=”" Or strBody=”" Then
Call DisplayUsage
Else
Set objSendMail = CreateObject(“CDONTS.NewMail”)
objSendMail.From = strFrom
objSendMail.To = strTo
objSendMail.Subject = strSubject
objSendMail.Body = strBody
objSendMail.BodyFormat = 0
objSendMail.MailFormat = 0
objSendMail.Send
Set objSendMail = Nothing
End If

‘******************************************************************************************************************************
‘*** Mostra o uso em linha de comando do script
‘******************************************************************************************************************************
Sub DisplayUsage
WScript.Echo “Usage:”
WScript.Echo “  sendmail -t <to address> -f <from address> -s ” & _
Chr(34) & “<subject>” & Chr(34) & ” -b ” & Chr(34) & _
“<message body>” & Chr(34)
WScript.Echo “  sendmail [-help|-?]“
WScript.Echo “”
WSCript.Quit
End Sub
‘******************************************************************************************************************************

Para habilitar no IIS a função de Reverse DNS, você pode executar a seguinte linha de comando:

C:\inetpub\adminscripts\Adsutil.vbs SET W3SVC/EnableReverseDNS TRUE

obs.: Habilitar esta função irá causar um aumento de consumo dos recursos CPU e BANDA em seu servidor web.

Microsoft JET Database Engine error ‘80004005′

Could not use ”; file already in use.

Este problema pode ocorrer pelas seguintes causas:

1) A conta de usuário internet guest (se default de instalação IUSR_SERVER) não possui permissão de escrita do database, *.mdb

2)  O UNC está incorreto

3) A quota para a conta de internet guest atingiu o seu limite

Para realizar esta tarefa você vai precisar confirmar se possui o script ADSUTIL.VBS, que por default de instalação fica em inetpub\adminscripts, caso não, você possui 2 opções: 1) reinstalar o IIS ou 2) pegar direto no site da Microsoft.

obs.: execute CScript.exe para que o mesmo seja o seu interpretador de linha de comando Default. (CScript.exe //H:CScript)

Para habilitar o Passive port range você pode digitar a seguinte linha de comando:

adsutil.vbs SET MSFTPSVC/PassivePortRange “inicio-fim”

sendo “inicio-fim” o seu range de portas liberadas no firewall local ou remoto de sua DMZ”

Para efetuar consulta basta somente trocar o parâmetro “SET” por “GET” …

[]´s

Rodolfo

1)Abra o IIS MANAGER, depois expanda a view “Default SMTP Virtual server”
2)Clique com o botão direito no painel e selecione New e depois clique em Domain
3)Vai começar o wizard do Smtp
4)Especifiquei o tipo de domínio, clique em Remote, e depois em Next
5)Na caixa Name, digite o nome do domínio (DNS), e depois clique em finish.
6)Clique com o botão direito no domínio criado e selecione properties
7)Selecione a aab General
8)Selecione a caixa Forward all mail to smart host, e depois digite o endeço ip do host que enviará as mensagems. tenha certeza que o endereço ip estará entre colchetes, [10.10.0.1].
9)Agora clique em OK
Realize um teste de envio de mensagens