Reopened Unassigned: user.config location [8122]

October 30, 2014, 7:34 am

≫ Next: Edited Feature: user.config location [8122]

$

0

0

Can user.config be placed in a user defined location instead of being at the
%userprofile%\AppData\Local\Overroot location?
I am not using roaming profiles, but do have employees that move around. I do have a shared folder (on server) for each employee based on their Windows username. This would allow the user to autologon Squiggle from any computer having access to the their shared folder.

Any comments??
thanks,
jakesahn
Comments: Fixed in 3.4.1

---

Edited Feature: user.config location [8122]

October 30, 2014, 7:34 am

≫ Next: Commented Feature: user.config location [8122]

≪ Previous: Reopened Unassigned: user.config location [8122]

$

0

0

Can user.config be placed in a user defined location instead of being at the
%userprofile%\AppData\Local\Overroot location?
I am not using roaming profiles, but do have employees that move around. I do have a shared folder (on server) for each employee based on their Windows username. This would allow the user to autologon Squiggle from any computer having access to the their shared folder.

Any comments??
thanks,
jakesahn

Commented Feature: user.config location [8122]

October 30, 2014, 7:34 am

≫ Next: New Post: Other path for config

≪ Previous: Edited Feature: user.config location [8122]

$

0

0

Can user.config be placed in a user defined location instead of being at the
%userprofile%\AppData\Local\Overroot location?
I am not using roaming profiles, but do have employees that move around. I do have a shared folder (on server) for each employee based on their Windows username. This would allow the user to autologon Squiggle from any computer having access to the their shared folder.

Any comments??
thanks,
jakesahn
Comments: Fixed in 3.4.1

New Post: Other path for config

October 30, 2014, 8:32 am

≫ Next: Created Unassigned: Does allow sign out [8138]

≪ Previous: Commented Feature: user.config location [8122]

$

0

0

that's a good news, can you give me an approximate release date?

Created Unassigned: Does allow sign out [8138]

October 31, 2014, 6:34 am

≫ Next: Created Unassigned: No Space in User Field [8139]

≪ Previous: New Post: Other path for config

$

0

0

Beta Version 3.4.1.0 Doesn't allow you to sign out.

Created Unassigned: No Space in User Field [8139]

October 31, 2014, 6:35 am

≫ Next: New Post: Other path for config

≪ Previous: Created Unassigned: Does allow sign out [8138]

$

0

0

Beta Version 3.4.1.0
Doesn't allow you to have a space in the UserName Field.

New Post: Other path for config

October 31, 2014, 9:53 pm

≫ Next: New Post: Other path for config

≪ Previous: Created Unassigned: No Space in User Field [8139]

$

0

0

3.4 is already available for download as beta. There is no date for final release yet. It depends on community on how soon the bugs are reported and how much contribution I receive in fixing those bugs.

New Post: Other path for config

November 1, 2014, 12:33 am

≫ Next: Edited Issue: Does allow sign out [8138]

≪ Previous: New Post: Other path for config

$

0

0

ok thank you for your great work.

---

Edited Issue: Does allow sign out [8138]

November 1, 2014, 8:49 am

≫ Next: Commented Issue: Does allow sign out [8138]

≪ Previous: New Post: Other path for config

$

0

0

Beta Version 3.4.1.0 Doesn't allow you to sign out.

Commented Issue: Does allow sign out [8138]

November 1, 2014, 8:49 am

≫ Next: Edited Issue: No Space in User Field [8139]

≪ Previous: Edited Issue: Does allow sign out [8138]

$

0

0

Beta Version 3.4.1.0 Doesn't allow you to sign out.
Comments: Thank you for reporting the issue. It has been resolved and will be available in next revision. Commit f0e06073eb

Edited Issue: No Space in User Field [8139]

November 1, 2014, 7:17 pm

≫ Next: Commented Issue: No Space in User Field [8139]

≪ Previous: Commented Issue: Does allow sign out [8138]

$

0

0

Beta Version 3.4.1.0
Doesn't allow you to have a space in the UserName Field.

Commented Issue: No Space in User Field [8139]

November 1, 2014, 7:17 pm

≫ Next: Released: Squiggle 3.4 Beta (Oct 25, 2014)

≪ Previous: Edited Issue: No Space in User Field [8139]

$

0

0

