Jump to content
Nikola Gramatikov

Stuck on "Loading Components" when starting UniLogic on Windows 10

Recommended Posts

Hello,
I have very strange problems starting UniLogic 1.17 Rev 58/ I use windows 10. The program stucks on "Loading Components". I tried to reinstall it couple of times + tried  to install older version - The same issue.

where is the problem?  please help.

Best wishes,
eng. Nikola gramatikov

Share this post


Link to post
Share on other sites

We would like to have a remote session to your computer in order to investigate the issue,

In the meanwhile, you can go to:

%programdata%\Unitronics\UniLogic\Temp\ErrorData\

 

There should be either zip file or several files (text files and maybe an image).

 

If there isn't any file in that folder (the date and time of the files should be from the last time UniLogic crashed), then there is nothing you can post right not in order to help me understand what's wrong.

 

If there are files, then look for information.txt

Post its content here.

Share this post


Link to post
Share on other sites

Hello, 

Sorry but i was traveling and now seeng the post.

 

There is nothing in appdata folders - there is no temp folder and etc. except RecentFiles.xml, UserOptions.xml

 

Lets arange some remote sesion to see whats going on. (write me on PM

 

Best wishes,

eng. Nikola Gramatikov

Share this post


Link to post
Share on other sites

Not AppData, but ProgramData

Contact our support by either email or phone call and they will arrange a remote session with a schedule that suitable for all of us.

 

10x

Share this post


Link to post
Share on other sites

Hi ,

After PC updated to Windows 10, version 1607 (window 10 force update), the UniLogic not working at all, Stop at splash screen, after Loading Notifier > Loading Components...

No matter uninstall reinstall still the same problem exist.

 

I have done some research said that might be related to Window UAC, and some components of the UniLogic is shared with the windows .net class and might be access denied by window 10.

 

*P.S. already disable window firewall and make firewall recognize Unilogic. Previous window 10 version is fine with Unilogic after turn Off firewall.

 

 

Below is the error log found on PC 

 

C:\User\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\UNILOGIC

 

Error :

 

2016-09-06 00:40:44.60 Server      Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64)

                Oct 19 2012 13:38:57

                Copyright (c) Microsoft Corporation

                Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )

 

2016-09-06 00:40:44.60 Server      (c) Microsoft Corporation.

2016-09-06 00:40:44.60 Server      All rights reserved.

2016-09-06 00:40:44.60 Server      Server process ID is 10256.

2016-09-06 00:40:44.60 Server      System Manufacturer: 'ASUSTeK COMPUTER INC.', System Model: 'X555LDB'.

2016-09-06 00:40:44.60 Server      Authentication mode is MIXED.

2016-09-06 00:40:44.60 Server      Logging SQL Server messages in file 'C:\Users\SHIN-CRS\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\UNILOGIC\error.log'.

2016-09-06 00:40:44.60 Server      The service account is 'SHIN-CRS-PC\SHIN-CRS'. This is an informational message; no user action is required.

2016-09-06 00:40:44.60 Server      Command Line Startup Parameters:

                 -c

                 -S "MSSQL11E.LOCALDB"

                 -s "LOCALDB#583EBAD3"

                 -d "C:\Users\SHIN-CRS\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\UNILOGIC\master.mdf"

                 -l "C:\Users\SHIN-CRS\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\UNILOGIC\mastlog.ldf"

                 -e "C:\Users\SHIN-CRS\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\UNILOGIC\error.log"

2016-09-06 00:40:44.73 Server      SQL Server detected 1 sockets with 2 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.

2016-09-06 00:40:44.73 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2016-09-06 00:40:44.73 Server      Detected 12187 MB of RAM. This is an informational message; no user action is required.

2016-09-06 00:40:44.73 Server      Using conventional memory in the memory manager.

2016-09-06 00:40:44.78 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

2016-09-06 00:40:44.78 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.

