Search results matching tag 'ODBC'

ASP & Access 4005 error: defining 32 bit dsn on 64 bit windows

timpollard — Fri, 30 Oct 2009 09:55:26 GMT

I'm having trouble making classic asp with access db work on Windows 7. On one box I have it all working fine on a 32 bit W7 Pro install, but on my main development server I am using 64 bit W7Pro and this one still doesn't work.

On both machines I have used the icacls workaround to grant appropriate permissions on the Users/Useraccount/AppData/Local/Temp folder, have also fiven that folder permissions for the IUSR account, and the same for the folder which contains the db. This worked for the 32 bit machine, but not the 64.

I then used the Process Monitor to trace w3wp.exe and discovered, if I'm reading the log file right, that the problem is that w7 64 bit can't find the dsn.

When I set up the dsn I went first to the default ODBC Admin console, only to find that in a 64 bit OS this only offers 64 bit drivers. I googled that and found that there is a legacy 32 bit version, which I used to create the dsn. However, although it appears to be there when viewed in the 32 bit ODBC Console, the 64 bit OS doesn't seem to recognise it.

Can anyone help, please?

The log file is below. I've highlighted the line which appears to suggest it can't find the dsn.

Tim

"Time of Day","Process Name","PID","Operation","Path","Result","Detail"
"09:34:39.4159347","w3wp.exe","7960","CreateFile","D:\My Documents\Web sites\dollman","SUCCESS","Desired Access: Generic Read, Disposition: Open, Options: Sequential Access, No Buffering, Attributes: RE, ShareMode: Read, Write, Delete, AllocationSize: n/a, Impersonating: NT AUTHORITY\IUSR, OpenResult: Opened"
"09:34:39.4159860","w3wp.exe","7960","QueryAllInformationFile","D:\My Documents\Web sites\dollman","BUFFER OVERFLOW","CreationTime: 28/02/2009 17:13:45, LastAccessTime: 21/04/2009 14:00:19, LastWriteTime: 21/04/2009 14:00:19, ChangeTime: 21/04/2009 14:00:19, FileAttributes: D, AllocationSize: 8,192, EndOfFile: 8,192, NumberOfLinks: 1, DeletePending: False, Directory: True, IndexNumber: 0x2000000013675, EaSize: 0, Access: Generic Read, Position: 0, Mode: Sequential Access, No Buffering, AlignmentRequirement: Word"
"09:34:39.4160668","w3wp.exe","7960","CreateFile","D:\My Documents\Web sites\dollman\DEFAULT.HTM","NAME NOT FOUND","Desired Access: Generic Read, Disposition: Open, Options: Sequential Access, Attributes: RE, ShareMode: Read, Write, Delete, AllocationSize: n/a, Impersonating: NT AUTHORITY\IUSR"
"09:34:39.4161531","w3wp.exe","7960","CreateFile","D:\My Documents\Web sites\dollman\default.asp","SUCCESS","Desired Access: Generic Read, Disposition: Open, Options: Sequential Access, Attributes: RE, ShareMode: Read, Write, Delete, AllocationSize: n/a, Impersonating: NT AUTHORITY\IUSR, OpenResult: Opened"
"09:34:39.4163917","w3wp.exe","7960","QueryAllInformationFile","D:\My Documents\Web sites\dollman\default.asp","BUFFER OVERFLOW","CreationTime: 28/02/2009 17:13:45, LastAccessTime: 28/02/2009 17:13:45, LastWriteTime: 06/11/2008 09:39:08, ChangeTime: 29/10/2009 15:01:48, FileAttributes: A, AllocationSize: 24,576, EndOfFile: 23,009, NumberOfLinks: 1, DeletePending: False, Directory: False, IndexNumber: 0x200000001367f, EaSize: 0, Access: Generic Read, Position: 0, Mode: Sequential Access, AlignmentRequirement: Word"
"09:34:39.4164733","w3wp.exe","7960","CreateFile","D:\My Documents\Web sites\dollman","SUCCESS","Desired Access: Read Data/List Directory, Read Attributes, Synchronize, Disposition: Open, Options: , Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened"
"09:34:39.4165243","w3wp.exe","7960","NotifyChangeDirectory","D:\My Documents\Web sites\dollman","","Filter: FILE_NOTIFY_CHANGE_FILE_NAME, FILE_NOTIFY_CHANGE_DIR_NAME, FILE_NOTIFY_CHANGE_ATTRIBUTES, FILE_NOTIFY_CHANGE_SIZE, FILE_NOTIFY_CHANGE_LAST_WRITE, FILE_NOTIFY_CHANGE_CREATION, FILE_NOTIFY_CHANGE_EA, FILE_NOTIFY_CHANGE_SECURITY, FILE_NOTIFY_CHANGE_STREAM_NAME, FILE_NOTIFY_CHANGE_STREAM_SIZE, FILE_NOTIFY_CHANGE_STREAM_WRITE"
"09:34:39.4165519","w3wp.exe","7960","ReadFile","D:\My Documents\Web sites\dollman\default.asp","SUCCESS","Offset: 0, Length: 23,009, Priority: Normal"
"09:34:39.4165933","w3wp.exe","7960","QuerySecurityFile","D:\My Documents\Web sites\dollman\default.asp","SUCCESS","Information: Owner, Group, DACL"
"09:34:39.4166178","w3wp.exe","7960","CloseFile","D:\My Documents\Web sites\dollman\default.asp","SUCCESS",""
"09:34:39.4167040","w3wp.exe","7960","QueryOpen","D:\My Documents\Web sites\dollman\Default.asp\web.config","PATH NOT FOUND",""
"09:34:39.4169856","w3wp.exe","7960","RegOpenKey","HKU\S-1-5-17","NAME NOT FOUND","Desired Access: Maximum Allowed"
"09:34:39.4170093","w3wp.exe","7960","RegOpenKey","HKU\.Default","SUCCESS","Desired Access: Maximum Allowed, Granted Access: Read"
"09:34:39.4170545","w3wp.exe","7960","RegOpenKey","HKU\.DEFAULT\Control Panel\International","SUCCESS","Desired Access: Read"
"09:34:39.4170794","w3wp.exe","7960","RegCloseKey","HKU\.DEFAULT","SUCCESS",""
"09:34:39.4170978","w3wp.exe","7960","RegQueryValue","HKU\.DEFAULT\Control Panel\International\LocaleName","SUCCESS","Type: REG_SZ, Length: 12, Data: en-GB"
"09:34:39.4171216","w3wp.exe","7960","RegCloseKey","HKU\.DEFAULT\Control Panel\International","SUCCESS",""
"09:34:39.4174813","w3wp.exe","7960","RegQueryKey","HKU\.DEFAULT","SUCCESS","Query: HandleTags, HandleTags: 0x0"
"09:34:39.4175101","w3wp.exe","7960","RegOpenKey","HKU\.DEFAULT\SOFTWARE\ODBC\ODBC.INI\dsnDollman","NAME NOT FOUND","Desired Access: Read"
"09:34:39.4175380","w3wp.exe","7960","RegQueryKey","HKLM","SUCCESS","Query: HandleTags, HandleTags: 0x0"
"09:34:39.4175629","w3wp.exe","7960","RegOpenKey","HKLM\SOFTWARE\ODBC\ODBC.INI\dsnDollman","NAME NOT FOUND","Desired Access: Read"
"09:34:39.4175917","w3wp.exe","7960","RegQueryKey","HKU\.DEFAULT","SUCCESS","Query: HandleTags, HandleTags: 0x0"
"09:34:39.4176173","w3wp.exe","7960","RegOpenKey","HKU\.DEFAULT\SOFTWARE\ODBC\ODBC.INI\Default","NAME NOT FOUND","Desired Access: Read"
"09:34:39.4176422","w3wp.exe","7960","RegQueryKey","HKLM","SUCCESS","Query: HandleTags, HandleTags: 0x0"
"09:34:39.4176668","w3wp.exe","7960","RegOpenKey","HKLM\SOFTWARE\ODBC\ODBC.INI\Default","NAME NOT FOUND","Desired Access: Read"
"09:34:39.4176947","w3wp.exe","7960","RegQueryKey","HKU\.DEFAULT","SUCCESS","Query: HandleTags, HandleTags: 0x0"
"09:34:39.4177189","w3wp.exe","7960","RegOpenKey","HKU\.DEFAULT\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources","NAME NOT FOUND","Desired Access: Query Value"
"09:34:39.4177434","w3wp.exe","7960","RegQueryKey","HKLM","SUCCESS","Query: HandleTags, HandleTags: 0x0"
"09:34:39.4177671","w3wp.exe","7960","RegOpenKey","HKLM\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources","NAME NOT FOUND","Desired Access: Query Value"
"09:34:39.4177917","w3wp.exe","7960","RegQueryKey","HKLM","SUCCESS","Query: HandleTags, HandleTags: 0x0"
"09:34:39.4178215","w3wp.exe","7960","RegOpenKey","HKLM\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\ODBC Data Sources","SUCCESS","Desired Access: Read"
"09:34:39.4178568","w3wp.exe","7960","RegSetInfoKey","HKLM\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\ODBC Data Sources","SUCCESS","KeySetInformationClass: KeySetHandleTagsInformation, Length: 0"
"09:34:39.4178813","w3wp.exe","7960","RegQueryValue","HKLM\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\ODBC Data Sources\dsnDollman","SUCCESS","Type: REG_SZ, Length: 64, Data: Microsoft Access Driver (*.mdb)"
"09:34:39.4179169","w3wp.exe","7960","RegCloseKey","HKLM\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\ODBC Data Sources","SUCCESS",""
"09:34:39.4179802","w3wp.exe","7960","RegQueryKey","HKCR","SUCCESS","Query: HandleTags, HandleTags: 0x0"
"09:34:39.4180058","w3wp.exe","7960","RegOpenKey","HKCR\CLSID\{C8B522CB-5CF3-11CE-ADE5-00AA0044773D}\ExtendedErrors","SUCCESS","Desired Access: Read"
"09:34:39.4180372","w3wp.exe","7960","RegEnumKey","HKCR\CLSID\{C8B522CB-5CF3-11CE-ADE5-00AA0044773D}\ExtendedErrors","SUCCESS","Index: 0, Name: {c8b522cc-5cf3-11ce-ade5-00aa0044773d}"
"09:34:39.4180794","w3wp.exe","7960","RegCloseKey","HKCR\CLSID\{C8B522CB-5CF3-11CE-ADE5-00AA0044773D}\ExtendedErrors","SUCCESS",""
"09:34:39.4184591","w3wp.exe","7960","CloseFile","D:\My Documents\Web sites\dollman","SUCCESS",""

