When loading the SEED folder in the Safe X3 management console, I get the error: Login failed for user 'SEED'.: Erreur SQL Server. There was no opportunity to setup anything for this user, so I don't know how to make it install properly. It went on to say it was completed but it received errors in the trace and the folder was not created when it finished. Anyone else seen this?
Kelly Hamann
I know the technical reason why you are getting the error, perhaps it will give you a clue to help move the story forward, not sure. Here it goes:
I mentioned this up front, but it bears repeating. The account that you have set in the console is important here as it seems the script we use to create all the database objects isn't completing. So, ensure that you are using the sa or equivalent account for this process for now.
Having said that, you should examing where in the process it failed by first looking at the security. In SQL you should see a login for the X3 user. That login is tied to a database user, role and schema. If you don't have the X3 user on your server then it could mean that you also don't have the schema, or the database roles that you should have. This is what you can check first.
To check if you have the server login:
SELECT principal_id, name, type_desc, is_disabled, create_date, default_database_name
FROM sys.server_principals
WHERE name = 'X3'
To check if you have the database user and the roles:
SELECT name, authentication_type, create_date, type_desc, default_schema_name
FROM sys.database_principals
WHERE name LIKE 'X3%'
To augment the discussion even further you can find the scripts we user to create the role, database, users and in the <drive>\sage\sagex3v7\x3runtime\runtime\tmp directory. The script in question for you is the adcrapss7_x3.sql script. I think when it ran it must have failed for you at some point. If you open the script up it will become evident why it is critical as it links everything together from a security standpoint.
Also, my experience with troubleshooting these kinds of things is that you should troubleshoot the first error you get first. So, in your case, learning why the table you mentioned before didn't load into the database correctly is going to be crucial to the overall health. You might try and isolate load process, mimic it and decipher the root cause.
Hope this helps.
It will not let me login to Management Studio:
Is that what you meant?
Kelly
