Welcome to the Calyx Software Message Boards where you can share ideas and solutions with other Calyx users! Calyx personnel including Tech Support, Development, QA, and Business Planning often visit these message boards unofficially to better understand our customers' needs. To submit your suggestions Click Here.
This discussion forum is a service provided by Calyx Software. Calyx Software does not endorse any particular point of view expressed in this forum or any information provided in it. The use of the information provided by other users in this message board is at your own risk.
Calyx Software Message Board
Home      Members   Calendar   Who's On
Welcome Guest ( Login | Register )
      



web.config corrupt?Expand / Collapse
Author
Message
Posted 4/10/2006 11:08:49 AM
Junior Member

Junior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior Member

Group: Forum Members
Last Login: 4/10/2006 9:19:03 PM
Posts: 12, Visits: 28
It appears that my web.config under the services directory. Here it is. Can you help?

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

<configuration>

<configSections>

<sectionGroup name="intesoft">

<section name="aspAccelerator" type="Intesoft.Web.Configuration.ConfigurationSectionHandler, Intesoft.ASPConfiguration, Version=2.0.5000.0, Culture=neutral, PublicKeyToken=75ebecc4fcf8b09f" />

</sectionGroup>

<section name="microsoft.web.services2" type="Microsoft.Web.Services2.Configuration.WebServicesConfiguration, Microsoft.Web.Services2, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />

</configSections>

<appSettings>

<add key="PdsConnectionString" value="workstation id=IFCSERVER;packet size=4096;user id=sa;pwd=*******;data source=IFCSERVER;persist security info=False;initial catalog=Pds" />

<add key="UpgradeMessage" value="" />

<add key="MaxRecordsGetTasks" value="5000" />

<add key="MaxRecordsGetLoanApps" value="50000" />

<add key="DatabaseCommandTimeOut" value="120" />

</appSettings>

<!-- ASPACCELERATOR.NET CONFIGURATION (Comprehensive)

This configuration rule set determines if the client has requested a compressed response by

looking at the Accept-Encoding header or if it can accept it based on the User-Agent string

and other http headers. The settings below are then configured based on the request - refer

to the help for a complete description of what each option does and how it should be used.

setting default description

===================== ======= ===========================================================

compression false whether compression will be applied to the response output

level normal the compression level to use (low, normal or high)

suppression true whether the resposne will be suppressed (if possible)

algorithm deflate the compression algorithm to use (deflate or gzip)

sendPoweredBy true send an "X-Powered-By: ASPAccelerator/3.5" header

sendETag true send the cache header used for suppression

varyBy (empty) http headers to vary the content by (Vary-By http header)

throwLicenseException false whether to raise an error if a valid license is not found

-->

<intesoft>

<aspAccelerator>

<!-- the default settings can be overridden as required. eg. the default compression

level to be used could be changed and suppression disabled:

<set name="level" value="high" />

<set name="suppression" value="false" />

<set name="throwLicenseException" value="true" />

-->

<!-- check for responses that we don't want to compress so we avoid any further content

negotiation and also do not add any Vary-By header (which would affect caching) -->

<choose>

<!-- already compressed images should not benefit much from further compression -->

<when match="image/jpeg|image/gif" context="Response.ContentType">

</when>

<!-- application-specific exceptions should be included here. eg:

<when match="dontcompress\.aspx" context="Request.RawUrl"></when>

<when match="dontsuppress\.aspx" context="Request.RawUrl">

<set name="suppression" value="false" />

</when>

-->

<!-- for all other responses, we will negotiate whether to use compression -->

<otherwise>

<!-- use the HTTP Accept-Encoding header to determine if the client will accept compressed content

and vary the cache by this header so different versions are stored in caches / proxies -->

<use header="Accept-Encoding" />

<add name="varyBy" value="Accept-Encoding" />

<choose>

<!-- if it contains 'deflate' then we can turn on compression and set the algorithm -->

<when match="deflate">

<set name="compression" value="true" />

<set name="algorithm" value="deflate" />

</when>

<!-- if it contains 'gzip' then we can turn on compression and set the algorithm -->

<when match="gzip">

<set name="compression" value="true" />

<set name="algorithm" value="gzip" />

</when>

