Error 800a01a8 object required

[Raj]

I have developed a component create database, sql login,pwd, create tables
etc.,

The component is working fine with VB

But the same is not working with ASP as I get this error: Error 800a01a8

For creating database, sql login,pwd I am using sa with a valid password.

Please advice.

Thank you,

Regards,

Raj.

 

[Raj]

Thanx indeed Job, but I have checked the link already.

Here's what I am trying exactly.

I have an application server running Windows 2003 Server with IIS 6.0 and
have a separate database server running Windows 2003 Server with MS SQL
Server 2000.

I am trying to create database, SQL login, tables from my application server
through ASP onto the database server.

Before creating the objects (database, sqllogin, tables etc.,) I check for
whether these objects exists already or not.

The database is created successfully, but SQLLogin and tables creation was
never successful.

I tried the same through VB it was successful. I tried to create all objects
on my application server itself it was successful.

I am able to connect to the database server through SQL Query Analyzer.

For all database creation and SQL Login creation I am using sa login.

Please advice

Thank you,

Regards,

Raj.

 

[Bob Barrows [MVP]]

For creating database, sql login,pwd I am using sa with a valid
password.

Jon tackled your subject problem, but I could not let this pass:
Never use the sa account in your applications. Never.
The sa is account is for System Administration. Period. The sa password
should NEVER appear in application code. It should be guarded as if your
database, server, network and job depended upon it ... it probably does.

Best practice is to create a limited-rights sql account (login) for use
in your applications. That account should have permissions for only the
tasks needed by the application. Since it appears your component is
creating a database, the account you create should be put in the
dbcreator server role.

 

[Bob Barrows [MVP]]

Thanx indeed Job, but I have checked the link already.

Here's what I am trying exactly.

I have an application server running Windows 2003 Server with IIS 6.0
and have a separate database server running Windows 2003 Server with
MS SQL Server 2000.

I am trying to create database, SQL login, tables from my application
server through ASP onto the database server.

Before creating the objects (database, sqllogin, tables etc.,) I
check for whether these objects exists already or not.

The database is created successfully, but SQLLogin and tables
creation was never successful.

I tried the same through VB it was successful. I tried to create all
objects on my application server itself it was successful.

I am able to connect to the database server through SQL Query
Analyzer.

For all database creation and SQL Login creation I am using sa login.

Please advice

Sorry, but with the information we've been given, it is impossible for
anyone to solve your problem. Someone will need to be able to run and
debug your code to do that.

 

[Raj]

Thanx for all your advice.

When I try to execute those commands (these commands I have used in the
component) directly in ASP page it works fine.

I need to know, whether I can use script encoder to encode .inc file which I
will include it in my ASP page which will do all?

The .inc file will be in location where it cannot be url downloaded

Regards,

Raj

 

[Dave Anderson]

Never use the sa account in your applications. Never.

Not even if you remove the [sysadmin] role?

It's clearly better to state that the web application should never use
credentials granted the [sysadmin] role. There is nothing special about sa
in this case.

 

[Bob Barrows [MVP]]

Thanx for all your advice.

When I try to execute those commands (these commands I have used in
the component) directly in ASP page it works fine.

I need to know, whether I can use script encoder to encode .inc file
which I will include it in my ASP page which will do all?

The .inc file will be in location where it cannot be url downloaded

Again. I haven't the slightest idea what you are talking about. What
does script encoding have to do with your problem?