WSIT
asked on
Office 2003 Service Pack 3 Problems
Hi All
We use a Access front end back end application in our office.
On one computer we have had Office 2003 SP3 installed and now certain functions that have always worked, fail.
If i debug the code it hits an 'End Sub' on the openform event then crashes.
This has also occured at 2 of clients, so it appears to be not just a coincidence, but our software worked fine before sp3 was applied.
Event log records the following
Event Type: Error
Event Source: Microsoft Office 11
Event Category: None
Event ID: 1000
Date: 03/10/2007
Time: 15:43:14
User: N/A
Computer: WSCS001
Description:
Faulting application msaccess.exe, version 11.0.8166.0, stamp 46437912, faulting module ntdll.dll, version 5.1.2600.2180, stamp 411096b4, debug? 0, fault address 0x00010de3.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 00 70 00 70 00 6c 00 A.p.p.l.
0008: 69 00 63 00 61 00 74 00 i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00 i.o.n. .
0018: 46 00 61 00 69 00 6c 00 F.a.i.l.
0020: 75 00 72 00 65 00 20 00 u.r.e. .
0028: 20 00 6d 00 73 00 61 00 .m.s.a.
0030: 63 00 63 00 65 00 73 00 c.c.e.s.
0038: 73 00 2e 00 65 00 78 00 s...e.x.
0040: 65 00 20 00 31 00 31 00 e. .1.1.
0048: 2e 00 30 00 2e 00 38 00 ..0...8.
0050: 31 00 36 00 36 00 2e 00 1.6.6...
0058: 30 00 20 00 34 00 36 00 0. .4.6.
0060: 34 00 33 00 37 00 39 00 4.3.7.9.
0068: 31 00 32 00 20 00 69 00 1.2. .i.
0070: 6e 00 20 00 6e 00 74 00 n. .n.t.
0078: 64 00 6c 00 6c 00 2e 00 d.l.l...
0080: 64 00 6c 00 6c 00 20 00 d.l.l. .
0088: 35 00 2e 00 31 00 2e 00 5...1...
0090: 32 00 36 00 30 00 30 00 2.6.0.0.
0098: 2e 00 32 00 31 00 38 00 ..2.1.8.
00a0: 30 00 20 00 34 00 31 00 0. .4.1.
00a8: 31 00 30 00 39 00 36 00 1.0.9.6.
00b0: 62 00 34 00 20 00 66 00 b.4. .f.
00b8: 44 00 65 00 62 00 75 00 D.e.b.u.
00c0: 67 00 20 00 30 00 20 00 g. .0. .
00c8: 61 00 74 00 20 00 6f 00 a.t. .o.
00d0: 66 00 66 00 73 00 65 00 f.f.s.e.
00d8: 74 00 20 00 30 00 30 00 t. .0.0.
00e0: 30 00 31 00 30 00 64 00 0.1.0.d.
00e8: 65 00 33 00 0d 00 0a 00 e.3.....
We use a Access front end back end application in our office.
On one computer we have had Office 2003 SP3 installed and now certain functions that have always worked, fail.
If i debug the code it hits an 'End Sub' on the openform event then crashes.
This has also occured at 2 of clients, so it appears to be not just a coincidence, but our software worked fine before sp3 was applied.
Event log records the following
Event Type: Error
Event Source: Microsoft Office 11
Event Category: None
Event ID: 1000
Date: 03/10/2007
Time: 15:43:14
User: N/A
Computer: WSCS001
Description:
Faulting application msaccess.exe, version 11.0.8166.0, stamp 46437912, faulting module ntdll.dll, version 5.1.2600.2180, stamp 411096b4, debug? 0, fault address 0x00010de3.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 00 70 00 70 00 6c 00 A.p.p.l.
0008: 69 00 63 00 61 00 74 00 i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00 i.o.n. .
0018: 46 00 61 00 69 00 6c 00 F.a.i.l.
0020: 75 00 72 00 65 00 20 00 u.r.e. .
0028: 20 00 6d 00 73 00 61 00 .m.s.a.
0030: 63 00 63 00 65 00 73 00 c.c.e.s.
0038: 73 00 2e 00 65 00 78 00 s...e.x.
0040: 65 00 20 00 31 00 31 00 e. .1.1.
0048: 2e 00 30 00 2e 00 38 00 ..0...8.
0050: 31 00 36 00 36 00 2e 00 1.6.6...
0058: 30 00 20 00 34 00 36 00 0. .4.6.
0060: 34 00 33 00 37 00 39 00 4.3.7.9.
0068: 31 00 32 00 20 00 69 00 1.2. .i.
0070: 6e 00 20 00 6e 00 74 00 n. .n.t.
0078: 64 00 6c 00 6c 00 2e 00 d.l.l...
0080: 64 00 6c 00 6c 00 20 00 d.l.l. .
0088: 35 00 2e 00 31 00 2e 00 5...1...
0090: 32 00 36 00 30 00 30 00 2.6.0.0.
0098: 2e 00 32 00 31 00 38 00 ..2.1.8.
00a0: 30 00 20 00 34 00 31 00 0. .4.1.
00a8: 31 00 30 00 39 00 36 00 1.0.9.6.
00b0: 62 00 34 00 20 00 66 00 b.4. .f.
00b8: 44 00 65 00 62 00 75 00 D.e.b.u.
00c0: 67 00 20 00 30 00 20 00 g. .0. .
00c8: 61 00 74 00 20 00 6f 00 a.t. .o.
00d0: 66 00 66 00 73 00 65 00 f.f.s.e.
00d8: 74 00 20 00 30 00 30 00 t. .0.0.
00e0: 30 00 31 00 30 00 64 00 0.1.0.d.
00e8: 65 00 33 00 0d 00 0a 00 e.3.....
We are having not quite the same issue at my office but we are having some odd issues with Outlook Calendar entries disappearing about 30 seconds to a minute after they are created. This issue only seems to crop up on workstations that are running Outlook 2003 in Cached mode and have been upgraded to SP3. They would also get an entry in their "Sync Issues" folder relating to that calendar entry and a security warning.
Sadly roll back is not an option and re-install of office with SP 2 is a bad deal too for some folks.
I attempted to re-produce the issue on my system and found I could not. The only appreciable difference in our accounts is I'm a Domain Admin
After some digging I found an article on Microsoft's site which reports certain Registry keys which are supposed to be created with the install of O2K SP3 which you will need to change to disable the new "security features either on an app by app basis or disable the feature completely to save you the time of digging.
See - http://support.microsoft.com/kb/938814/ for details.
As our GPO restricts the Users from modifying their system registry or even running regedit, as a quick and dirty test I dropped the user's account into the Domain Admins group and had them log out and back in. The registry keys were not there so just for kicks I asked them to create a calendar entry. They could create calendar entries that remained in their calendar. While the user was logged on I removed their account form the Domain Admins group and had them log out and back in again. Their calendar entries kept and have done so since Monday afternoon.
I know this is thread is regarding an Access issue but I'm wondering if either of those options would work for you or would even be viable.
Let me know how it works out.
--------------------------
"Just because you're paranoid doesn't mean they aren't all out to get you."
Sadly roll back is not an option and re-install of office with SP 2 is a bad deal too for some folks.
I attempted to re-produce the issue on my system and found I could not. The only appreciable difference in our accounts is I'm a Domain Admin
After some digging I found an article on Microsoft's site which reports certain Registry keys which are supposed to be created with the install of O2K SP3 which you will need to change to disable the new "security features either on an app by app basis or disable the feature completely to save you the time of digging.
See - http://support.microsoft.com/kb/938814/ for details.
As our GPO restricts the Users from modifying their system registry or even running regedit, as a quick and dirty test I dropped the user's account into the Domain Admins group and had them log out and back in. The registry keys were not there so just for kicks I asked them to create a calendar entry. They could create calendar entries that remained in their calendar. While the user was logged on I removed their account form the Domain Admins group and had them log out and back in again. Their calendar entries kept and have done so since Monday afternoon.
I know this is thread is regarding an Access issue but I'm wondering if either of those options would work for you or would even be viable.
Let me know how it works out.
--------------------------
"Just because you're paranoid doesn't mean they aren't all out to get you."
ASKER
Well i figured it out.
Its to do with combo boxes. to save having to write multiple queries we just based a combo box on an existing query or table, if that combo box was selected with more than 24 fields then it crashes.
not sure if this is a bug or by design but by just using the correct fields it works fine.
Its to do with combo boxes. to save having to write multiple queries we just based a combo box on an existing query or table, if that combo box was selected with more than 24 fields then it crashes.
not sure if this is a bug or by design but by just using the correct fields it works fine.
Interesting, imgir - I'll bear that in mind.
WSIT - as you figured it out yourself, you can ask Community Support to PAQ and refund the points for this question. Personally, I'd prefer this question to be closed rather than deleted, because of the usefulness of imgir's comment above.
jaynee
WSIT - as you figured it out yourself, you can ask Community Support to PAQ and refund the points for this question. Personally, I'd prefer this question to be closed rather than deleted, because of the usefulness of imgir's comment above.
jaynee
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Faulting application msaccess.exe, version 11.0.8166.0, stamp
http://news.office-watch.com?555