<!-- neither compression method matched (or the header was absent). Strictly adhering

to the http standard means that the response should not be compressed but many

clients can still accept compressed content if it is sent to them -->

<otherwise>

<!-- if the Accept-Encoding header wasn't sent then the browser may just be running in

HTTP/1.0 mode and so may not expect (or handle) a compressed response (esp. IE).

Unfortunately, we cannot just check the HTTP protocol of the request as it could

have come through a proxy server which has upgraded the request to HTTP/1.1 and

sending compressed content back to the client will produce scrambled text often

because the proxy does not send back the Content-Encoding header to tell the client

that the content is compressed (and the algorithm used)

If the client is running in HTTP/1.1 mode and *did* send the header but it didn't

reach us then it could have been masked by a local firewall that wants to filter

the content without having to uncompress it (eg. Norton Security). These typically

just rewrite characters in the header with '-' so we can look for this to decide

if the original client request was HTTP/1.1 if it has come through a proxy

(indicated by a Via or X-Forwarded-For header). -->

<!-- is the request HTTP/1.1? -->

<if match="HTTP/1\.1" server="SERVER_PROTOCOL">

<choose>

<!-- via a proxy? -->

<when match="\w+" header="Via">

<!-- original request HTTP/1.1 (Accept-Encoding header masked) -->

<if match="-" header="---------------">

<set name="attempt" value="true" />

</if>

<if match="-" header="_______________">

<set name="attempt" value="true" />

</if>

</when>

<!-- forwarded by a proxy? -->

<when match="\w+" header="X-Forwarded-For">

<!-- original request HTTP/1.1 (Accept-Encoding header masked) -->

<if match="-" header="---------------">

<set name="attempt" value="true" />

</if>

<if match="-" header="_______________">

<set name="attempt" value="true" />

</if>

</when>

<otherwise>

<set name="attempt" value="true" />

</otherwise>

</choose>

</if>

<if compare="true" with="attempt">

<!-- use the User Agent string to determine if the client will accept compressed content

and vary the cache by this header so different versions are stored in caches / proxies -->

<use context="Request.UserAgent" />

<add name="varyBy" value="User-Agent" />

<choose>

<!-- Internet Explorer -->

<when match="^Mozilla[^(]*\(compatible; MSIE (?'version'(?'major'\d+)(?'minor'\.\d+)(?'letters'\w*))(?'extra'.*)">

<!-- not all versions support compression, handle the exceptions -->

<choose>

<!-- IE on the Macintosh does not support compression -->

<when match="Mac_68000|Macintosh.*68K|Mac_PowerPC|Macintosh.*PPC|PPC Mac">

</when>

<!-- IE Web Services?do not support compression (unless specified) -->

<when match="Web Services Client">

</when>

<!-- IE 4+ on the PC supports compression -->

<when match="^[4-9]\." capture="version">

<set name="compression" value="true" />

<set name="varyBy" value="*" />

</when>

</choose>

</when>

<!-- Mozilla 5.0 based browsers (Firefox / Netscape) support compression -->

<when match="^Mozilla/5\.0 \(.*?\) Gecko/\d+">

<set name="compression" value="true" />

<set name="varyBy" value="*" />

</when>

<!-- Opera -->

<when match="^Opera[ /](?'version'(?'major'\d+)(?'minor'\.\d+)(?'letters'\w*))">

<!-- Opera 5+ supports compression -->

<if match="[5-9]" capture="major">

<set name="compression" value="true" />

<set name="varyBy" value="*" />

</if>

</when>

<!-- any additional browser checks should be added here -->

</choose>

</if>

</otherwise>

</choose>

<!-- if compression is activated then check for exceptions / browser quirks & app specific settings -->

<if compare="true" with="compression">

<choose>

<!-- Internet Explorer -->

<when match="^Mozilla[^(]*\(compatible; MSIE (?'version'(?'major'\d+)(?'minor'\.\d+)(?'letters'\w*))(?'extra'.*)" context="Request.UserAgent">

<!-- due to the interaction between IE and the Adobe Acrobat plugin compression

can cause problems so disable it also, IE doesn't like compressed JavaScript

