Runtime error 214721783(80040e4d) Authentication failed [Resolved]

Anytime I run my app on a win2k machine I get a "runtime error 214721783(80040e4d) Authentication failed"

Any thoughts?

Could it be the XP Manifest?

Did you use an installer, or did you just copy some files?

1st i tried just running the .exe from that machine, and I got the error so I used the package and deployment app and then ran an install on the machine.

bump.

Ok, it is "shot in the dark time"

Could it have anything to do with the account that is logged into the machine, and that accounts inability to authenticate to whatever it is that has to be authenticated to?

Quote:

---

Originally Posted by Hack

Ok, it is "shot in the dark time"

Could it have anything to do with the account that is logged into the machine, and that accounts inability to authenticate to whatever it is that has to be authenticated to?

---

I dont think so... I've never seen that error before on that machine, and the user does have admin rights.

Quote:

---

Originally Posted by DKasler

I dont think so... I've never seen that error before on that machine, and the user does have admin rights.

---

Well, I wasn't puttin' a whole lotta faith in that one anyway, but ya never know.

Is this happening on ALL Win2K machines?

Does it work on all XP machines?

What does your app do? Does it run at all or crash with that error when you do something?

Quote:

---

Originally Posted by RobDog888

What does your app do? Does it run at all or crash with that error when you do something?

---

The error that is being generated is the runtime error in the thread title.

My money was on user rights. 2nd guess would have to be Crystal.
Would you be using Crystal Reports? (Although it used to come with NT)

Well a runtime error is basically an unhandled error that could be invoked either at startup or during some program action
where there is no error handling. ;)

As far as I can tell it runs fine on all 2 XP machines I tried it on. (It was created on 1 of them)

It has happened on both 2k machines I tried it on. Both times I used the package and deployment wizard install.

Quote:

---

Originally Posted by RobDog888

What does your app do? Does it run at all or crash with that error when you do something?

---

Soon as you click the Icon to run the app the error pops up. The splash screen doesnt even open

Im wondering it it has something to do with the XP Manifest being added by VB Advance. Then again... If im dont compile the .exe using the VBAdvance compile then it shouldnt be adding an xp manifest... I dont think.

Yes, that is an issue if you do not have a proper manifest file. Take the manifest file out of that directory and test your app. If it runs
then you may not have a correct file. Did you enter the correct data in it for app name, etc.

Although I dont see why it would be specific to Win2k?

Whats VBAdvance ?

Quote:

---

Originally Posted by RobDog888

Yes, that is an issue if you do not have a proper manifest file. Take the manifest file out of that directory and test your app. If it runs
then you may not have a correct file. Did you enter the correct data in it for app name, etc.

Although I dont see why it would be specific to Win2k?

Whats VBAdvance ?

---

VBAdvance basically writes the xp manifest right into the app. So you dont have to copy the file to a machine after you run the setup. Since package and deployment wont install it with the exe.

Even without the manifest, the same thing seems to be happening.

I've tried all of the following:

-Compling P-Code
-Compling Native Code
-W/ XP Manifest from VBAdvance
-W/ Out XP Manifest from VBAdvance

I cant think of anything else...

You can add extra files to the P&D Wiz. You just need to clikc Add and browse to the location of your file.

Do you have any error handling in your form load procedure?

What does your app do? Could you be missing a dependancy file(s).

I bet you compiled on an XP system?

It could be an MDAC version issue if your app is using it.

Quote:

---

Originally Posted by RobDog888

You can add extra files to the P&D Wiz. You just need to clikc Add and browse to the location of your file.

Do you have any error handling in your form load procedure?

What does your app do? Could you be missing a dependancy file(s).

I bet you compiled on an XP system?

It could be an MDAC version issue if your app is using it.

---

1. Thanks for the tip about adding other files to the P&D Wiz.

2. The app is basically a Supplies DB app for our office.

None of the controls are custom. They are all VB supplied. Labels, Txtboxes, combo boxes, dtpicker, command buttons, images, and mshflexgrids

3. No, I dont currently have any error handling for my form load procedure. Any suggestions?

