Community
Showing results for 
Search instead for 
Do you mean 
Reply

Act crashes when trying to open a shared database

New Member
Posts: 5
Country: United_Kingdom

Act crashes when trying to open a shared database

I have Act Premium v16 on all computers in my office. The shared database is stored on a stand-alone server. All computers and are running Windows 7 Pro (SP1). I can open the shared database on 9 other computers no problem.

 

I can open the local demo database with no errors.

 

I have tried disabling all firewalls, anti-virus & windows defender - No change

I can successfully ping the server and access the shared database folder via explorer

 

I have spent approx 1.5hrs on the phone to support and they cant offer any other advice as the problem is local to one machine.

 

Would anyone be able to suggest any possible fixes or things to try?

New Member
Posts: 5
Country: United_Kingdom

Re: Act crashes when trying to open a shared database

In addition to the crash I have seen a runtime error (R6026) and the suggestion that port 1434 is not open even though all firewalls were turned off.
Bronze Elite Contributor
Posts: 2,547
Country: New_Zealand

Re: Act crashes when trying to open a shared database


dan.mcpherson wrote:

 

I have tried disabling all firewalls, anti-virus & windows defender - No change

 


 Apart from Windows Defender, what is the anti-virus software you mention and at the time you installed Act!, was it disabled? 

Graeme Leo
Xact Software - consultants and developers
Follow us on Twitter and check out our Blog


Copper Super Contributor
Posts: 49
Country: USA

Re: Act crashes when trying to open a shared database

I have 2 Windows 2003 servers which both have V16 Premium on 1 and APFW on the other and 2 Windows 7 machines. I get the same error on both of the windows 7 machines although I have disabled everythong on both machines and tested it. I think this problem came from a windows update as all was working well a couple of weeks ago. I can open the databases on the APFW server, but get the Port 1434 error on the other one. I have not had time to investigate further, just cut a remote for my machine and set it to sync hourly.

 

If anyone comes up with a solution, please post it.

Phillip R. Horn
ACTive Certified Consultants of Virginia, LLC
888-975-3111
www.accofva.com
New Member
Posts: 5
Country: United_Kingdom

Re: Act crashes when trying to open a shared database

I am using Bullguard Internet Security. I have only disabled it when trying to use the software. I will reinstall later today.

 

I am not sure if it makes a difference but I always right click and run as administrator...

Bronze Elite Contributor
Posts: 2,547
Country: New_Zealand

Re: Act crashes when trying to open a shared database

The issue is that allowing AV software to remain active while installing Act! can, and I repeat can, have a detrimental affect on the  installation to the extent that if a manual uninstall of Act! and subsequent reinstall is not effective then you would need to resort to reinstalling the operating system and reinstalling the software.

Graeme Leo
Xact Software - consultants and developers
Follow us on Twitter and check out our Blog


New Member
Posts: 5
Country: United_Kingdom

Re: Act crashes when trying to open a shared database

[ Edited ]

So I uninstalled Act, restarted, turned off Bullguard, windows firewall and defender, restarted, reinstalled Act, restarted.

 

No Joy. Act still crashes when opening a shared database. I vaguley recall someone said to try it on a new user account so I gave that a go and nothing.

 

Unless anyone has a less drastic solution, I may have to reinstall the OS.

Platinum Elite Contributor
Posts: 6,663
Country: USA

Re: Act crashes when trying to open a shared database

From what you wrote I assume that after the reinstall that the ACT! program opened to the welcome screen but crashed when you tried to open a database.. If so, I suspect that your SQL server installation is damaged. The ACT! uninstall doesn't uninstall the SQL server. You could also use ACTDiag to check the database. Also, with ACT! closed locate the PAD file for the ACTdemo database and try double clicking on the PAD file.

Roy Laudenslager
ACT! Certified Consultant
ACT! Report Expert
Durkin Impact Report Designer
www.techbenders.com
royel@techbenders.com
541-343-8129
New Member
Posts: 5
Country: United_Kingdom

Re: Act crashes when trying to open a shared database

I have no problems when opening the local demo database. I don't know much about the SQL side of things. I have obtained the error log that was registered during the last crash, I do not know what to look for here:

 

2014-05-20 09:05:36.93 Server      Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
 Jun 17 2011 00:54:03
 Copyright (c) Microsoft Corporation
 Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

