.Net Issue

GlobalSCAPE User Forum

Forums Register Login My Profile Inbox Address Book My Subscription My Forums

Member List Search Calendars FAQ Ticket List Log Out

.Net Issue

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [Secure FTP Server] >> Secure FTP Server Scripting >> .Net Issue

Page: [1]

Message

<< Older Topic Newer Topic >>

.Net Issue - 4/22/2008 6:54:16 PM

overllord64

Posts: 1
Joined: 4/22/2008
Status: offline

This is driving me nuts... was on SecureFTP 3.2 and everything was working nicely (connecting, adding/deleting users etc)
Went to 3.3 and it constantly "crashes" with (C# code by the way)

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 1000
Date:  4/22/2008
Time:  4:53:20 PM
User:  N/A
Computer: xxxx
Description:
Faulting application w3wp.exe, version 6.0.3790.3959, stamp 45d6968e, faulting module sftpcominterface.dll, version 330.0.0.1, stamp 459d6840, debug? 0, fault address 0x0003f8d7.

The VBScript options work fine, but I have no interest in rewriting a whole bunch of C# code, that was working.

I guess my question is.... anyone seen this and can help with getting it working
If not, does any one have downgrade instruction to 3.2 (tried and it would not take the config file from 3.3 and repopulate all my users folders)

Post #: 1

RE: .Net Issue - 6/11/2009 1:59:27 AM

stalla

Posts: 1
Joined: 6/4/2009
Status: offline

Things were working fine in the Dev environment, but when put in the production the following error is coming time and again. The following are the error details.

Event Type: Error
Event Source: .NET Runtime 2.0 Error
Event Category: None
Event ID: 1000
Date:  6/11/2009
Time:  11:40:27 AM
User:  N/A
Computer: xxxx
Description:
Faulting application sftpsyncservice.exe, version 1.0.0.0, stamp 47df6b58, faulting module sftpcominterface.dll, version 330.0.0.1, stamp 459d6840, debug? 0, fault address 0x0002bf36.

Can any one look into this and reply ASAP, as this one is a blocking issue for us.

(in reply to overllord64)

Post #: 2

RE: .Net Issue - 10/28/2009 4:36:10 PM

rickbassham

Posts: 2
Joined: 10/28/2009
Status: offline

Any luck with an answer? I am having the same issue.

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 1000
Date: 10/28/2009
Time: 4:37:51 PM
User: N/A
Computer: VIPSWEB01
Description:
Faulting application w3wp.exe, version 6.0.3790.3959, stamp 45d6968e, faulting module sftpcominterface.dll, version 330.0.10.3, stamp 4a9c5349, debug? 0, fault address 0x0004a707.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 00 70 00 70 00 6c 00 A.p.p.l.
0008: 69 00 63 00 61 00 74 00 i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00 i.o.n. .
0018: 46 00 61 00 69 00 6c 00 F.a.i.l.
0020: 75 00 72 00 65 00 20 00 u.r.e. .
0028: 20 00 77 00 33 00 77 00 .w.3.w.
0030: 70 00 2e 00 65 00 78 00 p...e.x.
0038: 65 00 20 00 36 00 2e 00 e. .6...
0040: 30 00 2e 00 33 00 37 00 0...3.7.
0048: 39 00 30 00 2e 00 33 00 9.0...3.
0050: 39 00 35 00 39 00 20 00 9.5.9. .
0058: 34 00 35 00 64 00 36 00 4.5.d.6.
0060: 39 00 36 00 38 00 65 00 9.6.8.e.
0068: 20 00 69 00 6e 00 20 00 .i.n. .
0070: 73 00 66 00 74 00 70 00 s.f.t.p.
0078: 63 00 6f 00 6d 00 69 00 c.o.m.i.
0080: 6e 00 74 00 65 00 72 00 n.t.e.r.
0088: 66 00 61 00 63 00 65 00 f.a.c.e.
0090: 2e 00 64 00 6c 00 6c 00 ..d.l.l.
0098: 20 00 33 00 33 00 30 00 .3.3.0.
00a0: 2e 00 30 00 2e 00 31 00 ..0...1.
00a8: 30 00 2e 00 33 00 20 00 0...3. .
00b0: 34 00 61 00 39 00 63 00 4.a.9.c.
00b8: 35 00 33 00 34 00 39 00 5.3.4.9.
00c0: 20 00 66 00 44 00 65 00 .f.D.e.
00c8: 62 00 75 00 67 00 20 00 b.u.g. .
00d0: 30 00 20 00 61 00 74 00 0. .a.t.
00d8: 20 00 6f 00 66 00 66 00 .o.f.f.
00e0: 73 00 65 00 74 00 20 00 s.e.t. .
00e8: 30 00 30 00 30 00 34 00 0.0.0.4.
00f0: 61 00 37 00 30 00 37 00 a.7.0.7.
00f8: 0d 00 0a 00 ....

(in reply to stalla)

Post #: 3

RE: .Net Issue - 10/29/2009 12:23:28 PM

rickbassham

Posts: 2
Joined: 10/28/2009
Status: offline

Changing IIS to "IIS 5.0 isolation mode" seems to have fixed this issue. That is something that should probably be documented somewhere...

(in reply to rickbassham)

Post #: 4