Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

RE: CRM 3.0 Installation HRESULT: 0x80131534 error

52 views
Skip to first unread message

Mike Christl

unread,
Jul 26, 2006, 4:13:06 PM7/26/06
to
Hi and thanks for the post.

1. Is this an upgrade or a new install?
2. Was the Windows Resource Kit used to set up the daylight changes?
(TZEdit).

The following modification of the registry helped one customer to solve the
issue.
=====================================================================
Please add the following registry keys on the CRM Server:
1. Add OLEDBTimeout
Open the registry by typing Start | Run | Regedit. Navigate to HKLM |
Software |
Microsoft | MSCRM.
- Right click, select New. Create a new Reg DWORD value called
OLEDBTimeout.
- Right click and modify to change the value to 240 in hexadecimal base
(about 576
seconds).

2. Increase MaxUserPort
Click Start, click Run, type regedit in the Open box, and then click OK.
Locate and then click the following subkey:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
On the Edit menu, point to New, click DWORD Value, and then type
MaxUserPort.
Double-click MaxUserPort, and then set a decimal value to a number close to
60000.
======================================================================

If these suggestions don't help would you please send the setup logs?

Kind regards,
Mike

======================================================
PLEASE NOTE: The partner managed newsgroups are provided to assist with
break/fix issues and simple how to questions.
======================================================
We also love to hear your product feedback! Let us know what you think by
posting from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback. We
look forward to hearing from you!
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

Itay-MDG Mdical

unread,
Jul 30, 2006, 6:21:01 AM7/30/06
to
Hello Mike!
1. this is a new install.
2. yes I did use the TZedit on this server.
3. After I added the 2 keys to the registry, uninstalled CRM, restarted
the server and reinstalled CRM. I got another error message :
Action Microsoft.Crm.Setup.Server.CreateSetupUserAction failed.
Specified cast is not valid.

Here is part of the log from the first install(the whole log didn’t fit,if
you need a specific part let me know):
10:30:22| Info| Microsoft CRM 3.0 Server Setup Failed.
10:30:22| Info| Microsoft CRM 3.0 Server Setup Setup did not complete
successfully.

Action Microsoft.Crm.Setup.Server.ProvisionBusinessAction failed.
Exception from HRESULT: 0x80131534.

--
Itay - Mdg Medical

Jaden Blake [MSFT]

unread,
Aug 2, 2006, 8:38:48 AM8/2/06
to
Hello,

How many servers are you installing with?
What is on each server; CRM, SQL, AD?

Please zip and send your installation log to crm...@microsoft.com for
review.


Best Regards,

Jaden

======================================================
PLEASE NOTE: The partner managed newsgroups are provided
to assist with break/fix issues and simple how to questions.
 

CRMAdmin

unread,
Aug 18, 2006, 4:59:02 PM8/18/06
to
Was their any solution to this problem? I am getting the "Action
Microsoft.Crm.Setup.Server.CreateSetupUserAction failed." error as well at
the end of the upgrade install. After fighting with it a while it appears to
be a permissions problem moving the users in the SystemUserBase table. I'm
unable to find a fix.

Tim

unread,
Aug 22, 2006, 9:48:40 AM8/22/06
to
For us, the fix was:

After the error message go to the "OrganizationBase" table. Find the
IsRegistered field and change it from null to 1. Hit retry. Fixed.

Mike Christl

unread,
Sep 1, 2006, 5:22:53 PM9/1/06
to
Hi.
I apologize for the long delay. How is this progressing? I am guessing
that you have fixed this by now.

Thanks!

0 new messages