Publishing error

[Dogsofdeep]

I recently redesigned my website, I changed the new
hoepage to index.html and attempted to publish the files,
everytime I try it I get this error WinINet error 12163.
Please anyhelp will be apreciated this is a business site
and I would like to get it uploaded as soon as possible.
Thanks
Donald

 

[E. T. Culling]

Don't know what that error means but...........
Your ISP will tell you what to use for your home page: index.htm,
index.html, default.htm or default.html..... It's not something you can
decide. Check with your ISP.
ETC

 

[Stefan B Rusynko]

The only error I see w/ WinINet is at
http://support.microsoft.com/default.aspx?scid=kb;en-us;310853

Rename your home page back to that required by your host server




| I recently redesigned my website, I changed the new
| hoepage to index.html and attempted to publish the files,
| everytime I try it I get this error WinINet error 12163.
| Please anyhelp will be apreciated this is a business site
| and I would like to get it uploaded as soon as possible.
| Thanks
| Donald

 

[Orest Kinasevych]

How did we make the connection between the renaming of the home page
(index.html) and the WinInet error 12163?

1. "index.html" has historically been the standard name for the default
page in a web server directory. If anything, I'd guess that the ISP may
have *added* alternates (without removing the default) and that the web
server first looks for index.html, and then the alternatives in a
particular order. This would not cause the use of "index.html" to cause
errors. That's the first reason reason why I wouldn't look here for the
cause of the problem.

2. An incorrectly named home page should not generate an error when it
is being published. The error of an incorrectly named home page will
manifest itself in the web browser in a number of possible and very
common ways, including listing the contents of that directory or
displaying a 404 - File Not Found error. That's another reason why I
wouldn't consider the file name as the cause of the problem originally
described.

3. A quick search on Google turned up a number of references to the
WinInet error 12163. It appears to be an error code generated by some
component of Delphi (a programming language that was probably used for
some component of the Internet connection). By all accounts the 12163
error appears to be "ERROR_INTERNET_DISCONNECTED", which is interpreted
as "possibly working offline." A link from one of these references
points to a Micosoft MSDN page that lists the errors by name, not
number, and provides confirmation of that interpretation:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wininet/wininet/wininet_errors.asp


So, Dogsofdeep, we're back to not having a solution to your problem. My
guess is that there's something up with your connection to the Internet.
What type of connection is is? Are you using any special software to
help you get connected or stay connected? Are you using any software
meant to speed up your Internet connection? Is there any other software
running in the background, including systray items like Kazaa, or
Morpheus, or other tools that rely on an Internet connection?

Bottom line is that the 12163 error isn't caused by the renamed
index.html file. There's something else going on, most likely
attributable to your Internet connection.

- Orest

The only error I see w/ WinINet is at
http://support.microsoft.com/default.aspx?scid=kb;en-us;310853

Rename your home page back to that required by your host server




| I recently redesigned my website, I changed the new
| hoepage to index.html and attempted to publish the files,
| everytime I try it I get this error WinINet error 12163.
| Please anyhelp will be apreciated this is a business site
| and I would like to get it uploaded as soon as possible.
| Thanks
| Donald

 

[Orest Kinasevych]

According to another web site, the 12163 error is the result of Internet
Explorer being in "Work Offline" mode. At this other web site, they
discuss a program that uses the WinInet Windows library for its
functionality. They suggest that if you switch to Work Offline mode in
IE, it will effect all programs on your computer that use WinInet.

So, try unchecking "Work Offline in IE" and try publishing your web site
again.

I found this info at http://www.prestosoft.com/ps.asp?page=fvc_faq#5,
via Google.

HTH

How did we make the connection between the renaming of the home page
(index.html) and the WinInet error 12163?

