Hi,
I am using the Extended Sp's sp_OACreate, sp_OAGetProperty,... to call 'MSXML2.ServerXMLHttp'.
This works fine when called from within EXEC Statements, other stored procedures, and any other means of calling it I can think of, recursivley, 100's of times in quick succession, multiple times simultaneousley all without a problem.
I then try to call the SP from outside SQL (from vb.net using ADO.net) and it works the first time perfectally, the next and subsequent calls return the helpful error msg: 'General network error. Check your network documentation. ' and MSSQL Server Service is terminated. I have trawled the logs, the onlything that crops up is:
2003-11-04 18:13:27.33 spid52 Using 'odsole70.dll' version '2000.80.760' to execute extended stored procedure 'sp_OACreate'.
2003-11-04 18:13:29.47 spid52 Using 'dbghelp.dll' version '4.0.5'
As you would expect calling odsole70.dll.
I have replicated this problem on 2 SQL2000 server boxes, both fully patched running sp3a, one on XP Professional the other on Win2K Server
Any help much appreciated
TIAHowdy
Sadly there seems to be a large number of issues with VB.NET and SQL 2000...I see quite a few people with similar problems.
Try updating to MDAC 2.7 SP1 refresh 1
Cheers,
SG.|||Thanks SG, unfortunatley this has not had any effect, I have also tried to get the MDAC 2.8, but this has not had any effect. One point I forgot to mention was that it is running on an Insert trigger (which baffles me even more)
If you or anyone else has any suggestions I would be very grateful!
Cheers
ED
Originally posted by sqlguy7777
Howdy
Sadly there seems to be a large number of issues with VB.NET and SQL 2000...I see quite a few people with similar problems.
Try updating to MDAC 2.7 SP1 refresh 1
Cheers,
SG.|||Howdy,
Try altering the VB code to open & close the connection between each firing of the trigger...it will make the app slow but at least may show where the problem is.....
Cheers,
SG|||Originally posted by sqlguy7777
Howdy,
Try altering the VB code to open & close the connection between each firing of the trigger...it will make the app slow but at least may show where the problem is.....
Cheers,
SG
How exactly do you do that?
There's no control over a trigger except the code that's in it or some parameters on bulk insert or the ability to disable one...
No?|||And I thought crashing SQL serves meant...you take 2 servers and fling them at each other at 55 mph down the highway...
great sport that is...
oh the days...|||Howdy Brett, Ed,
Ok Ok......
I was talking in general terms... Ed will have to alter his code to break the code down into chunks so its operating "lock step" while diagnosing the problem.
As to 55 mph........try 95 mph around the M25 in the morning when late for work.....great way to wake up....
Cheers,
SG|||Cheers Guys,
I have to say I am a little confused how I am supposed to Lock down the operating lock step, my understanding of update triggers is that SQL Fires them when you have added a row to a table, which is totally sepearate to my vb calling code, if I take off the trigger the insert statement/stored procedure work fine, as soon as i put them back on I get one attempt and it !?*!s up!
Could it be permissions related? am I closing my connections properley?
Any help much appreciated!|||Howdy,
By lockstep I mean running the app step by step and checking the response each step...that way you can step through the operation and determine what is going wrong.
Try simulating what the app is doing by using Query Analyser to generate the inserts etc ( instead of the VB code ) & see what SQL does in response....that will give you a general idea of whether its SQL or app by effectively isolating the parts of the system.
Once you know whats what, post back and anyone on this site should be able to help.
Cheers,
SG.|||SG,
Thanks for this, I have been through the steps now many times :-(
A quick analysis of my findings:
1: When http_get is called from an EXEC statement in QA it works fine, I can direct it to a REALLY slow page (takes 10 seconds to give a HTTP 200 response) and issue around 10 consecutive requests, and also call it multiple times in quick succession, all without a problem..works fine.
2: When the http_get SP is called from the Insert trigger it works fine when a record is inserted directly from Enterprise Manager, an insert statement in QA and when an insert SP is written and called from QA. However when I either use an Insert Statement, or the insert SP from vb.net it works the first time, and not any consecutive times. i have noted from Profiler that although this works on the first attempt, something is not happy as around 5 mins a full Stack dump is created. If i try to re-call the insert SP from vb within this 5 mins the entire SQL server is shut down, if it is called again after the 5 mins then I can re-call the SP from vb with no problems (as long as the SP is not called again within 5 mins)
3: I have tried calling the http_get SP directly from VB, same results as point 2.
4: I have removed the http_get EXEC statement from my insert trigger, this works fine, time and time again.
5: with http_get re-instated in the insert trigger, i have inserted one record from vb.net (works as in point 2) and then quickly followed it by numerous record additions from QA (using the same insert sp) all of these work fine with no problems.
In all these instances the only error messsage i can extract from vb.net is 'General network error. Check your network documentation.'
Any help much appreciated.
Many thanks
Ed
I'm now going to try and re-word and re-post this!|||Howdy,
Just one thought...set the insert trigger to call a stored procedure that then calls the original stored procedure - I'm trying to create a level of isolation between the trigger execution and the strored procedures' operation.
If you have the trigger call a stored procedure, say, sp_calloriginal
and inside sp_calloriginal you have
----
Create Procedure dbo.sp_calloriginal
AS
exec <the_original_insert_stored_procedure_name>
GO
-----
Try that - it should at least isolate where the problem is.
Cheers,
SG.
Showing posts with label crashing. Show all posts
Showing posts with label crashing. Show all posts
Monday, March 19, 2012
Crashing server (Event ID 333)
Hello,
We experience problems with machines running SQL Servers 2005 in our
production environment. This problem is rather connected to OS or network
settings but hopefully someone here can help. The error below appears several
times in a minute and leads to crash of a machine.
We have clustered environment Windows Servers 2003 SP2 x64 + SQL Server 2005
SP2. This problem started to occur after installation of automatic updates
(bunch of security updates).
Has anyone solved similar issue? Could someone help to track down the problem?
Many thanks
eXavier
Event Type:Error
Event Source:Application Popup
Event Category:None
Event ID:333
Date:07.04.2008
Time:09:01:57
User:N/A
Computer:CMPNT45
Description:
An I/O operation initiated by the Registry failed unrecoverably. The
Registry could not read in, or write out, or flush, one of the files that
contain the system's image of the Registry.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 01 00 6c 00 .....l.
0008: 00 00 00 00 4d 01 00 c0 ...M..à
0010: 00 00 00 00 4d 01 00 c0 ...M..à
0018: 00 00 00 00 00 00 00 00 ......
0020: 00 00 00 00 00 00 00 00 ......
I am a consultant by trade and help people with SQL Server problems for a
living. But I gotta say when something like this occurs MY first action
would be (and my advice to my clients would be) call Microsoft PSS!!
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"eXavier" <eXavier@.nospam.nospam> wrote in message
news:70DC487A-4928-40E1-9DC0-59FB0AB1B5AB@.microsoft.com...
> Hello,
> We experience problems with machines running SQL Servers 2005 in our
> production environment. This problem is rather connected to OS or network
> settings but hopefully someone here can help. The error below appears
> several
> times in a minute and leads to crash of a machine.
> We have clustered environment Windows Servers 2003 SP2 x64 + SQL Server
> 2005
> SP2. This problem started to occur after installation of automatic updates
> (bunch of security updates).
> Has anyone solved similar issue? Could someone help to track down the
> problem?
> Many thanks
> eXavier
>
> Event Type: Error
> Event Source: Application Popup
> Event Category: None
> Event ID: 333
> Date: 07.04.2008
> Time: 09:01:57
> User: N/A
> Computer: CMPNT45
> Description:
> An I/O operation initiated by the Registry failed unrecoverably. The
> Registry could not read in, or write out, or flush, one of the files that
> contain the system's image of the Registry.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 00 00 00 00 01 00 6c 00 .....l.
> 0008: 00 00 00 00 4d 01 00 c0 ...M..
> 0010: 00 00 00 00 4d 01 00 c0 ...M..
> 0018: 00 00 00 00 00 00 00 00 ......
> 0020: 00 00 00 00 00 00 00 00 ......
>
|||Hello,
I agree with Kevin it's best taht you call MS PSS for memory dump analysis
on this server crash issue. For a complete list of Microsoft Product
Support Services phone numbers, please go to the following address on the
World Wide Web:
http://support.microsoft.com/directory/overview.asp
Also, you may want to use add/edit the following registry key to see if it
helps
In the new HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Session
Manager\Configuration Manager subkey, configure the following entry:
Name: RegistryLazyFlushInterval
Data Type: REG_DWORD
Value data: 60 (decimal)
You may try to increase Windows paging file size to see if it's helpful.
It's possible that this kind of issue occurs when there are some issues
related to server hardware driver. For example, if the operating system
cannot satisfy the contiguous memory blocks under the 4 GB space, the
server may become unresponsive.
Reference the following HP site details:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&
objectID
=c00688313&jumpid=reg_R1002_USEN
Please let's know if you have any further questions or comments. Thanks.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up responske may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hello,
It seems the problem was really caused by drivers for extra sotrage added
during maintenace period.
Thanks for all responses!
Best Regards
eXavier
""Peter Yang[MSFT]"" wrote:
> Hello,
> I agree with Kevin it's best taht you call MS PSS for memory dump analysis
> on this server crash issue. For a complete list of Microsoft Product
> Support Services phone numbers, please go to the following address on the
> World Wide Web:
> http://support.microsoft.com/directory/overview.asp
>
> Also, you may want to use add/edit the following registry key to see if it
> helps
> In the new HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Session
> Manager\Configuration Manager subkey, configure the following entry:
> Name: RegistryLazyFlushInterval
> Data Type: REG_DWORD
> Value data: 60 (decimal)
> You may try to increase Windows paging file size to see if it's helpful.
> It's possible that this kind of issue occurs when there are some issues
> related to server hardware driver. For example, if the operating system
> cannot satisfy the contiguous memory blocks under the 4 GB space, the
> server may become unresponsive.
> Reference the following HP site details:
> http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&
> objectID
> =c00688313&jumpid=reg_R1002_USEN
> Please let's know if you have any further questions or comments. Thanks.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ==================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up responske may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscriptions/support/default.aspx>.
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hello,
Nice to hear you solved the problem!
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
================================================== ===
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
We experience problems with machines running SQL Servers 2005 in our
production environment. This problem is rather connected to OS or network
settings but hopefully someone here can help. The error below appears several
times in a minute and leads to crash of a machine.
We have clustered environment Windows Servers 2003 SP2 x64 + SQL Server 2005
SP2. This problem started to occur after installation of automatic updates
(bunch of security updates).
Has anyone solved similar issue? Could someone help to track down the problem?
Many thanks
eXavier
Event Type:Error
Event Source:Application Popup
Event Category:None
Event ID:333
Date:07.04.2008
Time:09:01:57
User:N/A
Computer:CMPNT45
Description:
An I/O operation initiated by the Registry failed unrecoverably. The
Registry could not read in, or write out, or flush, one of the files that
contain the system's image of the Registry.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 01 00 6c 00 .....l.
0008: 00 00 00 00 4d 01 00 c0 ...M..à
0010: 00 00 00 00 4d 01 00 c0 ...M..à
0018: 00 00 00 00 00 00 00 00 ......
0020: 00 00 00 00 00 00 00 00 ......
I am a consultant by trade and help people with SQL Server problems for a
living. But I gotta say when something like this occurs MY first action
would be (and my advice to my clients would be) call Microsoft PSS!!
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"eXavier" <eXavier@.nospam.nospam> wrote in message
news:70DC487A-4928-40E1-9DC0-59FB0AB1B5AB@.microsoft.com...
> Hello,
> We experience problems with machines running SQL Servers 2005 in our
> production environment. This problem is rather connected to OS or network
> settings but hopefully someone here can help. The error below appears
> several
> times in a minute and leads to crash of a machine.
> We have clustered environment Windows Servers 2003 SP2 x64 + SQL Server
> 2005
> SP2. This problem started to occur after installation of automatic updates
> (bunch of security updates).
> Has anyone solved similar issue? Could someone help to track down the
> problem?
> Many thanks
> eXavier
>
> Event Type: Error
> Event Source: Application Popup
> Event Category: None
> Event ID: 333
> Date: 07.04.2008
> Time: 09:01:57
> User: N/A
> Computer: CMPNT45
> Description:
> An I/O operation initiated by the Registry failed unrecoverably. The
> Registry could not read in, or write out, or flush, one of the files that
> contain the system's image of the Registry.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 00 00 00 00 01 00 6c 00 .....l.
> 0008: 00 00 00 00 4d 01 00 c0 ...M..
> 0010: 00 00 00 00 4d 01 00 c0 ...M..
> 0018: 00 00 00 00 00 00 00 00 ......
> 0020: 00 00 00 00 00 00 00 00 ......
>
|||Hello,
I agree with Kevin it's best taht you call MS PSS for memory dump analysis
on this server crash issue. For a complete list of Microsoft Product
Support Services phone numbers, please go to the following address on the
World Wide Web:
http://support.microsoft.com/directory/overview.asp
Also, you may want to use add/edit the following registry key to see if it
helps
In the new HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Session
Manager\Configuration Manager subkey, configure the following entry:
Name: RegistryLazyFlushInterval
Data Type: REG_DWORD
Value data: 60 (decimal)
You may try to increase Windows paging file size to see if it's helpful.
It's possible that this kind of issue occurs when there are some issues
related to server hardware driver. For example, if the operating system
cannot satisfy the contiguous memory blocks under the 4 GB space, the
server may become unresponsive.
Reference the following HP site details:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&
objectID
=c00688313&jumpid=reg_R1002_USEN
Please let's know if you have any further questions or comments. Thanks.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up responske may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hello,
It seems the problem was really caused by drivers for extra sotrage added
during maintenace period.
Thanks for all responses!
Best Regards
eXavier
""Peter Yang[MSFT]"" wrote:
> Hello,
> I agree with Kevin it's best taht you call MS PSS for memory dump analysis
> on this server crash issue. For a complete list of Microsoft Product
> Support Services phone numbers, please go to the following address on the
> World Wide Web:
> http://support.microsoft.com/directory/overview.asp
>
> Also, you may want to use add/edit the following registry key to see if it
> helps
> In the new HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Session
> Manager\Configuration Manager subkey, configure the following entry:
> Name: RegistryLazyFlushInterval
> Data Type: REG_DWORD
> Value data: 60 (decimal)
> You may try to increase Windows paging file size to see if it's helpful.
> It's possible that this kind of issue occurs when there are some issues
> related to server hardware driver. For example, if the operating system
> cannot satisfy the contiguous memory blocks under the 4 GB space, the
> server may become unresponsive.
> Reference the following HP site details:
> http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&
> objectID
> =c00688313&jumpid=reg_R1002_USEN
> Please let's know if you have any further questions or comments. Thanks.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ==================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up responske may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscriptions/support/default.aspx>.
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hello,
Nice to hear you solved the problem!
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
================================================== ===
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
Crashing server (Event ID 333)
Hello,
We experience problems with machines running SQL Servers 2005 in our
production environment. This problem is rather connected to OS or network
settings but hopefully someone here can help. The error below appears several
times in a minute and leads to crash of a machine.
We have clustered environment Windows Servers 2003 SP2 x64 + SQL Server 2005
SP2. This problem started to occur after installation of automatic updates
(bunch of security updates).
Has anyone solved similar issue? Could someone help to track down the problem?
Many thanks
eXavier
Event Type: Error
Event Source: Application Popup
Event Category: None
Event ID: 333
Date: 07.04.2008
Time: 09:01:57
User: N/A
Computer: CMPNT45
Description:
An I/O operation initiated by the Registry failed unrecoverably. The
Registry could not read in, or write out, or flush, one of the files that
contain the system's image of the Registry.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 01 00 6c 00 .....l.
0008: 00 00 00 00 4d 01 00 c0 ...M..Ã?
0010: 00 00 00 00 4d 01 00 c0 ...M..Ã?
0018: 00 00 00 00 00 00 00 00 ......
0020: 00 00 00 00 00 00 00 00 ......I am a consultant by trade and help people with SQL Server problems for a
living. But I gotta say when something like this occurs MY first action
would be (and my advice to my clients would be) call Microsoft PSS!! :)
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"eXavier" <eXavier@.nospam.nospam> wrote in message
news:70DC487A-4928-40E1-9DC0-59FB0AB1B5AB@.microsoft.com...
> Hello,
> We experience problems with machines running SQL Servers 2005 in our
> production environment. This problem is rather connected to OS or network
> settings but hopefully someone here can help. The error below appears
> several
> times in a minute and leads to crash of a machine.
> We have clustered environment Windows Servers 2003 SP2 x64 + SQL Server
> 2005
> SP2. This problem started to occur after installation of automatic updates
> (bunch of security updates).
> Has anyone solved similar issue? Could someone help to track down the
> problem?
> Many thanks
> eXavier
>
> Event Type: Error
> Event Source: Application Popup
> Event Category: None
> Event ID: 333
> Date: 07.04.2008
> Time: 09:01:57
> User: N/A
> Computer: CMPNT45
> Description:
> An I/O operation initiated by the Registry failed unrecoverably. The
> Registry could not read in, or write out, or flush, one of the files that
> contain the system's image of the Registry.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 00 00 00 00 01 00 6c 00 .....l.
> 0008: 00 00 00 00 4d 01 00 c0 ...M..À
> 0010: 00 00 00 00 4d 01 00 c0 ...M..À
> 0018: 00 00 00 00 00 00 00 00 ......
> 0020: 00 00 00 00 00 00 00 00 ......
>|||Hello,
I agree with Kevin it's best taht you call MS PSS for memory dump analysis
on this server crash issue. For a complete list of Microsoft Product
Support Services phone numbers, please go to the following address on the
World Wide Web:
http://support.microsoft.com/directory/overview.asp
Also, you may want to use add/edit the following registry key to see if it
helps
In the new HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session
Manager\Configuration Manager subkey, configure the following entry:
Name: RegistryLazyFlushInterval
Data Type: REG_DWORD
Value data: 60 (decimal)
You may try to increase Windows paging file size to see if it's helpful.
It's possible that this kind of issue occurs when there are some issues
related to server hardware driver. For example, if the operating system
cannot satisfy the contiguous memory blocks under the 4 GB space, the
server may become unresponsive.
Reference the following HP site details:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&
objectID
=c00688313&jumpid=reg_R1002_USEN
Please let's know if you have any further questions or comments. Thanks.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up responske may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello,
It seems the problem was really caused by drivers for extra sotrage added
during maintenace period.
Thanks for all responses!
Best Regards
eXavier
""Peter Yang[MSFT]"" wrote:
> Hello,
> I agree with Kevin it's best taht you call MS PSS for memory dump analysis
> on this server crash issue. For a complete list of Microsoft Product
> Support Services phone numbers, please go to the following address on the
> World Wide Web:
> http://support.microsoft.com/directory/overview.asp
>
> Also, you may want to use add/edit the following registry key to see if it
> helps
> In the new HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session
> Manager\Configuration Manager subkey, configure the following entry:
> Name: RegistryLazyFlushInterval
> Data Type: REG_DWORD
> Value data: 60 (decimal)
> You may try to increase Windows paging file size to see if it's helpful.
> It's possible that this kind of issue occurs when there are some issues
> related to server hardware driver. For example, if the operating system
> cannot satisfy the contiguous memory blocks under the 4 GB space, the
> server may become unresponsive.
> Reference the following HP site details:
> http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&
> objectID
> =c00688313&jumpid=reg_R1002_USEN
> Please let's know if you have any further questions or comments. Thanks.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ==================================================> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up responske may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscriptions/support/default.aspx>.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello,
Nice to hear you solved the problem!
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
=====================================================
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
We experience problems with machines running SQL Servers 2005 in our
production environment. This problem is rather connected to OS or network
settings but hopefully someone here can help. The error below appears several
times in a minute and leads to crash of a machine.
We have clustered environment Windows Servers 2003 SP2 x64 + SQL Server 2005
SP2. This problem started to occur after installation of automatic updates
(bunch of security updates).
Has anyone solved similar issue? Could someone help to track down the problem?
Many thanks
eXavier
Event Type: Error
Event Source: Application Popup
Event Category: None
Event ID: 333
Date: 07.04.2008
Time: 09:01:57
User: N/A
Computer: CMPNT45
Description:
An I/O operation initiated by the Registry failed unrecoverably. The
Registry could not read in, or write out, or flush, one of the files that
contain the system's image of the Registry.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 01 00 6c 00 .....l.
0008: 00 00 00 00 4d 01 00 c0 ...M..Ã?
0010: 00 00 00 00 4d 01 00 c0 ...M..Ã?
0018: 00 00 00 00 00 00 00 00 ......
0020: 00 00 00 00 00 00 00 00 ......I am a consultant by trade and help people with SQL Server problems for a
living. But I gotta say when something like this occurs MY first action
would be (and my advice to my clients would be) call Microsoft PSS!! :)
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"eXavier" <eXavier@.nospam.nospam> wrote in message
news:70DC487A-4928-40E1-9DC0-59FB0AB1B5AB@.microsoft.com...
> Hello,
> We experience problems with machines running SQL Servers 2005 in our
> production environment. This problem is rather connected to OS or network
> settings but hopefully someone here can help. The error below appears
> several
> times in a minute and leads to crash of a machine.
> We have clustered environment Windows Servers 2003 SP2 x64 + SQL Server
> 2005
> SP2. This problem started to occur after installation of automatic updates
> (bunch of security updates).
> Has anyone solved similar issue? Could someone help to track down the
> problem?
> Many thanks
> eXavier
>
> Event Type: Error
> Event Source: Application Popup
> Event Category: None
> Event ID: 333
> Date: 07.04.2008
> Time: 09:01:57
> User: N/A
> Computer: CMPNT45
> Description:
> An I/O operation initiated by the Registry failed unrecoverably. The
> Registry could not read in, or write out, or flush, one of the files that
> contain the system's image of the Registry.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 00 00 00 00 01 00 6c 00 .....l.
> 0008: 00 00 00 00 4d 01 00 c0 ...M..À
> 0010: 00 00 00 00 4d 01 00 c0 ...M..À
> 0018: 00 00 00 00 00 00 00 00 ......
> 0020: 00 00 00 00 00 00 00 00 ......
>|||Hello,
I agree with Kevin it's best taht you call MS PSS for memory dump analysis
on this server crash issue. For a complete list of Microsoft Product
Support Services phone numbers, please go to the following address on the
World Wide Web:
http://support.microsoft.com/directory/overview.asp
Also, you may want to use add/edit the following registry key to see if it
helps
In the new HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session
Manager\Configuration Manager subkey, configure the following entry:
Name: RegistryLazyFlushInterval
Data Type: REG_DWORD
Value data: 60 (decimal)
You may try to increase Windows paging file size to see if it's helpful.
It's possible that this kind of issue occurs when there are some issues
related to server hardware driver. For example, if the operating system
cannot satisfy the contiguous memory blocks under the 4 GB space, the
server may become unresponsive.
Reference the following HP site details:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&
objectID
=c00688313&jumpid=reg_R1002_USEN
Please let's know if you have any further questions or comments. Thanks.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up responske may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello,
It seems the problem was really caused by drivers for extra sotrage added
during maintenace period.
Thanks for all responses!
Best Regards
eXavier
""Peter Yang[MSFT]"" wrote:
> Hello,
> I agree with Kevin it's best taht you call MS PSS for memory dump analysis
> on this server crash issue. For a complete list of Microsoft Product
> Support Services phone numbers, please go to the following address on the
> World Wide Web:
> http://support.microsoft.com/directory/overview.asp
>
> Also, you may want to use add/edit the following registry key to see if it
> helps
> In the new HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session
> Manager\Configuration Manager subkey, configure the following entry:
> Name: RegistryLazyFlushInterval
> Data Type: REG_DWORD
> Value data: 60 (decimal)
> You may try to increase Windows paging file size to see if it's helpful.
> It's possible that this kind of issue occurs when there are some issues
> related to server hardware driver. For example, if the operating system
> cannot satisfy the contiguous memory blocks under the 4 GB space, the
> server may become unresponsive.
> Reference the following HP site details:
> http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&
> objectID
> =c00688313&jumpid=reg_R1002_USEN
> Please let's know if you have any further questions or comments. Thanks.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ==================================================> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up responske may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscriptions/support/default.aspx>.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello,
Nice to hear you solved the problem!
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
=====================================================
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
crashing excel when printing exported RS report
We are having a problem with some reports that get exported to excel and then
trying to print. we don't get this with all reports just some.
Here is what happens:
The report generates fine in RS. We then export to excel. We tell excel to
print and then get a 'Memory can't be read' error and excel crashes.
Whenever we want to just print a report as is, we export to PDF and print
that way. But many times the report is used in excel for further analisys
with other data. I have tried printing without touching the report in excel
and still get the error. So I know it is not something we added.
Because we are only getting this error with some reports and not all, I am
guessing that there must be something that was(n't) added to the report in RS
that would cause this.
Did I make enough sense to explain my issue?We are having the same problem with a couple of reports that were recently
modified. The modifications included adding a couple of additonal parameters
and then displaying the parameter values in the report footer. We already had
the report parameters displaying in the footer with no problems.
Our users are running Office 97 on WIndows NT worksatations. Our
deveoplment environment is running Windows XP with Office 2003 and the report
printing problem cannot be reproduced in the development environment.
Anyone had any luck with fixing this problem?
Ray
"David" wrote:
> We are having a problem with some reports that get exported to excel and then
> trying to print. we don't get this with all reports just some.
> Here is what happens:
> The report generates fine in RS. We then export to excel. We tell excel to
> print and then get a 'Memory can't be read' error and excel crashes.
> Whenever we want to just print a report as is, we export to PDF and print
> that way. But many times the report is used in excel for further analisys
> with other data. I have tried printing without touching the report in excel
> and still get the error. So I know it is not something we added.
> Because we are only getting this error with some reports and not all, I am
> guessing that there must be something that was(n't) added to the report in RS
> that would cause this.
> Did I make enough sense to explain my issue?
>
>|||We have finally solved this issue.
Our poblem was solved by reducing the amount of information in the report
footer. We display the users input parameter values in the footer to allow
them to print the parameters used when rendering the report. In our case we
had increased the number of parameters in the report and hence displayed in
the footer from 6 to 8. This caused Excel to crash when attempting to print
the export file. We have since reduced the parameters in the footer to 6
again and now the report prints in Excel.
Hope this may help you in finding the soucre of you printing problems.
"David" wrote:
> We are having a problem with some reports that get exported to excel and then
> trying to print. we don't get this with all reports just some.
> Here is what happens:
> The report generates fine in RS. We then export to excel. We tell excel to
> print and then get a 'Memory can't be read' error and excel crashes.
> Whenever we want to just print a report as is, we export to PDF and print
> that way. But many times the report is used in excel for further analisys
> with other data. I have tried printing without touching the report in excel
> and still get the error. So I know it is not something we added.
> Because we are only getting this error with some reports and not all, I am
> guessing that there must be something that was(n't) added to the report in RS
> that would cause this.
> Did I make enough sense to explain my issue?
>
>
trying to print. we don't get this with all reports just some.
Here is what happens:
The report generates fine in RS. We then export to excel. We tell excel to
print and then get a 'Memory can't be read' error and excel crashes.
Whenever we want to just print a report as is, we export to PDF and print
that way. But many times the report is used in excel for further analisys
with other data. I have tried printing without touching the report in excel
and still get the error. So I know it is not something we added.
Because we are only getting this error with some reports and not all, I am
guessing that there must be something that was(n't) added to the report in RS
that would cause this.
Did I make enough sense to explain my issue?We are having the same problem with a couple of reports that were recently
modified. The modifications included adding a couple of additonal parameters
and then displaying the parameter values in the report footer. We already had
the report parameters displaying in the footer with no problems.
Our users are running Office 97 on WIndows NT worksatations. Our
deveoplment environment is running Windows XP with Office 2003 and the report
printing problem cannot be reproduced in the development environment.
Anyone had any luck with fixing this problem?
Ray
"David" wrote:
> We are having a problem with some reports that get exported to excel and then
> trying to print. we don't get this with all reports just some.
> Here is what happens:
> The report generates fine in RS. We then export to excel. We tell excel to
> print and then get a 'Memory can't be read' error and excel crashes.
> Whenever we want to just print a report as is, we export to PDF and print
> that way. But many times the report is used in excel for further analisys
> with other data. I have tried printing without touching the report in excel
> and still get the error. So I know it is not something we added.
> Because we are only getting this error with some reports and not all, I am
> guessing that there must be something that was(n't) added to the report in RS
> that would cause this.
> Did I make enough sense to explain my issue?
>
>|||We have finally solved this issue.
Our poblem was solved by reducing the amount of information in the report
footer. We display the users input parameter values in the footer to allow
them to print the parameters used when rendering the report. In our case we
had increased the number of parameters in the report and hence displayed in
the footer from 6 to 8. This caused Excel to crash when attempting to print
the export file. We have since reduced the parameters in the footer to 6
again and now the report prints in Excel.
Hope this may help you in finding the soucre of you printing problems.
"David" wrote:
> We are having a problem with some reports that get exported to excel and then
> trying to print. we don't get this with all reports just some.
> Here is what happens:
> The report generates fine in RS. We then export to excel. We tell excel to
> print and then get a 'Memory can't be read' error and excel crashes.
> Whenever we want to just print a report as is, we export to PDF and print
> that way. But many times the report is used in excel for further analisys
> with other data. I have tried printing without touching the report in excel
> and still get the error. So I know it is not something we added.
> Because we are only getting this error with some reports and not all, I am
> guessing that there must be something that was(n't) added to the report in RS
> that would cause this.
> Did I make enough sense to explain my issue?
>
>
crashing DTS on table import
Hi
I am having some trouble importing certain tables from an odbc database
(Sage Line 50). Most of the tables import without any trouble whatsoever,
however there are 2 tables (SOP_items and POP_items) that always crash dts
when it tries to import them. The DTS screen simply dissappears from the
screen with no error. I realise that it is beyond the scope of this
newsgroup to ask about the specific odbc database. However I was wondering
is there a log somewhere which might help me to shed light on what in the
tables is making it crash. To note I can import and link to the tables in
access with no trouble whatsoever. Thanks for your time.
Dan
There will be no DTS log because it sounds as though something is crashing
DTS. Have you looked in Event Viewer?
Have you tried SPing (What SP are you running?)?
--
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know
"IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
news:OgXbKTBwEHA.3976@.TK2MSFTNGP09.phx.gbl...
> Hi
> I am having some trouble importing certain tables from an odbc database
> (Sage Line 50). Most of the tables import without any trouble whatsoever,
> however there are 2 tables (SOP_items and POP_items) that always crash dts
> when it tries to import them. The DTS screen simply dissappears from the
> screen with no error. I realise that it is beyond the scope of this
> newsgroup to ask about the specific odbc database. However I was
> wondering
> is there a log somewhere which might help me to shed light on what in the
> tables is making it crash. To note I can import and link to the tables in
> access with no trouble whatsoever. Thanks for your time.
> Dan
>
|||Thanks,
It has SP3 on it, just looking at the mdac 2.7 sp1, see if this sorts it.
Dan
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:eVWcPREwEHA.2568@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> There will be no DTS log because it sounds as though something is crashing
> DTS. Have you looked in Event Viewer?
> Have you tried SPing (What SP are you running?)?
> --
> --
> Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
> www.SQLDTS.com - The site for all your DTS needs.
> www.konesans.com - Consultancy from the people who know
>
> "IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
> news:OgXbKTBwEHA.3976@.TK2MSFTNGP09.phx.gbl...
whatsoever,[vbcol=seagreen]
dts[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
in
>
|||Change of plan, going to install Microsoft Data Access Components (MDAC)
2.8, didn't see the newer version at first. I already have SP3 of SQL, it
does advise that SP3a is only for versions below SP3, and as such I
shouldn't install it? Looked in the event log to see if there is any log of
an error, but there is nothing whatsoever. Thanks.
Dan
"IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
news:OgXbKTBwEHA.3976@.TK2MSFTNGP09.phx.gbl...
> Hi
> I am having some trouble importing certain tables from an odbc database
> (Sage Line 50). Most of the tables import without any trouble whatsoever,
> however there are 2 tables (SOP_items and POP_items) that always crash dts
> when it tries to import them. The DTS screen simply dissappears from the
> screen with no error. I realise that it is beyond the scope of this
> newsgroup to ask about the specific odbc database. However I was
wondering
> is there a log somewhere which might help me to shed light on what in the
> tables is making it crash. To note I can import and link to the tables in
> access with no trouble whatsoever. Thanks for your time.
> Dan
>
|||MDAC 2.8 doesn't seem to have made any difference. Any ideas?
Thanks
Dan
"IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
news:e6wXQ2LwEHA.1296@.TK2MSFTNGP10.phx.gbl...
> Change of plan, going to install Microsoft Data Access Components (MDAC)
> 2.8, didn't see the newer version at first. I already have SP3 of SQL, it
> does advise that SP3a is only for versions below SP3, and as such I
> shouldn't install it? Looked in the event log to see if there is any log
of[vbcol=seagreen]
> an error, but there is nothing whatsoever. Thanks.
> Dan
> "IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
> news:OgXbKTBwEHA.3976@.TK2MSFTNGP09.phx.gbl...
whatsoever,[vbcol=seagreen]
dts[vbcol=seagreen]
the[vbcol=seagreen]
> wondering
the[vbcol=seagreen]
in
>
|||Since this is an ODBC data source, you can try to turn on
ODBC tracing on the box where the package runs. Make sure to
turn the trace off after you have crashed with tracing
turned on. You can then go through the tracing log file and
look for ODBC errors.
-Sue
On Tue, 2 Nov 2004 09:34:59 -0000, "IT Dep"
<it@.isslimREMOVE_TO_REPLYited.co.uk> wrote:
>MDAC 2.8 doesn't seem to have made any difference. Any ideas?
>Thanks
>Dan
>"IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
>news:e6wXQ2LwEHA.1296@.TK2MSFTNGP10.phx.gbl...
>of
>whatsoever,
>dts
>the
>the
>in
>
|||Hi
Thanks for the responses, I think that I have worked out where the problem
was occuring. There were date columns in those two tables which were
causing the crash. The dates were in the form dd/mm/yyyy as well as
mm/dd/yyyy, so no wonder it had trouble with the data - what a wonderful
accounting package, if only it used SQL as the native database! Thanks for
all of your help
Dan
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:gu1fo0h2h1n4j4f3pnkgh8u2lfvl3h3tth@.4ax.com... [vbcol=seagreen]
> Since this is an ODBC data source, you can try to turn on
> ODBC tracing on the box where the package runs. Make sure to
> turn the trace off after you have crashed with tracing
> turned on. You can then go through the tracing log file and
> look for ODBC errors.
> -Sue
> On Tue, 2 Nov 2004 09:34:59 -0000, "IT Dep"
> <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote:
(MDAC)[vbcol=seagreen]
it[vbcol=seagreen]
log[vbcol=seagreen]
database[vbcol=seagreen]
crash[vbcol=seagreen]
tables
>
I am having some trouble importing certain tables from an odbc database
(Sage Line 50). Most of the tables import without any trouble whatsoever,
however there are 2 tables (SOP_items and POP_items) that always crash dts
when it tries to import them. The DTS screen simply dissappears from the
screen with no error. I realise that it is beyond the scope of this
newsgroup to ask about the specific odbc database. However I was wondering
is there a log somewhere which might help me to shed light on what in the
tables is making it crash. To note I can import and link to the tables in
access with no trouble whatsoever. Thanks for your time.
Dan
There will be no DTS log because it sounds as though something is crashing
DTS. Have you looked in Event Viewer?
Have you tried SPing (What SP are you running?)?
--
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know
"IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
news:OgXbKTBwEHA.3976@.TK2MSFTNGP09.phx.gbl...
> Hi
> I am having some trouble importing certain tables from an odbc database
> (Sage Line 50). Most of the tables import without any trouble whatsoever,
> however there are 2 tables (SOP_items and POP_items) that always crash dts
> when it tries to import them. The DTS screen simply dissappears from the
> screen with no error. I realise that it is beyond the scope of this
> newsgroup to ask about the specific odbc database. However I was
> wondering
> is there a log somewhere which might help me to shed light on what in the
> tables is making it crash. To note I can import and link to the tables in
> access with no trouble whatsoever. Thanks for your time.
> Dan
>
|||Thanks,
It has SP3 on it, just looking at the mdac 2.7 sp1, see if this sorts it.
Dan
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:eVWcPREwEHA.2568@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> There will be no DTS log because it sounds as though something is crashing
> DTS. Have you looked in Event Viewer?
> Have you tried SPing (What SP are you running?)?
> --
> --
> Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
> www.SQLDTS.com - The site for all your DTS needs.
> www.konesans.com - Consultancy from the people who know
>
> "IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
> news:OgXbKTBwEHA.3976@.TK2MSFTNGP09.phx.gbl...
whatsoever,[vbcol=seagreen]
dts[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
in
>
|||Change of plan, going to install Microsoft Data Access Components (MDAC)
2.8, didn't see the newer version at first. I already have SP3 of SQL, it
does advise that SP3a is only for versions below SP3, and as such I
shouldn't install it? Looked in the event log to see if there is any log of
an error, but there is nothing whatsoever. Thanks.
Dan
"IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
news:OgXbKTBwEHA.3976@.TK2MSFTNGP09.phx.gbl...
> Hi
> I am having some trouble importing certain tables from an odbc database
> (Sage Line 50). Most of the tables import without any trouble whatsoever,
> however there are 2 tables (SOP_items and POP_items) that always crash dts
> when it tries to import them. The DTS screen simply dissappears from the
> screen with no error. I realise that it is beyond the scope of this
> newsgroup to ask about the specific odbc database. However I was
wondering
> is there a log somewhere which might help me to shed light on what in the
> tables is making it crash. To note I can import and link to the tables in
> access with no trouble whatsoever. Thanks for your time.
> Dan
>
|||MDAC 2.8 doesn't seem to have made any difference. Any ideas?
Thanks
Dan
"IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
news:e6wXQ2LwEHA.1296@.TK2MSFTNGP10.phx.gbl...
> Change of plan, going to install Microsoft Data Access Components (MDAC)
> 2.8, didn't see the newer version at first. I already have SP3 of SQL, it
> does advise that SP3a is only for versions below SP3, and as such I
> shouldn't install it? Looked in the event log to see if there is any log
of[vbcol=seagreen]
> an error, but there is nothing whatsoever. Thanks.
> Dan
> "IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
> news:OgXbKTBwEHA.3976@.TK2MSFTNGP09.phx.gbl...
whatsoever,[vbcol=seagreen]
dts[vbcol=seagreen]
the[vbcol=seagreen]
> wondering
the[vbcol=seagreen]
in
>
|||Since this is an ODBC data source, you can try to turn on
ODBC tracing on the box where the package runs. Make sure to
turn the trace off after you have crashed with tracing
turned on. You can then go through the tracing log file and
look for ODBC errors.
-Sue
On Tue, 2 Nov 2004 09:34:59 -0000, "IT Dep"
<it@.isslimREMOVE_TO_REPLYited.co.uk> wrote:
>MDAC 2.8 doesn't seem to have made any difference. Any ideas?
>Thanks
>Dan
>"IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
>news:e6wXQ2LwEHA.1296@.TK2MSFTNGP10.phx.gbl...
>of
>whatsoever,
>dts
>the
>the
>in
>
|||Hi
Thanks for the responses, I think that I have worked out where the problem
was occuring. There were date columns in those two tables which were
causing the crash. The dates were in the form dd/mm/yyyy as well as
mm/dd/yyyy, so no wonder it had trouble with the data - what a wonderful
accounting package, if only it used SQL as the native database! Thanks for
all of your help
Dan
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:gu1fo0h2h1n4j4f3pnkgh8u2lfvl3h3tth@.4ax.com... [vbcol=seagreen]
> Since this is an ODBC data source, you can try to turn on
> ODBC tracing on the box where the package runs. Make sure to
> turn the trace off after you have crashed with tracing
> turned on. You can then go through the tracing log file and
> look for ODBC errors.
> -Sue
> On Tue, 2 Nov 2004 09:34:59 -0000, "IT Dep"
> <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote:
(MDAC)[vbcol=seagreen]
it[vbcol=seagreen]
log[vbcol=seagreen]
database[vbcol=seagreen]
crash[vbcol=seagreen]
tables
>
crashing DTS on table import
Hi
I am having some trouble importing certain tables from an odbc database
(Sage Line 50). Most of the tables import without any trouble whatsoever,
however there are 2 tables (SOP_items and POP_items) that always crash dts
when it tries to import them. The DTS screen simply dissappears from the
screen with no error. I realise that it is beyond the scope of this
newsgroup to ask about the specific odbc database. However I was wondering
is there a log somewhere which might help me to shed light on what in the
tables is making it crash. To note I can import and link to the tables in
access with no trouble whatsoever. Thanks for your time.
DanThere will be no DTS log because it sounds as though something is crashing
DTS. Have you looked in Event Viewer?
Have you tried SPing (What SP are you running?)?
--
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know
"IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
news:OgXbKTBwEHA.3976@.TK2MSFTNGP09.phx.gbl...
> Hi
> I am having some trouble importing certain tables from an odbc database
> (Sage Line 50). Most of the tables import without any trouble whatsoever,
> however there are 2 tables (SOP_items and POP_items) that always crash dts
> when it tries to import them. The DTS screen simply dissappears from the
> screen with no error. I realise that it is beyond the scope of this
> newsgroup to ask about the specific odbc database. However I was
> wondering
> is there a log somewhere which might help me to shed light on what in the
> tables is making it crash. To note I can import and link to the tables in
> access with no trouble whatsoever. Thanks for your time.
> Dan
>|||Thanks,
It has SP3 on it, just looking at the mdac 2.7 sp1, see if this sorts it.
Dan
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:eVWcPREwEHA.2568@.TK2MSFTNGP11.phx.gbl...
> There will be no DTS log because it sounds as though something is crashing
> DTS. Have you looked in Event Viewer?
> Have you tried SPing (What SP are you running?)?
> --
> --
> Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
> www.SQLDTS.com - The site for all your DTS needs.
> www.konesans.com - Consultancy from the people who know
>
> "IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
> news:OgXbKTBwEHA.3976@.TK2MSFTNGP09.phx.gbl...
whatsoever,[vbcol=seagreen]
dts[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
in[vbcol=seagreen]
>|||Change of plan, going to install Microsoft Data Access Components (MDAC)
2.8, didn't see the newer version at first. I already have SP3 of SQL, it
does advise that SP3a is only for versions below SP3, and as such I
shouldn't install it? Looked in the event log to see if there is any log of
an error, but there is nothing whatsoever. Thanks.
Dan
"IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
news:OgXbKTBwEHA.3976@.TK2MSFTNGP09.phx.gbl...
> Hi
> I am having some trouble importing certain tables from an odbc database
> (Sage Line 50). Most of the tables import without any trouble whatsoever,
> however there are 2 tables (SOP_items and POP_items) that always crash dts
> when it tries to import them. The DTS screen simply dissappears from the
> screen with no error. I realise that it is beyond the scope of this
> newsgroup to ask about the specific odbc database. However I was
wondering
> is there a log somewhere which might help me to shed light on what in the
> tables is making it crash. To note I can import and link to the tables in
> access with no trouble whatsoever. Thanks for your time.
> Dan
>|||MDAC 2.8 doesn't seem to have made any difference. Any ideas?
Thanks
Dan
"IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
news:e6wXQ2LwEHA.1296@.TK2MSFTNGP10.phx.gbl...
> Change of plan, going to install Microsoft Data Access Components (MDAC)
> 2.8, didn't see the newer version at first. I already have SP3 of SQL, it
> does advise that SP3a is only for versions below SP3, and as such I
> shouldn't install it? Looked in the event log to see if there is any log
of
> an error, but there is nothing whatsoever. Thanks.
> Dan
> "IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
> news:OgXbKTBwEHA.3976@.TK2MSFTNGP09.phx.gbl...
whatsoever,[vbcol=seagreen]
dts[vbcol=seagreen]
the[vbcol=seagreen]
> wondering
the[vbcol=seagreen]
in[vbcol=seagreen]
>|||Since this is an ODBC data source, you can try to turn on
ODBC tracing on the box where the package runs. Make sure to
turn the trace off after you have crashed with tracing
turned on. You can then go through the tracing log file and
look for ODBC errors.
-Sue
On Tue, 2 Nov 2004 09:34:59 -0000, "IT Dep"
<it@.isslimREMOVE_TO_REPLYited.co.uk> wrote:
>MDAC 2.8 doesn't seem to have made any difference. Any ideas?
>Thanks
>Dan
>"IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
>news:e6wXQ2LwEHA.1296@.TK2MSFTNGP10.phx.gbl...
>of
>whatsoever,
>dts
>the
>the
>in
>|||Hi
Thanks for the responses, I think that I have worked out where the problem
was occuring. There were date columns in those two tables which were
causing the crash. The dates were in the form dd/mm/yyyy as well as
mm/dd/yyyy, so no wonder it had trouble with the data - what a wonderful
accounting package, if only it used SQL as the native database! Thanks for
all of your help
Dan
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:gu1fo0h2h1n4j4f3pnkgh8u2lfvl3h3tth@.
4ax.com...
> Since this is an ODBC data source, you can try to turn on
> ODBC tracing on the box where the package runs. Make sure to
> turn the trace off after you have crashed with tracing
> turned on. You can then go through the tracing log file and
> look for ODBC errors.
> -Sue
> On Tue, 2 Nov 2004 09:34:59 -0000, "IT Dep"
> <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote:
>
(MDAC)[vbcol=seagreen]
it[vbcol=seagreen]
log[vbcol=seagreen]
database[vbcol=seagreen]
crash[vbcol=seagreen]
tables[vbcol=seagreen]
>
I am having some trouble importing certain tables from an odbc database
(Sage Line 50). Most of the tables import without any trouble whatsoever,
however there are 2 tables (SOP_items and POP_items) that always crash dts
when it tries to import them. The DTS screen simply dissappears from the
screen with no error. I realise that it is beyond the scope of this
newsgroup to ask about the specific odbc database. However I was wondering
is there a log somewhere which might help me to shed light on what in the
tables is making it crash. To note I can import and link to the tables in
access with no trouble whatsoever. Thanks for your time.
DanThere will be no DTS log because it sounds as though something is crashing
DTS. Have you looked in Event Viewer?
Have you tried SPing (What SP are you running?)?
--
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know
"IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
news:OgXbKTBwEHA.3976@.TK2MSFTNGP09.phx.gbl...
> Hi
> I am having some trouble importing certain tables from an odbc database
> (Sage Line 50). Most of the tables import without any trouble whatsoever,
> however there are 2 tables (SOP_items and POP_items) that always crash dts
> when it tries to import them. The DTS screen simply dissappears from the
> screen with no error. I realise that it is beyond the scope of this
> newsgroup to ask about the specific odbc database. However I was
> wondering
> is there a log somewhere which might help me to shed light on what in the
> tables is making it crash. To note I can import and link to the tables in
> access with no trouble whatsoever. Thanks for your time.
> Dan
>|||Thanks,
It has SP3 on it, just looking at the mdac 2.7 sp1, see if this sorts it.
Dan
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:eVWcPREwEHA.2568@.TK2MSFTNGP11.phx.gbl...
> There will be no DTS log because it sounds as though something is crashing
> DTS. Have you looked in Event Viewer?
> Have you tried SPing (What SP are you running?)?
> --
> --
> Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
> www.SQLDTS.com - The site for all your DTS needs.
> www.konesans.com - Consultancy from the people who know
>
> "IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
> news:OgXbKTBwEHA.3976@.TK2MSFTNGP09.phx.gbl...
whatsoever,[vbcol=seagreen]
dts[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
in[vbcol=seagreen]
>|||Change of plan, going to install Microsoft Data Access Components (MDAC)
2.8, didn't see the newer version at first. I already have SP3 of SQL, it
does advise that SP3a is only for versions below SP3, and as such I
shouldn't install it? Looked in the event log to see if there is any log of
an error, but there is nothing whatsoever. Thanks.
Dan
"IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
news:OgXbKTBwEHA.3976@.TK2MSFTNGP09.phx.gbl...
> Hi
> I am having some trouble importing certain tables from an odbc database
> (Sage Line 50). Most of the tables import without any trouble whatsoever,
> however there are 2 tables (SOP_items and POP_items) that always crash dts
> when it tries to import them. The DTS screen simply dissappears from the
> screen with no error. I realise that it is beyond the scope of this
> newsgroup to ask about the specific odbc database. However I was
wondering
> is there a log somewhere which might help me to shed light on what in the
> tables is making it crash. To note I can import and link to the tables in
> access with no trouble whatsoever. Thanks for your time.
> Dan
>|||MDAC 2.8 doesn't seem to have made any difference. Any ideas?
Thanks
Dan
"IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
news:e6wXQ2LwEHA.1296@.TK2MSFTNGP10.phx.gbl...
> Change of plan, going to install Microsoft Data Access Components (MDAC)
> 2.8, didn't see the newer version at first. I already have SP3 of SQL, it
> does advise that SP3a is only for versions below SP3, and as such I
> shouldn't install it? Looked in the event log to see if there is any log
of
> an error, but there is nothing whatsoever. Thanks.
> Dan
> "IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
> news:OgXbKTBwEHA.3976@.TK2MSFTNGP09.phx.gbl...
whatsoever,[vbcol=seagreen]
dts[vbcol=seagreen]
the[vbcol=seagreen]
> wondering
the[vbcol=seagreen]
in[vbcol=seagreen]
>|||Since this is an ODBC data source, you can try to turn on
ODBC tracing on the box where the package runs. Make sure to
turn the trace off after you have crashed with tracing
turned on. You can then go through the tracing log file and
look for ODBC errors.
-Sue
On Tue, 2 Nov 2004 09:34:59 -0000, "IT Dep"
<it@.isslimREMOVE_TO_REPLYited.co.uk> wrote:
>MDAC 2.8 doesn't seem to have made any difference. Any ideas?
>Thanks
>Dan
>"IT Dep" <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote in message
>news:e6wXQ2LwEHA.1296@.TK2MSFTNGP10.phx.gbl...
>of
>whatsoever,
>dts
>the
>the
>in
>|||Hi
Thanks for the responses, I think that I have worked out where the problem
was occuring. There were date columns in those two tables which were
causing the crash. The dates were in the form dd/mm/yyyy as well as
mm/dd/yyyy, so no wonder it had trouble with the data - what a wonderful
accounting package, if only it used SQL as the native database! Thanks for
all of your help
Dan
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:gu1fo0h2h1n4j4f3pnkgh8u2lfvl3h3tth@.
4ax.com...
> Since this is an ODBC data source, you can try to turn on
> ODBC tracing on the box where the package runs. Make sure to
> turn the trace off after you have crashed with tracing
> turned on. You can then go through the tracing log file and
> look for ODBC errors.
> -Sue
> On Tue, 2 Nov 2004 09:34:59 -0000, "IT Dep"
> <it@.isslimREMOVE_TO_REPLYited.co.uk> wrote:
>
(MDAC)[vbcol=seagreen]
it[vbcol=seagreen]
log[vbcol=seagreen]
database[vbcol=seagreen]
crash[vbcol=seagreen]
tables[vbcol=seagreen]
>
Crashing a server
Hi,
First of all I want to know if there is a manual way of crashing a server.
My second question -
I have two Standard Edition SQL Servers one(S1) running the production databases, and the other(S2) is just a standby. The database files are on a DISK array. Suppose if S1 crashes, can I point to the S2 Server to the same DISK array and use sp_attch sp's
to bring the database up.
Thanks,
Elvis
Have yo tried poring coke on the motherboard? That would crash the server
pretty good... you might want to explain what particular behairor you want
to cause to happen and then perhaps someone could offer good advice about
how to achieve it...
About the sp_attach...
there are a few issues.
1. Is it shared in some kind of cluster or SAN? Databases in SQL need to be
on local drives. So, you can't simply attach if the files are on a drive
that looks like a network drive to SQL.
2. If S1 goes down in an uncontrolled manner... the files themselves may be
damaged. Even if they're not damages... you can't guarantee the ability to
do an attach unless you had first done a detach. So... know... this doesn't
sound like a great solutioin.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Elvis Clinton" <anonymous@.discussions.microsoft.com> wrote in message
news:FA9EB5D2-AB32-4903-B270-DC5F6C2AC09C@.microsoft.com...
> Hi,
> First of all I want to know if there is a manual way of crashing a server.
> My second question -
> I have two Standard Edition SQL Servers one(S1) running the production
databases, and the other(S2) is just a standby. The database files are on a
DISK array. Suppose if S1 crashes, can I point to the S2 Server to the same
DISK array and use sp_attch sp's to bring the database up.
> Thanks,
> Elvis
First of all I want to know if there is a manual way of crashing a server.
My second question -
I have two Standard Edition SQL Servers one(S1) running the production databases, and the other(S2) is just a standby. The database files are on a DISK array. Suppose if S1 crashes, can I point to the S2 Server to the same DISK array and use sp_attch sp's
to bring the database up.
Thanks,
Elvis
Have yo tried poring coke on the motherboard? That would crash the server
pretty good... you might want to explain what particular behairor you want
to cause to happen and then perhaps someone could offer good advice about
how to achieve it...
About the sp_attach...
there are a few issues.
1. Is it shared in some kind of cluster or SAN? Databases in SQL need to be
on local drives. So, you can't simply attach if the files are on a drive
that looks like a network drive to SQL.
2. If S1 goes down in an uncontrolled manner... the files themselves may be
damaged. Even if they're not damages... you can't guarantee the ability to
do an attach unless you had first done a detach. So... know... this doesn't
sound like a great solutioin.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Elvis Clinton" <anonymous@.discussions.microsoft.com> wrote in message
news:FA9EB5D2-AB32-4903-B270-DC5F6C2AC09C@.microsoft.com...
> Hi,
> First of all I want to know if there is a manual way of crashing a server.
> My second question -
> I have two Standard Edition SQL Servers one(S1) running the production
databases, and the other(S2) is just a standby. The database files are on a
DISK array. Suppose if S1 crashes, can I point to the S2 Server to the same
DISK array and use sp_attch sp's to bring the database up.
> Thanks,
> Elvis
Crashing a server
Hi,
First of all I want to know if there is a manual way of crashing a server.
My second question -
I have two Standard Edition SQL Servers one(S1) running the production datab
ases, and the other(S2) is just a standby. The database files are on a DISK
array. Suppose if S1 crashes, can I point to the S2 Server to the same DISK
array and use sp_attch sp's
to bring the database up.
Thanks,
ElvisHave yo tried poring coke on the motherboard? That would crash the server
pretty good... you might want to explain what particular behairor you want
to cause to happen and then perhaps someone could offer good advice about
how to achieve it...
About the sp_attach...
there are a few issues.
1. Is it shared in some kind of cluster or SAN? Databases in SQL need to be
on local drives. So, you can't simply attach if the files are on a drive
that looks like a network drive to SQL.
2. If S1 goes down in an uncontrolled manner... the files themselves may be
damaged. Even if they're not damages... you can't guarantee the ability to
do an attach unless you had first done a detach. So... know... this doesn't
sound like a great solutioin.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Elvis Clinton" <anonymous@.discussions.microsoft.com> wrote in message
news:FA9EB5D2-AB32-4903-B270-DC5F6C2AC09C@.microsoft.com...
> Hi,
> First of all I want to know if there is a manual way of crashing a server.
> My second question -
> I have two Standard Edition SQL Servers one(S1) running the production
databases, and the other(S2) is just a standby. The database files are on a
DISK array. Suppose if S1 crashes, can I point to the S2 Server to the same
DISK array and use sp_attch sp's to bring the database up.
> Thanks,
> Elvis
First of all I want to know if there is a manual way of crashing a server.
My second question -
I have two Standard Edition SQL Servers one(S1) running the production datab
ases, and the other(S2) is just a standby. The database files are on a DISK
array. Suppose if S1 crashes, can I point to the S2 Server to the same DISK
array and use sp_attch sp's
to bring the database up.
Thanks,
ElvisHave yo tried poring coke on the motherboard? That would crash the server
pretty good... you might want to explain what particular behairor you want
to cause to happen and then perhaps someone could offer good advice about
how to achieve it...
About the sp_attach...
there are a few issues.
1. Is it shared in some kind of cluster or SAN? Databases in SQL need to be
on local drives. So, you can't simply attach if the files are on a drive
that looks like a network drive to SQL.
2. If S1 goes down in an uncontrolled manner... the files themselves may be
damaged. Even if they're not damages... you can't guarantee the ability to
do an attach unless you had first done a detach. So... know... this doesn't
sound like a great solutioin.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Elvis Clinton" <anonymous@.discussions.microsoft.com> wrote in message
news:FA9EB5D2-AB32-4903-B270-DC5F6C2AC09C@.microsoft.com...
> Hi,
> First of all I want to know if there is a manual way of crashing a server.
> My second question -
> I have two Standard Edition SQL Servers one(S1) running the production
databases, and the other(S2) is just a standby. The database files are on a
DISK array. Suppose if S1 crashes, can I point to the S2 Server to the same
DISK array and use sp_attch sp's to bring the database up.
> Thanks,
> Elvis
Subscribe to:
Posts (Atom)