(when it's cached locally and then re-loaded) -->

<if match="application/pdf|application/javascript" context="Response.ContentType">

<set name="compression" value="false" />

<add name="varyBy" value="User-Agent" />

</if>

</when>

<!-- Netscape Navigator -->

<when match="^Mozilla/(?'version'(?'major'\d+)(?'minor'\.\d+)(?'letters'\w*)).*" context="Request.UserAgent">

<!-- version 4.x has bugs with compression -->

<if match="^4\." capture="version">

<choose>

<!-- version 4.06/7/8 cannot reliably handle compessed content at all (despite claiming to) -->

<when match="^4\.0[678]" capture="version">

<set name="compression" value="false" />

<add name="varyBy" value="User-Agent" />

</when>

<!-- version 4.x has problems with compressed CSS and JavaScript -->

<when match="text/css|text/javascript" context="Response.ContentType">

<set name="compression" value="false" />

<add name="varyBy" value="User-Agent" />

</when>

</choose>

</if>

</when>

</choose>

<!-- any application specific settings for different compression levels should be defined here. eg:

<use context="Request.RawUrl">

<choose>

<when match="hugepage\.aspx"><set name="level" value="high" /></when>

<when match="tinypage\.aspx"><set name="level" value="low" /></when>

</choose>

-->

</if>

</otherwise>

</choose>

</aspAccelerator>

</intesoft>

<system.web>

<!-- add ASPAccelerator module to this web application -->

<httpModules>

<add name="ASPAccelerator" type="Intesoft.Web.Performance.AcceleratorModule, Intesoft.ASPAccelerator, Culture=neutral, Publi?KeyToken=75ebecc4fcf8b09f" />

</httpModules>

<!-- DYNAMIC DEBUG COMPILATION

Set compilation debug="true" to insert debugging symbols (.pdb information)

into the compiled page. Because this creates a larger file that executes

more slowly, you should set this value to true only when debugging and to

false at all other times. For more information, refer to the documentation about

debugging ASP.NET files.

-->

<compilation defaultLanguage="vb" debug="true" />

<!-- CUSTOM ERROR MESSAGES

Set customErrors mode="On" or "RemoteOnly" to enable custom error messages, "Off" to disable.

Add <error> tags for each of the errors you want to handle.

"On" Always display custom (friendly) messages.

"Off" Always display detailed ASP.NET error information.

"RemoteOnly" Display custom (friendly) messages only to users not running

on the local Web server. This setting is recommended for security purposes, so

that you do not display application detail information to remote clients.

-->

<customErrors mode="RemoteOnly" />

<!-- AUTHENTICATION

This section sets the authentication policies of the application. Possible modes are "Windows",

"Forms", "Passport" and "None"

"None" No authentication is performed.

"Windows" IIS performs authentication (Basic, Digest, or Integrated Windows) according to

its settings for the application. Anonymous access must be disabled in IIS.

"Forms" You provide a custom form (Web page) for users to enter their credentials, and then

you authenticate them in your application. A user credential token is stored in a cookie.

"Passport" Authentication is performed via a centralized authentication service provided

by Microsoft that offers a single logon and core profile services for member sites.

-->

<authentication mode="None" />

<!-- AUTHORIZATION

This section sets the authorization policies of the application. You can allow or deny access

to application resources by user or role. Wildcards: "*" mean everyone, "?" means anonymous

(unauthenticated) users.

-->

<authorization>

<allow users="*" />

<!-- Allow all users -->

<!-- <allow users="[comma separated list of users]"

roles="[comma separated list of roles]"/>

<deny users="[comma separated list of users]"

roles="[comma separated list of roles]"/>

-->

</authorization>

<!-- APPLICATION-LEVEL TRACE LOGGING

Application-level tracing enables trace log output for every page within an application.

Set trace enabled="true" to enable application trace logging. If pageOutput="true", the

trace information will be displayed at the bottom of each page. Otherwise, you can view the

application trace log by browsing the "trace.axd" page from your web application

root.

-->

<trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true" />

<!-- SESSION STATE SETTINGS

By default ASP.NET uses cookies to identify which requests belong to a particular session.

If cookies are not available, a session can be tracked by adding a session identifier to the URL.

To disable cookies, set sessionState cookieless="true".

-->

<sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes" cookieless="false" timeout="20" />

<!-- GLOBALIZATION

This section sets the globalization settings of the application.

-->

<globalization requestEncoding="utf-8" responseEncoding="utf-8" />

<webServices>

<wsdlHelpGenerator href="helppage.aspx" />

<protocols>

<?dd name="HttpGet" />

<add name="HttpPost" />

</protocols>

<soapExtensionTypes>

<add type="Microsoft.Web.Services2.WebServicesExtension, Microsoft.Web.Services2, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" priority="1" group="0" />

</soapExtensionTypes>

</webServices>

</system.web>

<microsoft.web.services2>

<security>

<timeToleranceInSeconds>86400</timeToleranceInSeconds>

</security>

<messaging>

<maxRequestLength>256000</maxRequestLength>

<!-- 256 mb -->

</messaging>

<filters>

<input>

<add type="Intesoft.Web.Performance.SoapInputFilter, Intesoft.ASPAccelerator" />

</input>

<output>

<add type="Intesoft.Web.Performance.SoapOutputFilter, Intesoft.ASPAccelerator" />

</output>

</filters>

</microsoft.web.services2>

</configuration>



J@ck@llM@ster0
Post #2960
Posted 4/10/2006 11:17:01 AM


www.ehuna.org

www.ehuna.orgwww.ehuna.orgwww.ehuna.orgwww.ehuna.orgwww.ehuna.orgwww.ehuna.orgwww.ehuna.orgwww.ehuna.org

Group: Administrators
Last Login: 12/17/2008 10:36:11 PM
Posts: 258, Visits: 13,336
Your PDS Service configuration file looks ok.  According to the error you PM'd me, it looks like a problem with WSE.  Can you try to re-install WSE?  You can find the installer on the PDS CD.

Note: don't post your SQL password on the forum.  I masked your real password with starts above ("******").



Disclaimer
: this post carries no explicit or implied warranty. Nor is there any guarantee that the information contained in this post is accurate. It is offered in the hopes of helping others, but you use it at your own risk. The author will not be liable for any damages that occur as a result of using this post.

Post #2961
Posted 4/10/2006 11:26:51 AM
Junior Member

Junior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior Member

Group: Forum Members
Last Login: 4/10/2006 9:19:03 PM
Posts: 12, Visits: 28
Emmanual,

thanks, I will try the install and also thanks for masking my info.

Dale

J@ck@llM@ster0

Post #2963
Posted 4/10/2006 11:38:08 AM
Junior Member

Junior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior Member

Group: Forum Members
Last Login: 4/10/2006 9:19:03 PM
Posts: 12, Visits: 28
Emmanual,

I tried the reinstall, however; this did not fix the problem. I have checked all the permissions, I have checked everything at least three times. I still get the same error when I browse the service web site:

here is the result:

thanks...... dale

You are not authorized to view this page

You might not have permission to view this directory or page using the credentials you supplied.

If you believe you should be able to view this directory or page, please try to contact the Web site by using any e-mail address or phone number that may be listed on the 127.0.0.1 home page.

You can click search.gif (114 bytes) Search to look for information on the Internet.


HTTP Error 403 - Forbidden
Internet Explorer

 



J@ck@llM@ster0

Post #2964
Posted 4/13/2006 8:14:07 AM
Calyx Software

Calyx SoftwareCalyx SoftwareCalyx SoftwareCalyx SoftwareCalyx SoftwareCalyx SoftwareCalyx SoftwareCalyx Software

Group: Administrators
Last Login: 7/18/2008 1:42:09 PM
Posts: 94, Visits: 467
Dale and I discussed this issue last night. We ended up changing the default page for the service page under documents in iis to pdsfunctions.asmx and doing a reinstall. He is up and running now.
Post #2978
« Prev Topic | Next Topic »


Reading This TopicExpand / Collapse
Active Users: 0 (0 guests, 0 members, 0 anonymous members)
No members currently viewing this topic.
Forum Moderators: Emmanuel Huna, Bryan Telford, Jason Beck, Mike Thompson, BetaFisch

PermissionsExpand / Collapse

All times are GMT -8:00, Time now is 12:42am

Powered by InstantForum.NET v4.1.4 © 2009
Execution: 0.031. 10 queries. Compression Enabled.
© 2005 Calyx Software. All rights reserved.