1. "index.html" has historically been the standard name for the default
page in a web server directory. If anything, I'd guess that the ISP may
have *added* alternates (without removing the default) and that the web
server first looks for index.html, and then the alternatives in a
particular order. This would not cause the use of "index.html" to cause
errors. That's the first reason reason why I wouldn't look here for the
cause of the problem.

2. An incorrectly named home page should not generate an error when it
is being published. The error of an incorrectly named home page will
manifest itself in the web browser in a number of possible and very
common ways, including listing the contents of that directory or
displaying a 404 - File Not Found error. That's another reason why I
wouldn't consider the file name as the cause of the problem originally
described.

3. A quick search on Google turned up a number of references to the
WinInet error 12163. It appears to be an error code generated by some
component of Delphi (a programming language that was probably used for
some component of the Internet connection). By all accounts the 12163
error appears to be "ERROR_INTERNET_DISCONNECTED", which is interpreted
as "possibly working offline." A link from one of these references
points to a Micosoft MSDN page that lists the errors by name, not
number, and provides confirmation of that interpretation:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wininet/wininet/wininet_errors.asp



So, Dogsofdeep, we're back to not having a solution to your problem. My
guess is that there's something up with your connection to the Internet.
What type of connection is is? Are you using any special software to
help you get connected or stay connected? Are you using any software
meant to speed up your Internet connection? Is there any other software
running in the background, including systray items like Kazaa, or
Morpheus, or other tools that rely on an Internet connection?

Bottom line is that the 12163 error isn't caused by the renamed
index.html file. There's something else going on, most likely
attributable to your Internet connection.

- Orest

 

[Steve Easton]

Depends upon the server and the server settings.

There are actually 4 common default home pages.
index.htm
index.html
default.htm
default.html.

Also I very rarely if ever have IE running when I publish.
The FrontPage publish feature is "Stand Alone"
and requires nothing but an enabled connection.

Steve

 

[David Baxter]

Also occasionally some servers/hosts use home.html or home.htm

Depends upon the server and the server settings.

There are actually 4 common default home pages.
index.htm
index.html
default.htm
default.html.

Also I very rarely if ever have IE running when I publish.
The FrontPage publish feature is "Stand Alone"
and requires nothing but an enabled connection.

Steve
--
using 2k PRO but....95isalive
This site is best viewed............
.......................with a computer

How did we make the connection between the renaming of the home page
(index.html) and the WinInet error 12163?

1. "index.html" has historically been the standard name for the default
page in a web server directory. If anything, I'd guess that the ISP may
have *added* alternates (without removing the default) and that the web
server first looks for index.html, and then the alternatives in a
particular order. This would not cause the use of "index.html" to cause
errors. That's the first reason reason why I wouldn't look here for the
cause of the problem.

2. An incorrectly named home page should not generate an error when it
is being published. The error of an incorrectly named home page will
manifest itself in the web browser in a number of possible and very
common ways, including listing the contents of that directory or
displaying a 404 - File Not Found error. That's another reason why I
wouldn't consider the file name as the cause of the problem originally
described.

3. A quick search on Google turned up a number of references to the
WinInet error 12163. It appears to be an error code generated by some
component of Delphi (a programming language that was probably used for
some component of the Internet connection). By all accounts the 12163
error appears to be "ERROR_INTERNET_DISCONNECTED", which is interpreted
as "possibly working offline." A link from one of these references
points to a Micosoft MSDN page that lists the errors by name, not
number, and provides confirmation of that interpretation:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wininet/wininet/wininet_errors.asp

So, Dogsofdeep, we're back to not having a solution to your problem. My
guess is that there's something up with your connection to the Internet.
What type of connection is is? Are you using any special software to
help you get connected or stay connected? Are you using any software
meant to speed up your Internet connection? Is there any other software
running in the background, including systray items like Kazaa, or
Morpheus, or other tools that rely on an Internet connection?

Bottom line is that the 12163 error isn't caused by the renamed
index.html file. There's something else going on, most likely
attributable to your Internet connection.

- Orest