2016-09-06 00:40:44.79 Server      Software Usage Metrics is disabled.

2016-09-06 00:40:44.79 spid7s      Starting up database 'master'.

2016-09-06 00:40:44.90 Server      CLR version v4.0.30319 loaded.

2016-09-06 00:40:44.94 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.

2016-09-06 00:40:45.12 spid7s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.

2016-09-06 00:40:45.12 spid7s      SQL Server Audit has started the audits. This is an informational message. No user action is required.

2016-09-06 00:40:45.15 spid7s      SQL Trace ID 1 was started by login "sa".

2016-09-06 00:40:45.15 spid7s      Server name is 'SHIN-CRS-PC\LOCALDB#583EBAD3'. This is an informational message only. No user action is required.

2016-09-06 00:40:45.16 spid11s     Server local connection provider is ready to accept connection on [ \\.\pipe\LOCALDB#583EBAD3\tsql\query ].

2016-09-06 00:40:45.16 spid11s     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.

2016-09-06 00:40:45.16 spid11s     SQL Server is now ready for client connections. This is an informational message; no user action is required.

2016-09-06 00:40:45.17 spid7s      Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\110\LocalDB\Binn\\ftimport.dll'.

2016-09-06 00:40:45.17 spid9s      Starting up database 'mssqlsystemresource'.

2016-09-06 00:40:45.20 spid9s      The resource database build version is 11.00.3000. This is an informational message only. No user action is required.

2016-09-06 00:40:45.27 spid7s      Starting up database 'msdb'.

2016-09-06 00:40:45.64 spid9s      Starting up database 'model'.

2016-09-06 00:40:45.93 spid9s      Clearing tempdb database.

2016-09-06 00:40:46.17 spid9s      Starting up database 'tempdb'.

2016-09-06 00:40:46.28 spid15s     The Service Broker endpoint is in disabled or stopped state.

2016-09-06 00:40:46.28 spid15s     The Database Mirroring endpoint is in disabled or stopped state.

2016-09-06 00:40:46.33 spid15s     Service Broker manager has started.

2016-09-06 00:40:46.84 spid7s      Recovery is complete. This is an informational message only. No user action is required.

2016-09-06 00:45:46.84 Server      The RANU instance is terminating in response to its internal time out. This is an informational message only. No user action is required.

2016-09-06 00:45:46.85 spid10s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

 

 

Error 1:

 

2016-09-06 00:40:35.25 Server      Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64)

                Oct 19 2012 13:38:57

                Copyright (c) Microsoft Corporation

                Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )

 

2016-09-06 00:40:35.25 Server      (c) Microsoft Corporation.

2016-09-06 00:40:35.25 Server      All rights reserved.

2016-09-06 00:40:35.25 Server      Server process ID is 8688.

2016-09-06 00:40:35.25 Server      System Manufacturer: 'ASUSTeK COMPUTER INC.', System Model: 'X555LDB'.

2016-09-06 00:40:35.25 Server      Authentication mode is MIXED.

2016-09-06 00:40:35.25 Server      Logging SQL Server messages in file 'C:\Users\SHIN-CRS\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\UNILOGIC\error.log'.

2016-09-06 00:40:35.25 Server      The service account is 'SHIN-CRS-PC\SHIN-CRS'. This is an informational message; no user action is required.

2016-09-06 00:40:35.25 Server      Command Line Startup Parameters:

                 -m

                 -K

                 -T 1617

                 -w 5

                 -c

                 -S "MSSQL11E.LOCALDB"

                 -s "LOCALDB#39013790"

                 -d "C:\Users\SHIN-CRS\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\UNILOGIC\master.mdf"

                 -l "C:\Users\SHIN-CRS\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\UNILOGIC\mastlog.ldf"

                 -e "C:\Users\SHIN-CRS\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\UNILOGIC\error.log"

2016-09-06 00:40:35.52 Server      SQL Server detected 1 sockets with 2 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.

