10-28-2008 12:00 PM
Try these steps, let me know if it is not working.
The SQL Service Is Not Running To start the SQL Service, please use the following steps: Click the Windows® Start button and select Run. The Run dialog box appears. Type services.msc in the Open field, and then click OK. The Services Panel launches. Locate the SQL Server (ACT7) entry from the name column. Verify that the Status is listed as started. If it is started, close the Services panel and proceed to Verifying SQL Installed Properly. If it is not started, right-click on the SQL Server (ACT7) service and select Start. Close Services panel. Verifying SQL Installed Properly To verify that SQL installed properly, please use the following steps: Click the Windows Start button and select Run. The Run dialog box appears. Type actdiag in the Open field and click OK. The ACT! Diagnostics disclaimer window will appear. Click OK to proceed in to the ACT! Diagnostic. If the tool opens without any errors, close the tool and proceed to the following section, ACT! Was Not Able To Configure The ACT7 SQL Instance If you get the following error message: Click OK and proceed to the following section, Uninstalling Microsoft SQL Server 2005. ACT Was Not Able To Configure The ACT7 SQL Instance To configure the ACT7 Instance by creating a new SQL password, please use the following steps: Click the Windows Start button and select Run. The Run dialog box appears. Type cmd in the Open field, and then click OK. The Command Prompt appears. If you are not at C:\ then type cd c:\ and press Enter. Type sqlcmd -S(local)\ACT7 -E and press Enter. Type sp_password NULL, '(New Password)','sa' and press Enter. In the example below the new password is set to "bluesky", you may create a new password of you choice. Type go and press Enter. Type Exit and press Enter. Type cd C:\Program Files\ACT\Act for Windows and press Enter. Type SecurityCmdLnApp.exe "(New Password)" and press Enter. In the example below we used "bluesky" as our password, you will need to place your new password inside the quotation marks. Type Exit to close the command prompt.
10-29-2008 03:57 AM
The password doesn't have to be 'sage'. It is just a temporary password and gets reset when you connect ACT! to the SQL instance.
Its requesting a strong password, because you have a password policy set that doesn't allow simply password like 'sage'. SO you'll need to enter a password that meets your policies criteria (e.g. Sage1234!).
But there is no way to type in that password anyway. I don't specify anything, it uses what's built into the install CD.
And when telling me I should give another password, a stronger one, there is no place where I can type it in! That's what's stupid. It offers a RETRY button without letting you type anything.
But I will try to remove everything from the registry and first install MSSQL directly from the Act! CD without Act! itself, and without disabling most services at boot time (that's the only way not to be asked about that password).
10-29-2008 08:31 AM
OK just tried again and this time I was able to set the ACT7 instance.
Still the same problem though.
Act7 is running
SQL Server is running
ActDiag doesn't even show anything as it fails immediately to connect.
Try again tomorrow.
by the way, when manually installing SQLServeur, there is no MSXML installed at all.
And when it appears (in some trials I did recently, it's MSXML 4, not MSXML6)
10-30-2008 06:17 AM
I have followed your guidelines and here are the results:
>The SQL Service Is Not Running To start the SQL Service,
The Service is up and running.
>Locate the SQL Server (ACT7) entry from the name column. Verify that the Status is listed as started.
Always started and running.
>Verifying SQL Installed Properly
>To verify that SQL installed properly, please use the following steps:
>Click the Windows Start button and select Run.
>The Run dialog box appears. Type actdiag in the Open field and click OK.
>The ACT! Diagnostics disclaimer window will appear.
No. ActDiag immediately complains "Could not connect to the SQL Server Instance" and doesn't go any further.
>Type sqlcmd -S(local)\ACT7 -E and press Enter.
This causes the following error message:
HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server .
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establi
shing a connection to the server. When connecting to SQL Server 2005, this failu
re may be caused by the fact that under the default settings SQL Server does not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
For information, I have verified the Pipe and TCP/IP status:
SQL Server Configuration Manager (Local)
SQL Server 2005 Network Configuration
- Protocols for ACT7
- Named Pipes Enabled
- Enabled Yes
- Pipe Name \\.\pipe\MSSQL$ACT7\sql\query
- TCP/IP Enabled
- Enabled Yes
- Keep Alive 30000
- Listen All Yes
- No Delay No
TCP Dynamic Ports 49160
TCP Port <blank>
Is this of any helP?
10-30-2008 06:29 AM
10-30-2008 06:55 AM
This gives the following message (which in my opinion is no surprise as it doesn't communicate at all with SQL Server):
Reset Error: System.Data.SqlClient.SqlException: Login failed for user 'sa'.
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfoserverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at SecurityCmdLnApp.?.?(String ?)
10-31-2008 08:33 AM
It's ACT! 2008 standard, right?
You might try removing ACT! and SQL and using this download for SQL and see if it works:
10-31-2008 02:35 PM
I'm boarding for a long flight. I may try to tweak this in the plane and will let you know during the week-end.
10-31-2008 02:46 PM
If that fails, it should give a SQL Install Log - post that.
Also any errors in the Windows Event Log - start | run | eventvwr.msc