Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 917
  • Last Modified:

Websites work in Visual Studio Development & IIS6 but NOT in IIS7

Dear Experts

we have upgraded our server from Windows Server 2003 to Windows Server 2008 R2.

1) All our websites work fine on WS 2003 IIS6.

2) All our websites work fine in Visual Studio (also on visual studio on WS 2008 R2)

3) None of the websites work on IIS7. They all use webservices (on the same server).

4) Webservices work if you 'browse' them direct from -> Manage Application -> Browse

5) Application pool is in 'Classic'

6) Identity is 'Network Service'

----------------------------

Tests Already Completed in small tester programs within IIS7 and visual studio.
a) Ajax tester - completed ok
b) Session Variables - completed ok

----------------------------

Please help. I've been pulling my hair out over this.

ps: I know this is a 500 authentification error but how do I overcome this?

Thanks for all your help in advance!

Darren
iis7-error.png
0
Darrenshome
Asked:
Darrenshome
  • 8
  • 3
  • 2
1 Solution
 
tan_devCommented:
your physical path to the folder should be the folder which has web.config inside it. that solved similar problem for me.

also which version of .net framwork are you using for your app pool? 2.0 i hope i think that works with classic pool?
0
 
DarrenshomeAuthor Commented:
Dear tan_dev

This is already the case.....

a) .NET Framework version V2.0.50727
b) Pipeline mode Classic
c) web.config is within physical path

Any other ideas?
0
 
tan_devCommented:
your app pool on the diagonostic is default app pool. Also you are trying to access the webservice. Does you application work fine when you browse it?
0
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 
DarrenshomeAuthor Commented:
Yes...webservices work.

As described in the question number 4.
0
 
DarrenshomeAuthor Commented:
Does anyone else know how to solve my IIS7 problem?

Please help.

Darren
0
 
tan_devCommented:
its probably just the security permissions on your webservice folder.
can you try to grant all access to the user you're trying to run your application with.
0
 
DarrenshomeAuthor Commented:
Dear tan_dev

The webservices are being called from the Inetpub website.

Please be more specific. Which permission should be allowed to call the web services? I already have Network Service including Anonoymous and Everyone on full control on the WebServices folder!

I said from the start this is an Authentification error. No further down the road.....

I think its deeper than this. Theres something not right elsewhere!

Any more suggestions?

Regards
Darren
0
 
DarrenshomeAuthor Commented:
Update

Have created a simple program with a connection string.

Get the error

ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application

Therefore, it seems that it is 32 bit and 64 bit related issue.

IIS7 is pointing to the 64bit odbc admin whilst Visual Studio is pointing to 32bit odbc admin.

The connection string points to a 32bit Pervsaive database odbc and there is no 64 bit available.

Will look at using a 64bit odbc driver to connect to Pervasive.

Regards
Darren
0
 
mirtheilCommented:
You have a few options:

- You can upgrade to Pervasive PSQL v11 to get the 64 bit ODBC driver.  

- You can switch from ODBC to the PSQL Managed Provider to get 64 bit support with PSQL v10.  

- You can make sure your web application is set to "x86" for the Active Solution Platform setting rather than "AnyCPU".  That will force the .NET to use 32 bit.  You might also need to enable 32 bit support within IIS.  
0
 
DarrenshomeAuthor Commented:
Dear Mirtheil

Upgrading Pervasive is out the question....

I have set the Active Solution Platform to 'x86' in Configuration Manager

I have published it direct ti IIS7 but still fails.

ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application

ps: feels like were going in the right directiion though!!!

Any more ideas?

Regards
Darren
x86-visual-studio.png
0
 
mirtheilCommented:
What is your connection string?  Are you using an ODBC DSN?  If so, did you use the ODBC ADministrator in c:\windows\syswow64\odbad32.exe?  
0
 
DarrenshomeAuthor Commented:
Dear All

Got the website working by changing the user permissions on the SQL Server Database

'Select' was not authorised for the logon credentials -> Security settiings within SQL Server. This was the 500 error shown origionally.

Problem Solved By:
1) Databases -> Security -> Users (Click on user to grant permmissions)
2) Database User (Login) opens
3) Securables tab -> Check permission 'Select'

Also, Identity within the AppPool should be ApplicationPoolIdentity.

Therefore:
a) It was NOT to do with 32 or 64 bit
b) Not the permissions on the webservices folder
c) It was NOT the connection string.

ps: Thanks for all your input mirtheil and tan_dev

Regards
Darren
0
 
DarrenshomeAuthor Commented:
Gave detailed instructions on how to allow permissions on SQL Server Database that held data for webservices used by a website.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 8
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now