Beta Version 3.4.1.0
Doesn't allow you to have a space in the UserName Field.
Comments: Thank you for reporting the issue. It has been fixed and will be available in next revision of 3.4. Commit 23980e19dad514

Released: Squiggle 3.4 Beta (Oct 25, 2014)

November 1, 2014, 8:03 pm

≫ Next: Updated Release: Squiggle 3.4 Beta (Oct 25, 2014)

≪ Previous: Commented Issue: No Space in User Field [8139]

$

0

0

• Build on .NET Framework 4.5.1
• Tested on Windows 8.1
• MSI installs in AppData folder
• Replaced zeromq with NetMQ to avoid dependency on VC++ runtime
• Save history in SQLite instead of SQLServerCE

Revision 1: Save config settings in roaming profile
Revision 2: Fixed issue 8138 and8139

Updated Release: Squiggle 3.4 Beta (Oct 25, 2014)

November 1, 2014, 8:03 pm

≫ Next: Commented Unassigned: Squiggle Exception code 40000015 [8137]

≪ Previous: Released: Squiggle 3.4 Beta (Oct 25, 2014)

$

0

0

• Build on .NET Framework 4.5.1
• Tested on Windows 8.1
• MSI installs in AppData folder
• Replaced zeromq with NetMQ to avoid dependency on VC++ runtime
• Save history in SQLite instead of SQLServerCE

Revision 1: Save config settings in roaming profile
Revision 2: Fixed issue 8138 and 8139

Commented Unassigned: Squiggle Exception code 40000015 [8137]

November 3, 2014, 6:19 am

≫ Next: Commented Unassigned: Squiggle Exception code 40000015 [8137]

≪ Previous: Updated Release: Squiggle 3.4 Beta (Oct 25, 2014)

$

0

0

Our users are receiving the following error:

Application: Squiggle.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code 40000015, exception address 758DC42D



Faulting application name: Squiggle.exe, version: 3.3.3.0, time stamp: 0x5326770a
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86
Exception code: 0x40000015
Fault offset: 0x0000c42d
Faulting process id: 0x4c70
Faulting application start time: 0x01cff2a02d270c10
Faulting application path: \\acts-prt1\public\SQUIGGLE\Squiggle.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 7358603a-5e96-11e4-a950-18a9053eb401


Please let me know if there is a fix for this problem.





Comments: co-worker of klstorey. This seems to have resolved this issue. Thanks.

---

Commented Unassigned: Squiggle Exception code 40000015 [8137]

November 3, 2014, 6:55 am

≫ Next: Commented Unassigned: Squiggle Exception code 40000015 [8137]

≪ Previous: Commented Unassigned: Squiggle Exception code 40000015 [8137]

$

0

0

Our users are receiving the following error:

Application: Squiggle.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code 40000015, exception address 758DC42D



Faulting application name: Squiggle.exe, version: 3.3.3.0, time stamp: 0x5326770a
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86
Exception code: 0x40000015
Fault offset: 0x0000c42d
Faulting process id: 0x4c70
Faulting application start time: 0x01cff2a02d270c10
Faulting application path: \\acts-prt1\public\SQUIGGLE\Squiggle.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 7358603a-5e96-11e4-a950-18a9053eb401


Please let me know if there is a fix for this problem.





Comments: I retract. The error still exists.

Commented Unassigned: Squiggle Exception code 40000015 [8137]

November 3, 2014, 6:55 am

≫ Next: New Post: History to SQL Server

≪ Previous: Commented Unassigned: Squiggle Exception code 40000015 [8137]

$

0

0

Our users are receiving the following error:

Application: Squiggle.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code 40000015, exception address 758DC42D



Faulting application name: Squiggle.exe, version: 3.3.3.0, time stamp: 0x5326770a
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86
Exception code: 0x40000015
Fault offset: 0x0000c42d
Faulting process id: 0x4c70
Faulting application start time: 0x01cff2a02d270c10
Faulting application path: \\acts-prt1\public\SQUIGGLE\Squiggle.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 7358603a-5e96-11e4-a950-18a9053eb401


Please let me know if there is a fix for this problem.





Comments: Currently, we are able to bring it up but nobody can see each other.

New Post: History to SQL Server

November 3, 2014, 1:14 pm

≫ Next: New Post: History to SQL Server

≪ Previous: Commented Unassigned: Squiggle Exception code 40000015 [8137]

$

0

0