Custom Logging configured but not able to see bytes sent

thaichi23 — Tue, 20 Oct 2009 11:00:36 GMT

Hello all,

I have done all the steps to enable ODBC logging in IIS7. I can see that it is in fact working and recording information in SQL but for bytes sent, it is not showing anything. The default fields are fine but I would like for it to record bytes sent as well because that is important.

Unfortunately the "select fields" button is grayed out so I know I'll have to do it with an appcmd statement. What would be the appcmd statement to change the logExtFileFlags?

Edit: I have been hacking away at the applicationhost.config file and added bytessent and bytesrecv to all the logs and still no data shows up in my sql database.

Also another thing I ran into is that for some reason it will not show the name of the document if it was clicked on. It only shows the url to the website in which it was accessed and not the actual file name. Help please! This is killing me!

Thank you,

Nat Sirimaturos

odbc connection pooling with Delphi 7 & IIS7

ffsetit — Mon, 05 Oct 2009 08:04:19 GMT

We have a application that utilizes a combination of ASP.net (c#) and classic ASP (Delphi 7). When running the application on Windows Vista or Server 2008 using IIS7 we experience terrible performance problems from the classic ASP pages when retrieving data from SQL. Upon investigation using SQL Profiler it is apparent that hard connections are being opened and closed rather than being pooled. We experience the same issue with IIS6 on Server 2003 however this can be worked around by enabling IIS5.0 compatibility mode. Unfortunately there seems to be no such workaround for IIS7 Does anyone have any ideas as to why odbc connection pooling does not work in IIS7 (or 6)

Re: Logging vs. kernel mode caching

LesterDK — Wed, 19 Aug 2009 05:37:28 GMT

Sure I can, try atleast.

Been a while, so cannot remember if this was the actual site that helped me getting it to work, but this was exactly our error. http://mattlog.net/2009/04/16/iis-odbc-logging-event-id-1016-error-data-80070057/ ODBC logging failing and warnings added in eventviewer. Did what Matt he is also showing as the solution, enabled the custom logging feature and ODBC logging started working.

If I recall it right, the ODBC logging had to be enabled via some appCmd and there is no kind of warning, adding the ODBC logging feature does not automatically add the custom logging feature or state that it is depending on that to work.

Though this may or may not be correct, it did indeed solve the problem for us. Of course it could be something else than the custom logging feature itself that did the trick, but whatever it was, it got active when that specific feature was added.

Re: Visual Web Developer 2008 Express with SP1 this product did not install successfully

Taeke — Sat, 11 Jul 2009 10:02:02 GMT

[quote user="kapikiri"]

DownloadManager Information: 0 : Increasing current install to 8
DownloadManager Information: 0 : SQL Server 2008 Management Objects installation log: C:\Documents and Settings\user\Local Settings\Application Data\Microsoft\Web Platform Installer\logs\install\2009-07-10T09.07.25\SharedManagementObjects.txt
DownloadManager Warning: 0 : Dependency failed for product 'Silverlight 3 Tools for Visual Studio'. Skipping install
DownloadManager Information: 0 : Product Silverlight 3 Tools for Visual Studio had a dependency fail. Increasing install product to 9
DownloadManager Information: 0 : Clearing cart

[/quote]

ODBC logging - processingtime = 0ms

LesterDK — Mon, 11 May 2009 15:29:40 GMT

We are currently using ODBC logging on a variety of machines, they are all using the same database.

For some odd reason all the entries from our 2008 Server / IIS7 shows a processingtime of 0, the other servers show a number worth doing stats on. I find it hard to believe that we do not have a single request taking more than 0ms to process.

No errors in the eventlog, only the errors from when we changed the application pool to be 32bit and had to create an 32bit ODBC entry via the syswow64/odbc.exe (Woops - and do remember to install custom logging to be able to use ODBC logging)

Anyone got a clue on why this one field just seems not to be set correctly? And how to fix it? Missing dependecy, error when using 32bit appPool.... or whatever it might be.

Re: Building package for ODBC data provider

faith_a — Wed, 29 Apr 2009 15:43:40 GMT

Hi workerbee2,

We don't have a specific ODBC provider but system DSNs are stored in the registry, so you can grab it using the regkey and regvalue providers.

I created a system DSN called TestODBC and then searched the registry to determine where it was stored.

Here's an example manifest that captures this DSN (saved as manifest.xml):

Then sync to a package:

msdeploy -verb:sync -source:manifest=manifest.xml -dest:package=c:\ODBC.zip

And sync from the package:

msdeploy -verb:sync -source:package=c:\ODBC.zip -dest:auto

Let me know if you have any questions or different ODBC connections that need to be synced.

thanks,

-faith

Building package for ODBC data provider

WorkerBee2 — Wed, 29 Apr 2009 04:26:56 GMT

Our ASP.NET application uses ODBC data provider. We need to have the web deployment tool create a database, an ODBC data source and update the ODBC connection string in web.config. The only documentation is that single web page that shows how to do it for SqlClient. Can you tell us how to achieve the steps I described above? Thanks!

How do we build a package for our app that uses ODBC data provider

WorkerBee2 — Sat, 25 Apr 2009 23:10:41 GMT

How do we build a package for our app that uses ODBC data provider

WorkerBee2 — Sat, 25 Apr 2009 23:06:41 GMT