|
Buy Support
Incidents |
|
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
|
Click Here
|
If you can't
login and post questions or you are having trouble viewing forum posts:
Click Here
|
Callback
Support |
|
If you live in USA, UK, Canada, Australia or New
Zealand, you can leave us details on your question and request us to call you back and discuss
them with you personally (charges apply). |
|
Click Here
|
Buy Support
Incidents |
|
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
|
Click Here
|
|
| Remote Connector crashing IIS on Windows XP Professional |
| Author |
Message |
| jeff |
| |
| Group | : Members |
| Posts | : 76 |
| Joined | : 2006-06-03 |
|
| Profile |
|
| Posted : 2006-08-31 09:56:41 |
My Environment: Windows Xp Pro, IIS 5.0 and QB 2006 Pro.
I am using the Remote Connector to enable IIS to connect to QB. My web server is on the same machine as the Remote Connector and the QB. I have attempted to use the DCOM Server but all attempts to make that work with my web application have failed. (By the way, using the Remote Connector also fixes my ASP.net applications, that give DCOM instance errors when attempt ing to connect using DCOM Server option.) If I use the remote connector the application can make successful connections. The problem is that the Remote Connector randomly crashes IIS. Here is the event log message:
Faulting application inetinfo.exe, version 5.1.2600.2180, faulting module ibizqb3.dll, version 3.1.1934.0, fault address 0x0003baa6.
|
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-08-31 10:10:55 |
The Windows XP Professional O/S is not a web server. While you can use it as a web developement test server, Microsoft have internally limited IIS so it cannot be used as a production web server. It's normal for IIS to choke when you push it with too many connections or complex tasks. You then restart the O/S and things that failed a minute ago suddenly work again no problems without having to change anything.
Regardless whether you use the Remote Connector or the DCOMs, you can only run a small amount of web tasks using Windows XP Professional. |
|
|
|
|