Problem sa konektovanjem na server u Local-u

[Darkonyks]

Postovane kolege,

imam problem sa konektovanjem na Sql Server. Naime, u local-u se nalazi 14 racunara i jedan sa koga se dele folderi, tabele i sl. Na tom racunaru je podignut SQL Server 2008. Aplikacija koju sam napravio uspesno se pokrece i pristupa podacima iz baze sa 10 racunara dok problem prave samo 4 kompa sa sledecom porukom: (attach u prilogu). Da li neko ima neki predlog?

U detaljima poruke se nalazi:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=42081; handshake=1; ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
at System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParserStateObject.ReadSni Error(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni SyncOverAsync()
at System.Data.SqlClient.TdsParserStateObject.TryRead NetworkPacket()
at System.Data.SqlClient.TdsParser.ConsumePreLoginHan dshake(Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean& marsCapable)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)
at System.Data.SqlClient.SqlInternalConnectionTds.Att emptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
at System.Data.SqlClient.SqlInternalConnectionTds.Log inNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
at System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ct or(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions)
at System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.Creat ePooledConnection(DbConnectionPool pool, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionPool.CreateOb ject(DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionPool.UserCrea teRequest(DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionPool.TryGetCo nnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionPool.TryGetCo nnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionFactory.TryGe tConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionClosed.TryOpe nConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCo mpletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at System.Data.Common.DbDataAdapter.FillInternal(Data Set dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
at RedCorrection.CrveneIspravkeDataSetTableAdapters.I spravkeKBWTableAdapter.Fill(IspravkeKBWDataTable dataTable) in e:\Developer\GeoDigit\CrveneIspravke\RedCorrection - Copy\RedCorrection\CrveneIspravkeDataSet.Designer. cs:line 9533
at RedCorrection.CrveneIspravke.puniDataSet() in e:\Developer\GeoDigit\CrveneIspravke\RedCorrection - Copy\RedCorrection\CrveneIspravke.cs:line 34
at RedCorrection.CrveneIspravke.CrveneIspravke_Activa ted(Object sender, EventArgs e) in e:\Developer\GeoDigit\CrveneIspravke\RedCorrection - Copy\RedCorrection\CrveneIspravke.cs:line 95
at System.Windows.Forms.Form.OnActivated(EventArgs e)
at System.Windows.Forms.Form.set_Active(Boolean value)
at System.Windows.Forms.Form.WmActivate(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
ClientConnectionId:2e9339ce-182c-4dbd-bb3c-77108b7ec1cc


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18047 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
RedCorrection
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/GIS15-pc/AppData/Local/Apps/2.0/3LCT7H70.M1E/12C5A65X.N95/redc..tion_0000000000000000_0001.0001_78d46d752a8c 3973/RedCorrection.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18047 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18021 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18044 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18047 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18047 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Data.DataSetExtensions
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Data.DataSetExtensions/v4.0_4.0.0.0__b77a5c561934e089/System.Data.DataSetExtensions.dll
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Transactions
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.EnterpriseServices
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[surferxyz]

otvori port 1433 na tim računarima (firewall)

[mangia]

Vrlo lako za provjeriti. Na klijentskoj mašini lupi komandu

telnet XX.XX.XX.XX 1433
gdje je XX.XX.XX.XX IP adresa DB servera...

Trebao bi u command promptu dobiti "crn ekran"

[Darkonyks]

Originalno napisao surferxyz

otvori port 1433 na tim računarima (firewall)

Port je otvoren na svim klijentskim masinama. Medjutim, u firmi koristimo dva net provajdera, i kada pogledam mapu lokalne mreze, ispostavlja se da svi racunari nakaceni na jedan "svičer" imaju pristup serveru, dok ostalih par koji se nalaze na drugom nemaju. Da li to mozda ima neke veze? Ne poznajem mrežnu arhitekturu baš najbolje.

[Darkonyks]

Originalno napisao mangia

Vrlo lako za provjeriti. Na klijentskoj mašini lupi komandu

telnet XX.XX.XX.XX 1433
gdje je XX.XX.XX.XX IP adresa DB servera...

Trebao bi u command promptu dobiti "crn ekran"

Gde da kucaм, u command prompt-u? Tamo, ne prepoznaje komandu "telnet". Sta se postize sa zadatom komandom?

[misk0]

Originalno napisao Darkonyks

Medjutim, u firmi koristimo dva net provajdera, i kada pogledam mapu lokalne mreze, ispostavlja se da svi racunari nakaceni na jedan "svičer" imaju pristup serveru, dok ostalih par koji se nalaze na drugom nemaju. Da li to mozda ima neke veze? Ne poznajem mrežnu arhitekturu baš najbolje.

Naravno da ima veze. Racunari bi trebalo da se vide. Ako su na istom switch-u ne znaci da se i vide medjusobodno. Vjerovatno je jedan dio racunara na jednom subnetu, drugi na drugom (isto tako i modemi) i jedan sa drugim ne komuniciraju.
Ne znam koja je struktura mreze kod vas i zasto imate potrebu da imate na jedno mrezi dva izlaza ali bi to najbolje bilo prebaciti sve na jednu mrezu.
Znaci da svi racunari su na istom subnetu, kao i modemi. U tom slucaju trebas imati sva manuelna podesavanja (nema DHCP i slicnih fora).
Ako to ovo sve sto pisem djeluje 'spansko selo' zamoli nekoga u blizini da ti pomogne srediti sve to. Nemoguce je opisati u jednom forumskom postu sta i kako.

[Darkonyks]

Originalno napisao misk0

Naravno da ima veze. Racunari bi trebalo da se vide. Ako su na istom switch-u ne znaci da se i vide medjusobodno. Vjerovatno je jedan dio racunara na jednom subnetu, drugi na drugom (isto tako i modemi) i jedan sa drugim ne komuniciraju.
Ne znam koja je struktura mreze kod vas i zasto imate potrebu da imate na jedno mrezi dva izlaza ali bi to najbolje bilo prebaciti sve na jednu mrezu.
Znaci da svi racunari su na istom subnetu, kao i modemi. U tom slucaju trebas imati sva manuelna podesavanja (nema DHCP i slicnih fora).
Ako to ovo sve sto pisem djeluje 'spansko selo' zamoli nekoga u blizini da ti pomogne srediti sve to. Nemoguce je opisati u jednom forumskom postu sta i kako.

Tako sam i mislio! Hvala ti puno na pomoci.

[mangia]

Na win7 telnet client nije po defaultu omogućen. Control panel - Programs.... - Windows components ili tako nešto... Uključi Telnet Client (dakle samo Client)...

Naravno, uslov za bilo šta je fizička i operativna veza između računara...

p.s. Ne znam zašto ali 99% programera ne zna osove rač. mreža... To je jako loše

[Darkonyks]

Originalno napisao mangia

Na win7 telnet client nije po defaultu omogućen. Control panel - Programs.... - Windows components ili tako nešto... Uključi Telnet Client (dakle samo Client)...

Naravno, uslov za bilo šta je fizička i operativna veza između računara...

p.s. Ne znam zašto ali 99% programera ne zna osove rač. mreža... To je jako loše

Ok. Enable-ovao sam Telnet client Windows feature, ukucao u command promt-u onako kako si napisao, pojavio se crni ekran, ali se nista konkretno, po pogledu pristupa serveru nije promenilo mislim da je ipak u pitanju switch kao sto je misko napisao.

p.s. Ne znam zasto ali 99% administratora mreza ne zna osnove programiranja

[nn.nn]

Originalno napisao Darkonyks

p.s. Ne znam zasto ali 99% administratora mreza ne zna osnove programiranja

Je l' računaš pisanje skriptova u programiranje?