2016-09-06 00:40:35.52 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2016-09-06 00:40:35.52 Server      Detected 12187 MB of RAM. This is an informational message; no user action is required.

2016-09-06 00:40:35.52 Server      Using conventional memory in the memory manager.

2016-09-06 00:40:35.61 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

2016-09-06 00:40:35.63 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.

2016-09-06 00:40:35.64 Server      Database Mirroring Transport is disabled in the endpoint configuration.

2016-09-06 00:40:35.64 Server      Software Usage Metrics is disabled.

2016-09-06 00:40:35.64 spid6s      Warning ******************

2016-09-06 00:40:35.64 spid6s      SQL Server started in single-user mode. This an informational message only. No user action is required.

2016-09-06 00:40:35.64 spid6s      Starting up database 'master'.

2016-09-06 00:40:35.67 spid6s      The tail of the log for database master is being rewritten to match the new sector size of 4096 bytes.  512 bytes at offset 347648 in file C:\Users\SHIN-CRS\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\UNILOGIC\mastlog.ldf will be written.

2016-09-06 00:40:35.73 Server      CLR version v4.0.30319 loaded.

2016-09-06 00:40:35.76 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.

2016-09-06 00:40:35.91 spid6s      The password regeneration attempt for SA was successful.

2016-09-06 00:40:35.92 spid6s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.

2016-09-06 00:40:35.92 spid6s      SQL Server Audit has started the audits. This is an informational message. No user action is required.

2016-09-06 00:40:35.97 spid6s      SQL Trace ID 1 was started by login "sa".

2016-09-06 00:40:35.97 spid6s      Server name is 'SHIN-CRS-PC\LOCALDB#39013790'. This is an informational message only. No user action is required.

2016-09-06 00:40:35.98 spid6s      Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\110\LocalDB\Binn\\ftimport.dll'.

2016-09-06 00:40:35.98 spid9s      Starting up database 'mssqlsystemresource'.

2016-09-06 00:40:35.98 spid11s     Password policy update was successful.

2016-09-06 00:40:35.99 spid11s     The service master key regeneration was successful.