Alright, I can't figure this out.... I've tried everything I can think of short of modifying the code myself (Not as good with C#)

I have Squiggle 3.3.3.0 and i can't get the chat to log to a sql server. I've downloaded the 3.3 scripts, ran the sql script, copied the connection string, specified the correct server, for testing I'm using the trusted connection my account is db_admin but it's not making a connection to the server.

I've enabled logging and it appears that it's still trying to use SQLServerCE to make the connection to the database and not SQLClient.

the actual error message is
Erorr occured while logging history.: System.ArgumentException: Keyword not supported: 'server'.

I've tried changing the <system.data> and the <entityFramework> to reflect the fact that I want to use SQLClient but that doesn't seem to work either.

am I doing something stupid? I can't seem to find any other answers

Thank you for your help



more log entries

Erorr occured while logging history.: System.ArgumentException: Keyword not supported: 'server'.
at System.Data.SqlServerCe.SqlCeConnectionStringBuilder.GetIndex(String keyword)
at System.Data.SqlServerCe.SqlCeConnectionStringBuilder.set_Item(String keyword, Object value)
at System.Data.Common.DbConnectionStringBuilder.set_ConnectionString(String value)
at System.Data.SqlServerCe.SqlCeConnectionStringBuilder..ctor(String connectionString)
at System.Data.SqlServerCe.SqlCeConnection.set_ConnectionString(String value)
at System.Data.Entity.Infrastructure.SqlCeConnectionFactory.CreateConnection(String nameOrConnectionString)
at System.Data.Entity.Internal.LazyInternalConnection.Initialize()
at System.Data.Entity.Internal.LazyInternalConnection.get_ProviderName()
at System.Data.Entity.Internal.LazyInternalContext.InitializeContext()
at System.Data.Entity.Internal.InternalContext.GetEntitySetAndBaseTypeForType(Type entityType)
at System.Data.Entity.Internal.Linq.InternalSet1.Initialize()
at System.Data.Entity.Internal.Linq.InternalSet1.get_InternalContext()
at System.Data.Entity.Internal.Linq.InternalSet1.ActOnSet(Action action, EntityState newState, Object entity, String methodName)
at System.Data.Entity.Internal.Linq.InternalSet1.Add(Object entity)
at System.Data.Entity.DbSet1.Add(TEntity entity)
at Squiggle.History.DAL.HistoryRepository.AddStatusUpdate(DateTime stamp, Guid contactId, String contactName, Int32 status)
at Squiggle.History.HistoryManager.AddStatusUpdate(Guid contactId, String contactName, Int32 status)
at Squiggle.Client.ChatClient.<>c__DisplayClass16.<LogStatus>b__15()
at Squiggle.Utilities.ExceptionMonster.<>c__DisplayClass1.<EatTheException>b__0()
at Squiggle.Utilities.ExceptionMonster.EatTheException[T](Func1 action, String actionDescription, Boolean& success, Exception& ex)

New Post: History to SQL Server

November 3, 2014, 1:23 pm

≫ Next: New Post: History to SQL Server

≪ Previous: New Post: History to SQL Server

$

0

0

Did you change the DBProvider app setting to point to the SQLClient provider?
See http://squiggle.codeplex.com/SourceControl/latest#Squiggle.UI/app.config

Look for DbProvider key in appSettings

<appSettings>
    <add key="DbProvider" value="System.Data.SQLite.EF6" />

New Post: History to SQL Server

November 3, 2014, 1:33 pm

≫ Next: Created Unassigned: File transfer not available in group chat [8140]

≪ Previous: New Post: History to SQL Server

$

0

0

hasankhan wrote:

Did you change the DBProvider app setting to point to the SQLClient provider?
See http://squiggle.codeplex.com/SourceControl/latest#Squiggle.UI/app.config

Look for DbProvider key in appSettings

<appSettings>
    <add key="DbProvider" value="System.Data.SQLite.EF6" />

I don't have that option, Must just be in the 3.4 beta.

I did just figure it out though. I had to erase the <system.data> and the <entityFramework> sections all together. It appears to be working now but the chat messages that are logged are being doubled both in the history viewer and the SQL server, is that supposed to happen? doesn't seem like that is desired behavior.


EDIT so it looks like one client is logging the sent message and the other client is logging the received message because the time stamps are about a half second apart. Is there a way to fix it so it only logs the sent or vise versa? if not I'm just gladi got it connecting and logging to SQL for now lol