4. Yes I complied it on an XP system. Unfortunately I dont have VB installed on any of our 2k Machines. They belong to other users so long term access to them is somewhat of a hassle. :(

Ok, if you have your code connecting to your db in the form_load event it could be that the systems dont have MDAC installed so the
connection will fail and error. It could also be that XP is using MDAC 2.7 or XP SP2 uses 2.8. This version conflict could also cause issues if
your not distributing MDAC.

I would first reccommend downloading the Component Checker from MS. It will tell you if MDAC is installed and the version.

Then I would add error handling and line numbers to your form load event so you can pinpoint the error if its not MDAC.

Quote:

---

Originally Posted by RobDog888

Ok, if you have your code connecting to your db in the form_load event it could be that the systems dont have MDAC installed so the
connection will fail and error. It could also be that XP is using MDAC 2.7 or XP SP2 uses 2.8. This version conflict could also cause issues if
your not distributing MDAC.

I would first reccommend downloading the Component Checker from MS. It will tell you if MDAC is installed and the version.

Then I would add error handling and line numbers to your form load event so you can pinpoint the error if its not MDAC.

---

Thanks for the Help RobDog. I'll look into that now.

Im also running windows updates on 1 of the 2 win2k machines to see if that makes any difference.

Ok.. I have run the Component Checker on my machine and 1 of the win2k machines.

Win2k Machine: 2.5sp3
WinXp Machine: 2.8sp1 on XP SP2

So how can I work around this?

You can download MDAC from MS and upgrade the 2k machines but you should only do this after determining if it is nothing else first.

Add line numbers in your form load event and error handling like this.
Code is for display example only!

VB Code:

Private sub form_load()
 
    On error goto MyError
 
100 Set rs = new adodb.recordset
110 rs.open "SELECT * FROM Table1"
120 '...
130 '... etc.
 
    Exit Sub
MyError:
    MsgBox err.number & " - " & err.description, vbOkOnly + vbExclamation, "Form_Load: " & erl
End Sub

Ok.. This seems to be the line causing the error: dfwConn.Open sconnect

The error message indicated line 127 as the problem

VB Code:

100 Check1.Value = GetSetting(App.Title, Me.Name, "LocationCheck", Check1.Value)
101 Text1.Text = GetSetting(App.Title, Me.Name, "Location", Text1.Text)
102 Text2.Text = GetSetting(App.Title, Me.Name, "Location2", Text2.Text)
103 Option1.Value = GetSetting(App.Title, Me.Name, "OurBrowser", Option1.Value)
104 Option2.Value = GetSetting(App.Title, Me.Name, "DefBrowser", Option2.Value)
105 Drive1.Drive = GetSetting(App.Title, Me.Name, "DRIVE", Drive1.Drive)
106 Dir1.Path = GetSetting(App.Title, Me.Name, "DIRECTORY", Dir1.Path)
107 File1.FileName = GetSetting(App.Title, Me.Name, "FILE", File1.FileName)
 
108    Data1.DatabaseName = frmLocation.Text1.Text
109    Data1.Refresh
    
110    SSTab1.Tab = 0
 
111 If Me.Check1.Value = vbChecked Then
112 Me.Visible = False
113 frmLocation.Text1.Text = Me.Text1.Text
114 frmLocation.Text2.Text = Me.Text2.Text
115 FrmSplash.Show
116 Else
117 frmLocation.Text1.Text = Me.Text1.Text
118 frmLocation.Text2.Text = Me.Text2.Text
119 End If
 
120    Dim sconnect As String
121    Dim sSQL As String
122    Dim dfwConn As adodb.Connection
123    Dim datPrimaryRs
 
    ' set strings
124    sconnect = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source='" & frmLocation.Text1.Text & "';Persist Security Info=False"
125    sSQL = "select PurchaserName from Purchaser ORDER by PurchaserName"
    ' open connection
126    Set dfwConn = New adodb.Connection
127    dfwConn.Open sconnect
 
    ' create a recordset using the provided collection
128    Set datPrimaryRs = New adodb.Recordset
129    datPrimaryRs.CursorLocation = adUseClient
130    datPrimaryRs.Open sSQL, dfwConn, adOpenForwardOnly, adLockReadOnly
    
131    Combo1.Clear
132    While Not datPrimaryRs.EOF
133        Combo1.AddItem (datPrimaryRs("PurchaserName"))
134        datPrimaryRs.MoveNext
135    Wend

Now... If thats an MDAC issue... I have to manually install the newer version any win2k machine I want to put my application on? Or is there a way to add the MDAC update into the install process?

What procedure and form is this code from?

Is frmLocation.Text1.Text populated? If so whats the value.

sconnect = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source='" & frmLocation.Text1.Text & "';Persist Security Info=False"
should be...
sconnect = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & frmLocation.Text1.Text & ";Persist Security Info=False"
No single quotes surrounding the datasource is needed.

Do you have a user id and password needing to be passed in order to open your db?

Quote:

---

Originally Posted by RobDog888

What procedure and form is this code from?

Is frmLocation.Text1.Text populated? If so whats the value.

sconnect = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source='" & frmLocation.Text1.Text & "';Persist Security Info=False"
should be...
sconnect = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & frmLocation.Text1.Text & ";Persist Security Info=False"
No single quotes surrounding the datasource is needed.

Do you have a user id and password needing to be passed in order to open your db?

---

The 1st time the app is run, the config screen should load an allow the user to choose the location of the DB, click the "Dont show form" check box. Then save the settings to the registry...

After that the config form should load, but now show calling the db location from the registry using Text1.Text = GetSetting(App.Title, Me.Name, "Location", Text1.Text) and passing it to FrmLocation.Text1.Text a little later.

I know its sloppy... but its the only way I could think of doing it, so every user could choose the drive where the DB is located.

So does the choose db location form show at all on first run on the troubled systems?

Ok.. Im an idiot. I got it all worked out now.

Thanks RobDog.

I added a "If frmLocation.Text1.Text = "" Then GoTo NoLocation" line to bypass the SQL code if the info for the db location has never been entered.

Thanks for your help, I really appreciate it.

Always glad to help. It keeps me sharp covering all kinds of topics. ;)

See, now if you installed MDAC on the two 2k systems then that wouldnt have fixed the problem. Patience young grasshopper. :D

Go with the path of least resistance. :)