Search This Blog

Showing posts with label Error. Show all posts
Showing posts with label Error. Show all posts

Thursday, January 10, 2019

Oddest error in Windows 10 Pro: windows 10 pro spotify error data area passed is too small caused by SQL 2017 enabled with filestream

https://answers.microsoft.com/en-us/windows/forum/all/windows-10-store-the-data-area-passed-to-a-system/0b727e53-d562-4145-b458-90c8bbe25047?auth=1


https://blogs.msdn.microsoft.com/sql_server_team/centennial-appsdesktop-bridge-sql-server-and-
error-the-data-area-passed-to-a-system-call-is-too-small/

I had tried to install Spotify and Skype on my new Windows 10 pro laptop and this error occurred:

  Data area passed is too small

From first article:

I suspect you may have a SQL database using filestream. It looks like a SQL bug is causing Windows Store apps using Centennial to crash with this error. For me this includes Ubuntu and WhatsApp. For more info check out the SQL Tiger blog where it is discussed. A fix is out for SQL 2017 but still waiting for older versions.

From second article:

Scenario:

1. Install Windows 10 1607 or later on the system.
2. Install SQL Server and enable the SQL Filestream feature (Ref: https://docs.microsoft.com/en-us/sql/relational-databases/blob/enable-and-configure-filestream )
3. Create a database with a filestream container. Ensure that container is hosted on the drive which also hosts the Centennial applications.
4. Install any Centennial application such as MS Office Preview apps or Ubuntu Linux from the Microsoft Store application
5. Launching any Centennial application fails with the following error
Fix: Install latest SQL 2017 update.

Friday, July 17, 2009

VB6 App with C# COM object

VB6 project using C# COM Assembly
-2147024896 (80070002) Automation error The System cannot find file specified

I get this very thing...

from MSDN forum

Question:
i'm having problems running the vb6 app, and the error occurs when i make the form show. i've followed the instructions from the help file and still the problem arises everytime.

here's another weird thing, when i added the interop form to an existing vb6 application, it was ok when run inside the ide. when i compiled this to an .exe file, the error happened. i also tried creating fresh vb6 app and it worked, so any ideas on this issue? thanks.


Answer:
1) Strongly name Assemblies.
   sn -k TestKeyPair.snk
2) Add TestKeyPair.snk to project(s).
3) Edit AssemblyInfo.cs
A) Make assembly is versioned
[assembly: AssemblyVersion("1.0.0.0")]
b) Add [assembly: AssemblyKeyFile("TestKeyPair.snk")]
4) Add Assembly to GAC
gacutil /i MyInterop.dll
- Make sure all Assembly DLLS has been
5) Regasm Assembly and expose COM use /codebase
REGASM MyInterop.dll /tlb:com.MyInterop.tlb /codebase
Better Answer:
1) Strongly name Assemblies.
   sn -k TestKeyPair.snk
2) Add TestKeyPair.snk to project(s).
3) Edit AssemblyInfo.cs
A) Make assembly is versioned
[assembly: AssemblyVersion("1.0.0.0")]
b) Add [assembly: AssemblyKeyFile("TestKeyPair.snk")]
4) Copied all related assemblies local to folder containing VB6 project
5) Run from this folder: tlbexp sampleDLL.dll /out:sampleDLL.tlb
6) run from this folder: regasm sampleDLL.dll /tlb:sampleDLL.tlb
7) Open VB6 project and reference to sampleDLL.tlb is local to project.