2016-09-06 00:40:35.99 spid11s     Server local connection provider is ready to accept connection on [ \\.\pipe\LOCALDB#39013790\tsql\query ].

2016-09-06 00:40:35.99 spid11s     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.

2016-09-06 00:40:36.00 spid9s      The resource database build version is 11.00.3000. This is an informational message only. No user action is required.

2016-09-06 00:40:36.55 spid6s      Starting up database 'msdb'.

2016-09-06 00:40:36.64 spid6s      The tail of the log for database msdb is being rewritten to match the new sector size of 4096 bytes.  3072 bytes at offset 50176 in file C:\Users\SHIN-CRS\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\UNILOGIC\MSDBLog.ldf will be written.

2016-09-06 00:40:36.64 spid9s      Starting up database 'model'.

2016-09-06 00:40:36.71 spid9s      The tail of the log for database model is being rewritten to match the new sector size of 4096 bytes.  3072 bytes at offset 58368 in file C:\Users\SHIN-CRS\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\UNILOGIC\modellog.ldf will be written.

2016-09-06 00:40:36.90 spid9s      Clearing tempdb database.

2016-09-06 00:40:37.15 spid9s      Starting up database 'tempdb'.

2016-09-06 00:40:37.32 spid6s      Database 'master' is upgrading script 'u_tables.sql' from level 502 to level 569.

2016-09-06 00:40:37.32 spid6s      Starting u_Tables.SQL at  06 Sep 2016 00:40:37:323

2016-09-06 00:40:37.32 spid6s      This file creates all the system tables in master.

2016-09-06 00:40:37.34 spid6s      drop view spt_values ....

2016-09-06 00:40:37.36 spid6s      Creating view 'spt_values'.

2016-09-06 00:40:38.08 spid6s      drop table spt_monitor ....

2016-09-06 00:40:38.11 spid6s      Creating 'spt_monitor'.

2016-09-06 00:40:38.11 spid6s      Grant Select on spt_monitor

2016-09-06 00:40:38.11 spid6s      Insert into spt_monitor ....

2016-09-06 00:40:38.26 spid6s      Finishing at  06 Sep 2016 00:40:38:263

2016-09-06 00:40:38.29 spid6s      Database 'master' is upgrading script 'ProvisionAgentIdentity.sql' from level 184551476 to level 184552376.

2016-09-06 00:40:38.55 spid6s      Database 'master' is upgrading script 'no_op.sql' from level 184551476 to level 184552376.

2016-09-06 00:40:38.55 spid6s      -----------------------------------------

2016-09-06 00:40:38.55 spid6s      Starting execution of dummy.sql

2016-09-06 00:40:38.55 spid6s      -----------------------------------------

2016-09-06 00:40:38.56 spid6s      Database 'master' is upgrading script 'repl_upgrade.sql' from level 184551476 to level 184552376.

2016-09-06 00:40:38.56 spid6s      Executing replication upgrade scripts.

2016-09-06 00:40:38.60 spid6s      Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.

2016-09-06 00:40:38.60 spid6s      Using 'xpstar.dll' version '2011.110.3000' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.

2016-09-06 00:40:38.60 spid6s      Replication feature is not installed. Upgrade scripts will not be run.

2016-09-06 00:40:39.02 spid6s      SQL Server is now ready for client connections. This is an informational message; no user action is required.

2016-09-06 00:40:39.05 spid6s      Recovery is complete. This is an informational message only. No user action is required.

2016-09-06 00:40:39.07 spid51      .NET Framework runtime has been stopped.

2016-09-06 00:40:39.25 spid51      Server shut down by request from login SHIN-CRS-PC\SHIN-CRS.

2016-09-06 00:40:39.25 spid51      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Share this post


Link to post
Share on other sites

Contact our support for scheduling a remote session.

In the meanwhile, do you get any error when you write the following in the Command prompt?

 

SQLLocalDB start unilogic

 

And

SQLLocalDB i Unilogic

 

 

 

Can you also check %programdata%\unitronics\unilogic\Temp\ErrorData\  ?

If UniLogic was able to collect crash report, then it will be in that folder (look at the time and date to make sure that it is not an old crash report, but a relevant one).

 

Thanks.

Share this post


Link to post
Share on other sites

I don't remember. You should contact support as well, so me or someone else from the R&D will take a look at your computer.

It is most likely the SQL Server not working properly.

 

Share this post


Link to post
Share on other sites

Download the attached Rar file, and extract the files to UniLogic installation directory. This means that the "UniLogic Diagnostics.exe" (and all the other files) must be placed in the same directory where "Unitronics.Shell.UI.exe" is located (usually at: "C:\Program Files (x86)\Unitronics\UniLogic\")

 

After you've extracted the files, run "UniLogic Diagnostics.exe" and click on Diagnose.

Most chances that it will show "SQL Instance" as one that has problems. In case it find problems, the "Fix" button will become enabled. Click on Fix, and the program will attempt to fix the problem, and then it will re-diagnose the problems to confirm that they are fixed.

 

Please tell me what problems it found .

Also tell me if it managed to fix the problem that you're experiencing with UniLogic (that it is stuck in loading components).

Thanks.

UniLogic Diagnostics.rar

  • Like 3
  • Upvote 1

Share this post


Link to post
Share on other sites

Hi,

I had the same problem with 1.22 rev13 on Win10 with "SQL Instance" and applied the same solution this morning.

Now it's ok

Thanks

Share this post


Link to post
Share on other sites

Hello,

I'm having the same issue with 1.22 rev 13 and ran the suggested diagnostics.  It shows there is an issue with the SQL server and instance, but the fix button does not seem to do anything.  It is enabled, but nothing happens when I press it.  Any advice?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×