Hello,
You may should better contact the support of the software vendor to get assistance.
Anyway, what have you already tried, are you getting an error message and if so, which one?
Hi djinstructor,
Based on my research, GoldMine can create a new database or connect to existing database(depends on your choice) when installing GoldMine. During the next step, you need to provide a user that can connect to the database and has the right permissions. For more
details, please review this
guide.
Also as other post, it is better to post the question in the
GoldMine forum .
There is a similar thread for your reference.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/cb91d16f-0386-45d1-a405-a272e97fa819/goldmine-sql-express-problem?forum=sqlgetstarted
Thanks,
Lydia
Thank you Lydia. I have posted in that forum with no response. I did find that thread, but that individual appears to have been able to install Goldmine. I can't install it. I get this error, but I don't know why:
"SQLState = 42000, Native Error = 18456, Description = Login failed for user 'administrator'."
- Edited by djinstructor 18 hours 12 minutes ago
Hello,
When you are installing Goldmine is very important to take in consideration the operating system and the SQL Server version.
For example, if you are installing on Windows Server 2008 you cannot use SQL Server Express for Goldmine 2014.
What version of SQL Server you are using? SQL Server 2008 and SQL Server 2008 R2, both with no service packs, are the recommended
options. Goldmine 2014 also supports SQL Server 2008 SP2, SQL Server 2008 R2 SP1 and SQL Server 2012 (no service pack).
Please examine the Summary.txt log file created by SQL Server setup to make sure SQL Server was successfully created.
Make sure you have enabled TCP/IP and Named Pipes protocols after installation.
https://technet.microsoft.com/en-us/library/ms191294(v=sql.110).aspx
Configure Windows Firewall for SQL Server access.
https://msdn.microsoft.com/en-us/library/Cc646023(v=sql.110).aspx
To troubleshoot error 18456, please read the following resources:
http://blogs.msdn.com/b/sql_protocols/archive/2006/02/21/536201.aspx?PageIndex=7
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
- Edited by Alberto MorilloMVP, Moderator 16 hours 19 minutes ago
Thanks Alberto. My predecessor installed SQL Server 2012 successfully back in October. It has SP2. I have enabled the TCP/IP and Named Pipes protocols and configured Windows Firewall for SQL Server access.
I'm not familiar enough with SQL to follow all the troubleshooting procedures on the blog though.
Thank you Lydia. I have posted in that forum with no response. I did find that thread, but that individual appears to have been able to install Goldmine. I can't install it. I get this error, but I don't know why:
"SQLState = 42000, Native Error = 18456, Description = Login failed for user 'administrator'."
- Edited by djinstructor Friday, May 29, 2015 12:53 PM
Hello,
Please examine the SQL Server Error log and look for Error 18456 Login Failed. Share with us the State number of those
errors. That state number will give us the cause of the login fail as explained on the blog post I shared with you.
https://msdn.microsoft.com/en-us/ms187109.aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Hello,
When you are installing Goldmine is very important to take in consideration the operating system and the SQL Server version.
For example, if you are installing on Windows Server 2008 you cannot use SQL Server Express for Goldmine 2014.
What version of SQL Server you are using? SQL Server 2008 and SQL Server 2008 R2, both with no service packs, are the recommended
options. Goldmine 2014 also supports SQL Server 2008 SP2, SQL Server 2008 R2 SP1 and SQL Server 2012 (no service pack).
Please examine the Summary.txt log file created by SQL Server setup to make sure SQL Server was successfully created.
Make sure you have enabled TCP/IP and Named Pipes protocols after installation.
https://technet.microsoft.com/en-us/library/ms191294(v=sql.110).aspx
Configure Windows Firewall for SQL Server access.
https://msdn.microsoft.com/en-us/library/Cc646023(v=sql.110).aspx
To troubleshoot error 18456, please read the following resources:
http://blogs.msdn.com/b/sql_protocols/archive/2006/02/21/536201.aspx?PageIndex=7
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
- Edited by Alberto MorilloMVP, Moderator Friday, May 29, 2015 2:46 PM
I'm not sure if this is the correct log, but I looked here (C:\Program Files\Microsoft SQL Server\MSSQL11.SQLSERVER\MSSQL\Log\errorlog) and found this:
2015-05-29 11:08:12.19 Logon Error: 18456, Severity: 14, State: 38.
2015-05-29 11:08:12.19 Logon Login failed for user 'NT SERVICE\ReportServer$SQLSERVER'. Reason: Failed to open the explicitly specified database 'ReportServer$SQLSERVER'. [CLIENT: <local machine>]
2015-05-29 11:08:15.98 Logon Error: 18456, Severity: 14, State: 38.
2015-05-29 11:08:15.98 Logon Login failed for user 'NT SERVICE\ReportServer$SQLSERVER'. Reason: Failed to open the explicitly specified database 'ReportServer$SQLSERVER'. [CLIENT: <local machine>]
2015-05-29 11:08:21.91 Logon Error: 18456, Severity: 14, State: 38.
2015-05-29 11:08:21.91 Logon Login failed for user 'NT SERVICE\ReportServer$SQLSERVER'. Reason: Failed to open the explicitly specified database 'ReportServer$SQLSERVER'. [CLIENT: <local machine>]
Thanks for your help.
2015-05-29 11:08:21.91 Logon Error: 18456, Severity: 14, State: 38.
2015-05-29 11:08:21.91 Logon Login failed for user 'NT SERVICE\ReportServer$SQLSERVER'. Reason: Failed to open the explicitly specified database 'ReportServer$SQLSERVER'. [CLIENT: <local machine>]
Hi djinstructor,
According to above error message, the issue could occur if the 'ReportServer$SQLSERVER' database is offline, shutdown, deleted, dropped, renamed, auto-closed, or inaccessible. It could also be due to that the user 'NT SERVICE\ReportServer$SQLSERVER' has
no permission for the database.
To overcome this error, please check the database state and the user permission.
For more details about the error, please review the following blog.
Troubleshooting Error 18456
SQL Server Error 18456: Finding the Missing Databases
Thanks,
Lydia Zhang