Having an issue with SRM5.0.1 and the database. I run the install and everything is going fine when it stops and I get the following error:
My ODBC setup is correct and the dtatbase is setup according to the documentation.
Any help would be appreciated.
Tom
Not sure how your ODBC connection is set up but you can start here.
Is SQL instance local to SRM? Make usre you are not using Windows Authentication.
Thanks for the replies.
This is happening on both servers. One has the database on the same server and one has the database on a separate server. In both cases the db users are local sql and have all the correct permissions.
What confuses me is that the error states C:\users\myusername\appdata\local\vmware is not a directory. Not sure why this is an issue.
Regards,
Thomas Woodhead
Windows Administrator, Operations
F 480.609.4308
5301 North Pima Road, Suite 100, Scottsdale, AZ 85250 | P 866.297.7364 | www.OneNeck.com<http://www.oneneck.com/>;
Hosted Application Management<http://oneneck.com/Solutions/HostedApplicationManagement.aspx> | Cloud Services<http://www.oneneck.com/Solutions/CloudServices.aspx> | Managed Hosting<http://www.oneneck.com/Solutions/ManagedHosting.aspx> | Infrastructure Services<http://www.oneneck.com/Solutions/InfrastructureServices.aspx>
[cid:image015.jpg@01CDD6B5.BC3336B0][cid:image016.jpg@01CDD6B5.BC3336B0][cid:image017.jpg@01CDD6B5.BC3336B0][cid:image018.jpg@01CDD6B5.BC3336B0]
Did you use a 32-bit DSN?
Run c:\windowssyswow64\odbcad32.exe and make sure your DSN is listed under system dsn.
Yup.
I fixed the issue. I don’t remember seeing that the vSphere client needed to be installed on the server, but I installed anyway, which created the vmware folder and that fixed the issue.
I fixed the issue. I don’t remember seeing that the vSphere client needed to be installed on the server, but I installed anyway, which created the vmware folder and that fixed the issue.
Tnaks for your sugeestions.
When you create your SRM DB, you need to make sure of the following:
a: it is a seperate instance if you are using a remote DB
b: the default schema of the DB is named the same as the SRM user account
c: your ODBC connection must be 32bit
it was B that caught me out.