Bonnie_K
asked on
Server.CreateObject Failed
Hello,
All of a sudden, I am getting the error below on this line of code: SET acc = Server.CreateObject("Acces
Server object error 'ASP 0177 : 8000401a'
Server.CreateObject Failed
/reports/asp/Purchasing/GR
The server process could not be started because the configured identity is incorrect. Check the username and password.
I am using integrated authentication for the website. It was working for 6 months and I don't know why it is no longer working.
Any ideas would be appreciated.
Thanks -Bonnie
All of a sudden, I am getting the error below on this line of code: SET acc = Server.CreateObject("Acces
Server object error 'ASP 0177 : 8000401a'
Server.CreateObject Failed
/reports/asp/Purchasing/GR
The server process could not be started because the configured identity is incorrect. Check the username and password.
I am using integrated authentication for the website. It was working for 6 months and I don't know why it is no longer working.
Any ideas would be appreciated.
Thanks -Bonnie
ASKER
I ran dcomcnfg and went to the Access Application. On the Identity tab, I changed it from Interactive user to a specific user.
I entered the Administrator username and password. Now it is working again.
Can I leave this setting like this? Is there any problem with it? Again, I have no idea why the interactive user is no longer working, especially since I was the user logged in and am an administrator.
I entered the Administrator username and password. Now it is working again.
Can I leave this setting like this? Is there any problem with it? Again, I have no idea why the interactive user is no longer working, especially since I was the user logged in and am an administrator.
Did anyone change the password for the user?
Cheers!!
Cheers!!
This is a bad way to do things, and Microsoft explicitly warns against it:
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q257/7/57.ASP&NoWebContent=1
Fritz the Blank
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q257/7/57.ASP&NoWebContent=1
Fritz the Blank
Dumb question maybe....have you rebooted?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Well, this morning, just for fun, I changed it back to the interactive user and it is working again. If however, it happens again, I will use frederichernry's idea which seems the safest.
Fritz - when you say a "bad way" do you mean one shouldn't use access at all with asp? I am using it to export snapshots files of reports. I am still trying to figure out different ways to get data to people over a web interface. Using asp and access is the only way I know so far. I just haven't had the opportunity to explorer other methods. If you don't mind answering, what would you use if a company wanted to look at access reports over the web?
Fritz - when you say a "bad way" do you mean one shouldn't use access at all with asp? I am using it to export snapshots files of reports. I am still trying to figure out different ways to get data to people over a web interface. Using asp and access is the only way I know so far. I just haven't had the opportunity to explorer other methods. If you don't mind answering, what would you use if a company wanted to look at access reports over the web?
Not to jump in on Fritz, but I'd recommend creating the reports yourself, and using SQL as a database backend, not Access. In the link Fritz posted, MS recommends against it simply because they do not want to support (and I don't blame them). Access is meant to be used as a desktop database application, and nothing more.
If you are in a small scale environment (-10 users) then it will probably work fine, however, if you have over that number, and they regularly interact with your application, you could run into some stability issues in Access.
That being said, you mentioned that you have run this application for some time now, and if you haven't had any of the problems listed in the KB article, you're probably fine. Scalability will not be a good friend for you though. :)
Last, MS did recommend SoftArtisans. I have used their products in the past and they're quite good. Excellent support as well.
Glad to hear that you got everything working again.
If you are in a small scale environment (-10 users) then it will probably work fine, however, if you have over that number, and they regularly interact with your application, you could run into some stability issues in Access.
That being said, you mentioned that you have run this application for some time now, and if you haven't had any of the problems listed in the KB article, you're probably fine. Scalability will not be a good friend for you though. :)
Last, MS did recommend SoftArtisans. I have used their products in the past and they're quite good. Excellent support as well.
Glad to hear that you got everything working again.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
@frederichenry--
Sorry, I posted my last comment before I saw yours (it was not a response to it, but rather to Bonnie's question).
Newer versions of Access support 25 simultaneous connections rather ably, so as long as you are careful with closing and destroying connections as quickly as possible, things work out fine. Nonetheless, you are absolutely correct in asserting that for high-traffic sites, some other more robust DBMS (SQL Server, MySQL) is the way to go.
Fritz the Blank
Sorry, I posted my last comment before I saw yours (it was not a response to it, but rather to Bonnie's question).
Newer versions of Access support 25 simultaneous connections rather ably, so as long as you are careful with closing and destroying connections as quickly as possible, things work out fine. Nonetheless, you are absolutely correct in asserting that for high-traffic sites, some other more robust DBMS (SQL Server, MySQL) is the way to go.
Fritz the Blank
ASKER
Thanks for your help and feedback. It will be very helpful to me.
Bonnie
Bonnie
ASKER
PS - we are only going to use this for about 10 users at off site locations over a vpn. I am still testing, so we'll find out how it fairs. It will probably go live in a couple of weeks.
Thanks again,
Bonnie
Thanks again,
Bonnie
I had the same problem when creating an Excel document in asp script (Set ExcelApp = Server.CreateObject("Excel
Server object error 'ASP 0177 : 8000401a'
Server.CreateObject Failed
When changing the user Administrator, it works well :
- run dcomcnfg.exe
- go to Console Root / Components Services / Computer / My Computer / DCOM Config / Application Microsoft Excel
- open properties
- go to identity tab
- change "interactive user" by "this user", and use Administrator account
I know this is a temporary modification, but know i can continue working...
Server object error 'ASP 0177 : 8000401a'
Server.CreateObject Failed
When changing the user Administrator, it works well :
- run dcomcnfg.exe
- go to Console Root / Components Services / Computer / My Computer / DCOM Config / Application Microsoft Excel
- open properties
- go to identity tab
- change "interactive user" by "this user", and use Administrator account
I know this is a temporary modification, but know i can continue working...
Cheers!!