2014-05-20 09:05:36.93 Server      (c) Microsoft Corporation.
2014-05-20 09:05:36.93 Server      All rights reserved.
2014-05-20 09:05:36.93 Server      Server process ID is 2476.
2014-05-20 09:05:36.93 Server      System Manufacturer: 'To Be Filled By O.E.M.', System Model: 'To Be Filled By O.E.M.'.
2014-05-20 09:05:36.93 Server      Authentication mode is MIXED.
2014-05-20 09:05:36.93 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\Log\ERRORLOG'.
2014-05-20 09:05:36.94 Server      This instance of SQL Server last reported using a process ID of 2348 at 19/05/2014 18:00:02 (local) 19/05/2014 17:00:02 (UTC). This is an informational message only; no user action is required.
2014-05-20 09:05:36.94 Server      Registry startup parameters:
  -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\DATA\master.mdf
  -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\Log\ERRORLOG
  -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\DATA\mastlog.ldf
2014-05-20 09:05:36.95 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-05-20 09:05:36.95 Server      Detected 8 CPUs. This is an informational message; no user action is required.
2014-05-20 09:05:37.09 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2014-05-20 09:05:37.17 Server      Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014-05-20 09:05:37.23 spid7s      Starting up database 'master'.
2014-05-20 09:05:37.25 spid7s      2 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2014-05-20 09:05:37.26 spid7s      0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2014-05-20 09:05:37.26 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2014-05-20 09:05:37.31 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'ACT7'.
2014-05-20 09:05:37.35 spid7s      SQL Trace ID 1 was started by login "sa".
2014-05-20 09:05:37.36 spid7s      Starting up database 'mssqlsystemresource'.
2014-05-20 09:05:37.36 spid7s      The resource database build version is 10.50.2500. This is an informational message only. No user action is required.
2014-05-20 09:05:37.53 spid10s     Starting up database 'model'.
2014-05-20 09:05:37.53 spid7s      Server name is 'SBS-LAB-SERVER\ACT7'. This is an informational message only. No user action is required.
2014-05-20 09:05:37.53 spid7s      Informational: No full-text supported languages found.
2014-05-20 09:05:37.53 spid7s      Starting up database 'msdb'.
2014-05-20 09:05:37.56 spid10s     Clearing tempdb database.
2014-05-20 09:05:37.64 Server      A self-generated certificate was successfully loaded for encryption.
2014-05-20 09:05:37.65 Server      Server is listening on [ 'any' <ipv6> 49208].
2014-05-20 09:05:37.65 Server      Server is listening on [ 'any' <ipv4> 49208].
2014-05-20 09:05:37.65 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\ACT7 ].
2014-05-20 09:05:37.65 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$ACT7\sql\query ].
2014-05-20 09:05:37.65 Server      Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2014-05-20 09:05:37.65 spid10s     Starting up database 'tempdb'.
2014-05-20 09:05:37.66 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2014-05-20 09:05:37.66 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014-05-20 09:05:37.68 spid13s     The Service Broker protocol transport is disabled or not configured.
2014-05-20 09:05:37.68 spid13s     The Database Mirroring protocol transport is disabled or not configured.
2014-05-20 09:05:37.70 spid13s     Service Broker manager has started.
2014-05-20 09:05:37.70 spid7s      Recovery is complete. This is an informational message only. No user action is required.
2014-05-20 09:05:37.71 spid7s      Launched startup procedure 'PRC_MASTER_AUTOSTARTUPS'.
2014-05-20 09:05:37.83 spid25s     ISENABLED = 1
2014-05-20 09:05:37.84 spid25s     NUM_DATABASES = 3
2014-05-20 09:05:37.84 spid25s     NUM_DAYS = 30
2014-05-20 09:05:37.90 spid25s     ************************* ACT2014Demo (2014-05-19T12:25:24.610) *************************
2014-05-20 09:05:37.91 spid25s     Starting up database 'ACT2014Demo'.
2014-05-20 09:05:37.94 spid25s     26 transactions rolled forward in database 'ACT2014Demo' (5). This is an informational message only. No user action is required.
2014-05-20 09:05:37.94 spid25s     0 transactions rolled back in database 'ACT2014Demo' (5). This is an informational message only. No user action is required.
2014-05-20 09:05:37.94 spid25s     Recovery is writing a checkpoint in database 'ACT2014Demo' (5). This is an informational message only. No user action is required.
2014-05-20 09:05:38.60 spid25s     Error: 515, Severity: 16, State: 2.
2014-05-20 09:05:38.60 spid25s     Cannot insert the value NULL into column 'GRABFIELD', table 'tempdb.dbo.#TEMPTB_____________________________________________________________________________________________________________000000000005'; column does not allow nulls. INSERT fails.