This topic is locked

Install Problem

3/15/2008 8:31:30 AM
ASPRunnerPro General questions
D
dcihon author

I am having problems getting any version of ASPRunnerPro installed and running.

I have a Vista 64bit business OS.

I am trying this with Version 5.1 at the moment.

It seems to install without any problems.

When I got to run it it starts fine.

When I attempt to open a Access Database with it, it does a hard crash and exits the program.

I have uninstall and reinstalled several times.

I have tried to run as administrator - no luck.

I have tried to run in XP compatibility mode no luck.

I am out of ideas.

Hope someone has one here.

Thanks

Dan

W
Wazup 3/15/2008

I am having problems getting any version of ASPRunnerPro installed and running.

I have a Vista 64bit business OS.

I am trying this with Version 5.1 at the moment.

It seems to install without any problems.

When I got to run it it starts fine.

When I attempt to open a Access Database with it, it does a hard crash and exits the program.

I have uninstall and reinstalled several times.

I have tried to run as administrator - no luck.

I have tried to run in XP compatibility mode no luck.

I am out of ideas.

Hope someone has one here.

Thanks

Dan


Ah yes, Windows BUSTA!
You didn't mention what DB product you are using, makes it hard to help. Also, don't know if your using a User DSN (these cause problems - only visible to logged in user), File DSN or System DSN.
There are known issues with ODBC in Vista. Check out some of the MS NGs for a lot more intel, but here are a few links that may help:

  1. http://www.windowshelp.microsoft.com/Windo...7509401033.mspx (Look at POOLING),
  2. Some info regarding MS SQL in Vista. http://www.microsoft.com/sql/prodinfo/prev...l_on_vista.mspx,
    Big Tip:Try using a query in Query Analyzer. If that works then you have a definite ODBC issue (Query Analyzer uses Named Pipes - NOT ODBC).
    Try these as well:
  3. When you set up your DSN, make sure that you click "Test...",
  4. Try using the Trace Feature,
  5. If using MS SQL, create a Specific account for SQL. Add the account to Administrators ANDPower Users (security glitch with Vista),
  6. Do you use SQL or Integrated authentication? Try using NATIVE SQL SA first, if that works, then create a ROLE for logging into the DB. Try NOT to use the NT Administrator account,
  7. Try using the SQL Debugger account. Make sure that you set the account password first,
  8. Check the Event Log for any SQL errors. look for error 19011 (SuperSocket info: (SpnRegister) : Error 1355. This basically means that the SQL account used to start SQL is NOT part of a trusted domain/connection.
    If Query Analyzer works, try upgrading the ODBC driver. Google the interweb for something like: Vista ODBC drivers for YOUR DB SYSTEM(ex: MySQL 5.1).
    That's about it for now. ODBC is actually quite stable but in Vista, Microsoft decided to use security tokens for the ODBC connection. Review the articles in Link #2 above.
    Sorry, without more intel, can't help more.

D
dcihon author 3/15/2008

First thanks for helping me. I think this is going to take awhile before we get this fixed. So please be patient with me.

I am trying to use an Access Database with ASPRunner.

I went to your first link and here is what has happened.

When I go to control panel > Additional options there is no Data Sources (ODBC) to click on. Where do I find it?
How do I add a data source and driver to my computer?

Follow these steps:



  1. Open ODBC data source administrator by clicking the Start button Picture of the Start button, clicking Control Panel, clicking Additional Options, and then clicking Data Sources (ODBC).‌


  2. Click Add, choose the appropriate driver for the data source you're adding, and then click Finish.


  3. In the Data Source Name box, type a name for the data source (for example, you could type FileMaker). You can also type a description to help you remember why you are using this data source.


    Ah yes, Windows BUSTA!
    You didn't mention what DB product you are using, makes it hard to help. Also, don't know if your using a User DSN (these cause problems - only visible to logged in user), File DSN or System DSN.
    There are known issues with ODBC in Vista. Check out some of the MS NGs for a lot more intel, but here are a few links that may help:

  1. http://www.windowshelp.microsoft.com/Windo...7509401033.mspx (Look at POOLING),
  2. Some info regarding MS SQL in Vista. http://www.microsoft.com/sql/prodinfo/prev...l_on_vista.mspx,
    Big Tip:Try using a query in Query Analyzer. If that works then you have a definite ODBC issue (Query Analyzer uses Named Pipes - NOT ODBC).
    Try these as well:
  3. When you set up your DSN, make sure that you click "Test...",
  4. Try using the Trace Feature,
  5. If using MS SQL, create a Specific account for SQL. Add the account to Administrators ANDPower Users (security glitch with Vista),
  6. Do you use SQL or Integrated authentication? Try using NATIVE SQL SA first, if that works, then create a ROLE for logging into the DB. Try NOT to use the NT Administrator account,
  7. Try using the SQL Debugger account. Make sure that you set the account password first,
  8. Check the Event Log for any SQL errors. look for error 19011 (SuperSocket info: (SpnRegister) : Error 1355. This basically means that the SQL account used to start SQL is NOT part of a trusted domain/connection.
    If Query Analyzer works, try upgrading the ODBC driver. Google the interweb for something like: Vista ODBC drivers for YOUR DB SYSTEM(ex: MySQL 5.1).
    That's about it for now. ODBC is actually quite stable but in Vista, Microsoft decided to use security tokens for the ODBC connection. Review the articles in Link #2 above.
    Sorry, without more intel, can't help more.

W
Wazup 3/15/2008

Once you are in ODBC administrator (connection manager - depending on the OS), click on the System DSN tab. Click Add, then scroll down to Microsoft Access Driver (*.MDB).
Click on Finish, then you will be presented with another dialog box. In this dialog box, navigate to your Access DB. Select it and you will return to ODBC connection Manger (or admin depending on the OS).
Then you should be good to go.

Sergey Kornilov admin 3/15/2008

First step - install and use ASPRunnerPro 5.2.
Second step - make sure you have ODBC drivers for MS Access 2007 installed:

http://www.microsoft.com/downloads/details...;displaylang=en

W
Wazup 3/15/2008

First step - install and use ASPRunnerPro 5.2.

Second step - make sure you have ODBC drivers for MS Access 2007 installed:

http://www.microsoft.com/downloads/details...;displaylang=en


Installed ASPrunner 5.1 with access 2K7 on Vista - worked fine out of the box - no tweaking, no mess.
Link for the Access driver was discussed and referrenced in one of my links

D
dcihon author 3/15/2008

Sergey,

I did as you suggested. What is happening is I open the database and I get an error box that is from Microsoft Visual C++ Runtime Library. I don't know why I am getting that I don't have any C++ installed or ever have that I am aware of.

The box says Runtime Error!

Also I have a Name and Code for 5.1 but not for 5.2.

Thanks

Dan Cihon my order number was

Order Number 05092007-67294-1545 (DSS479370477171SSD)

First step - install and use ASPRunnerPro 5.2.

Second step - make sure you have ODBC drivers for MS Access 2007 installed:

http://www.microsoft.com/downloads/details...;displaylang=en

Sergey Kornilov admin 3/16/2008

Dan,
you need to contact support team directly for all license related questions.

D
dcihon author 3/16/2008

OK I got past the install and running problem.

Now when I go to build the pages I get

HTTP Error 404.3 - Not Found

Error Code: 0x800070032
Thanks

D
dcihon author 3/17/2008

OK the latest is error is this one when I go to View in Browser
ADODB.Connection error '800a0e7a'
Provider cannot be found. It may not be properly installed.
/include/dbcommon.asp, line 121

Sergey Kornilov admin 3/17/2008

I guess driver for MS Access 2007 is not installed properly.
I recommend to upload your application to Demo Account.

If it works there that means your web server is not configured properly.

D
dcihon author 3/22/2008

I finally found the fix for my problem.

Here it is:
http://brh.numbera.com/blog/index.php/2007...s7-on-vista-x64
Thanks for all the help from everyone.

This forum has been a great help to me when I have had a problem.