Hello
Remember WinInet is only sup****ted for use in desktop application.
238425 INFO: WinInet Not Sup****ted for Use in Services
http://sup****t.microsoft.com/?id=238425
You may also want to test on the problem box using VBHTTP
259100 SAMPLE: Vbhttp.exe Demonstrates How to Use HTTP WinInet APIs in
Visual
http://sup****t.microsoft.com/?id=259100
Other then that you can get Network trace and WinINet log.
You can download debug builds of WinInet.Dll from the following location:
ftp://ftp.microsoft.com/PSS/Tools/Developer%20Sup****t%20Tools/WinInet/
You should use the build number that is closest to the version of WinInet
that is on your system.
On Win ME/ Windows 2000/ Windows XP and greater OSs with Windows File
Protection
1. Configure Internet Explorer to use a default Start Page as close to the
page as possible. This eliminates much unnecessary logging that will add
additional size to the output log.
2. Close Internet Explorer as well as any other Internet-based
applications
(additional applications that use WININET for connectivity may generate
extra traffic within the log).
3. Navigate to the location of where Internet Explorer is installed.
Typically this is either the \Program Files\Internet Explorer folder or
the
\Program Files\Plus!\Microsoft Internet folder.
4. You must have extensions viewable so that the proper extension is
assigned to your file. You can turn on the extensions for all files by
going into the Folder Options from within Windows Explorer and choosing
the
View tab and selecting to ‘Show all files’ and to not “Hide extensions of
known file types”.
5. Create a dummy file out of a new text file. Rename the file to the
following filename and extension:
IEXPLORE.EXE.LOCAL
The proper extension for this file is .local If you create this file and
you still have a Notepad icon for the file, re-do step 4 above.
6. Once the file has been created successfully, copy a suitable logging
version of WININET.DLL into the same directory as the file you created in
step 5.
7. Once the logging version of WININET is in place, open a CMD prompt.
Navigate to the location of where Internet Explorer is installed.
Typically this is either the \Program Files\Internet Explorer folder or
the
\Program Files\Plus!\Microsoft Internet folder.
8. At the CMD prompt, type the following and hit <enter>:
SET WININETLOG=1
9. Now that the logging environment variable is set, you can now start the
logging by typing the following and hitting <enter>:
IEXPLORE.EXE
10. Internet Explorer should now open on the desktop and navigate to the
Start Page. It is im****tant that you do not close either the CMD window
or
Internet Explorer. As soon as Internet Explorer starts navigation, a
WININET.LOG file will be created on the desktop. Do not attempt to open
this log while it is being written to.
11. Recreate the problem. Once the behavior is observed, you can now
safely close Internet Explorer, as well as the CMD window. Logging should
cease. The log file should be zipped up and forwarded to a sup****t
professional that has been trained to read these logs. If the log is too
large to send via Microsoft email (5mb), then it must be placed on the
FTPPSS FTP site (ftp://ftppss.microsoft.com)
12. Very Im****tant: once logging is complete, you should remove the
logging version of WININET.DLL and the IEXPLORE.EXE.LOCAL file. Leaving
the logging version of WININET.DLL in place can affect overall browsing
performance because of the numerous checks written into that version.
TIP: For contrast purposes, it would be advisable to have a log of the
problem occurring and one of a normal condition, if possible. Also, a
Network Monitor packet trace that is taken at the same time as the WININET
log may also be beneficial when attempting to correlate network patterns
during the WININET communication.
NOTE: All of Microsoft’s operating systems from Windows 2000 and forward
sup****t the use of IEXPLORE.EXE.LOCAL. This concept is called Dynamic
Link
Library Redirection and do***ented online at http://msdn.microsoft.com.
NOTE: If you are using a custome WinInet application you can replace
IEXPLORE.EXE.LOCAL with your Application file name. And then run your
application from the command prompt.
NOTE: You can change where the log file is saved by setting environment
variable WininetLogFile, like this:
"set wininetlogfile=c:\temp\MyNewLog.log" with out the quotes.
Thanks
Brian [MSFT]
Microsoft Developer Sup****t
This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
| From: sergio.turon@[EMAIL PROTECTED]
(Sergio T.)
| Newsgroups: microsoft.public.inetsdk.programming.wininet
| Subject: Time Out in InternetOpenUrl Function, why?
| Date: 20 Aug 2004 06:01:33 -0700
| Organization: http://groups.google.com
| Lines: 26
| Message-ID: <c8034be1.0408200501.66af1cec@[EMAIL PROTECTED]
>
| NNTP-Posting-Host: 80.58.47.170
| Content-Type: text/plain; charset=ISO-8859-1
| Content-Transfer-Encoding: 8bit
| X-Trace: posting.google.com 1093006893 2298 127.0.0.1 (20 Aug 2004
13:01:33 GMT)
| X-Complaints-To: groups-abuse@[EMAIL PROTECTED]
| NNTP-Posting-Date: Fri, 20 Aug 2004 13:01:33 +0000 (UTC)
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.s
ul.t-online.de!t-online.de!newsfeed.gamma.ru!Gamma.RU!newsfeed.icl.net!newsf
eed.fjserv.net!news-lond.gip.net!news.gsl.net!gip.net!news.tele.dk!news.tele
dk!small.news.tele.dk!proxad.net!postnews2.google.com!not-for-mail
| Xref: cpmsftngxa10.phx.gbl
microsoft.public.inetsdk.programming.wininet:11619
| X-Tomcat-NG: microsoft.public.inetsdk.programming.wininet
|
| Hi everyone!
|
| I have a problem with wininet programming. A few days ago I started to
| make a little DLL in VB that uses wininet, a new experience for me, in
| order to open an url, get his code (with InternetOpenUrl) and work
| with it.
|
| I have had no problem when I've programmed and tuned it in my machine,
| and it works well, but when I upload the dLL to the main web server it
| doesn´t work and show the error 12002 (ERROR_INTERNET_TIMEOUT) in my
| error control Interface.
|
| The fact is that it only happens with some urls. For example, trying
| on the main server with the basic url "www.google.es"... it works
| OK... so I mean that conexion parameters in the main server are OK
| (proxy etc...) and the problem is "only" a TimeOut which starts to
| become mad.
|
| I've tried with InternetQueryOption and INTERNET_OPTION_SEND_TIMEOUT
| etc... with no results. I think this function have problems with some
| versions of wininet.dll Can anybody give me some idea? Why does it
| works in my machine, but not in the server? Versions? What can I do?
|
| Thanks, Sergio.
|
| PD: I know my basic english, sorry!!
|
|
