Mapi init failure 0x80004005 on Arm64 computer
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
No files, tests, or entry points are named. Start by tracing MAPI initialization for an Arm64 app with Arm64X Outlook and compare the supported architecture combinations; done means determining whether 0x80004005 is a known limitation or identifying a reproducible fix or documented workaround.
Written by the indexing model from the issue text.
Description
My app's architecture is Arm64, Outlook's architecture is Arm64X. Mapi init always fails with error 0x80004005 in my app. Is this a known issue or a limitation?
- Dominant language
- C
- Stars
- 37
- Forks
- 24
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 5
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/MAPIStubLibrary
-
microsoft/MAPIStubLibrary#198 · 1 reaction · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
microsoft/MAPIStubLibrary#62 · 1 comment ·
All issues in microsoft/MAPIStubLibrary
Similar issues
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
hapostgres/pg_auto_failover#1190 ·
-
docs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
P3 sonic-vpp
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sonic-net/sonic-buildimage#29662 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
spack/spack-packages#6586 ·