Sage 100

Hi All,

I am having this exact issue with a client.  We have checked everywhere and cannot find what is causing this file to grow.

I do know that I cannot delete it without stopping SQL Server service.

Any ideas would be greatly appreciated.
Thanks Jacquie.

Check all DSN's on that machine.

Hi All,

I am having this exact issue with a client.  We have checked everywhere and cannot find what is causing this file to grow.

I do know that I cannot delete it without stopping SQL Server service.

Any ideas would be greatly appreciated.
Thanks Jacquie.

Thanks Kevin

we have gone through them several times and none are enabled. Is there a registry edit that can turn it off?

I also understand that it can be built into a script-is that correct - I've been checking with our third-parties but they all say "not them".

All ideas are appreciated-the file grew to 30 GB over the weekend  

Thanks again

Jacquie. 

Check all DSN's on that machine.

Hi All,

I am having this exact issue with a client.  We have checked everywhere and cannot find what is causing this file to grow.

I do know that I cannot delete it without stopping SQL Server service.

Any ideas would be greatly appreciated.
Thanks Jacquie.

Is it Advanced with the CS-ODBC service (which might be responsible)?

Thanks Kevin

we have gone through them several times and none are enabled. Is there a registry edit that can turn it off?

I also understand that it can be built into a script-is that correct - I've been checking with our third-parties but they all say "not them".

All ideas are appreciated-the file grew to 30 GB over the weekend  

Thanks again

Jacquie. 

Check all DSN's on that machine.

Hi All,

I am having this exact issue with a client.  We have checked everywhere and cannot find what is causing this file to grow.

I do know that I cannot delete it without stopping SQL Server service.

Any ideas would be greatly appreciated.
Thanks Jacquie.

Yes, it is Advanced, but not sure what the CS-ODBC service is.

Can it be uninstalled and reinstalled?

Is it Advanced with the CS-ODBC service (which might be responsible)?

Thanks Kevin

we have gone through them several times and none are enabled. Is there a registry edit that can turn it off?

I also understand that it can be built into a script-is that correct - I've been checking with our third-parties but they all say "not them".

All ideas are appreciated-the file grew to 30 GB over the weekend  

Thanks again

Jacquie. 

Check all DSN's on that machine.

Hi All,

I am having this exact issue with a client.  We have checked everywhere and cannot find what is causing this file to grow.

I do know that I cannot delete it without stopping SQL Server service.

Any ideas would be greatly appreciated.
Thanks Jacquie.

Check if CS-ODBC is enabled in System Configuration, tab 5.

Sage KB has instructions for removing / re-adding the Windows Service, if it is enabled.

Yes, it is Advanced, but not sure what the CS-ODBC service is.

Can it be uninstalled and reinstalled?

Is it Advanced with the CS-ODBC service (which might be responsible)?

Thanks Kevin

we have gone through them several times and none are enabled. Is there a registry edit that can turn it off?

I also understand that it can be built into a script-is that correct - I've been checking with our third-parties but they all say "not them".

All ideas are appreciated-the file grew to 30 GB over the weekend  

Thanks again

Jacquie. 

Check all DSN's on that machine.

Hi All,

I am having this exact issue with a client.  We have checked everywhere and cannot find what is causing this file to grow.

I do know that I cannot delete it without stopping SQL Server service.

Any ideas would be greatly appreciated.
Thanks Jacquie.

Is it Advanced with the CS-ODBC service (which might be responsible)?

Thanks Kevin

we have gone through them several times and none are enabled. Is there a registry edit that can turn it off?

I also understand that it can be built into a script-is that correct - I've been checking with our third-parties but they all say "not them".

All ideas are appreciated-the file grew to 30 GB over the weekend  

Thanks again

Jacquie. 

Check all DSN's on that machine.

Hi All,

I am having this exact issue with a client.  We have checked everywhere and cannot find what is causing this file to grow.

I do know that I cannot delete it without stopping SQL Server service.

Any ideas would be greatly appreciated.
Thanks Jacquie.

Hi Kevin,

Thanks much for the responses.  After several weeks, we were finally able to figure out the issue and I wanted to note it in case anyone else had this issue.

We have a linked server setup in SQL.  Not sure what caused it to change but the connection string was set to debug=1 (True) and it should have been set to 0 (false).

May be of help to someone in the future.

Thanks Jacquie.

Is it Advanced with the CS-ODBC service (which might be responsible)?

Thanks Kevin

we have gone through them several times and none are enabled. Is there a registry edit that can turn it off?

I also understand that it can be built into a script-is that correct - I've been checking with our third-parties but they all say "not them".

All ideas are appreciated-the file grew to 30 GB over the weekend  

Thanks again

Jacquie. 

Check all DSN's on that machine.

Hi All,

I am having this exact issue with a client.  We have checked everywhere and cannot find what is causing this file to grow.

I do know that I cannot delete it without stopping SQL Server service.

Any ideas would be greatly appreciated.
Thanks Jacquie.