Thanks David, unfortunately that didn't help.
I've made an additional discovery. If I'm connected to my work
network, it behaves normally. Once I disconnect, I get these errors.
It could be some sort of name resolution problem. Axapta does seem to
think that the DB is on the network. It's not, it's on the same
machine and always has been. Any ideas at all apreciated because, at
present, Axapta is useless to me.
--- In Axapta-Knowledge-Village@yahoogroups.com, "David Casas"
<[EMAIL PROTECTED]> wrote:
>
> It´s a resolution name problem.
> Try with the ip, and if you can modify de hosts file adding the
local name with the ip.
>
> Regards.
>
> David
> ----- Original Message -----
> From: jetjockey.geo
> To: Axapta-Knowledge-Village@yahoogroups.com
> Sent: Tuesday, January 31, 2006 10:27 AM
> Subject: [Axapta-Knowledge-Village] SQL Server timeout
>
>
>
> My Axapta 3 demo was working fine. It started throwing connection
> errors occassionally. They have been increasing over the last week or
> so and now I find I can't log in at all as the timeout occurs before
> the login dlg is shown. The error is:
>
> --------------
> SQL has reported the following error:
>
> [Microsoft][ODBC SQL Server Driver] Timeout expired. Connect
> information was
>
Userid=[bmssa],Database=[AXDB],Server=[(local)\AXMSDE001],DSN=[AXMSDE001],
> Other=[]
>
> You may refer to the error log file for further details.
>
> Retry the operation
> --------------
>
> Previously, a retry would get things going again, sometimes after
> several attempts. Now, nothing works. I've done some reading around
> regarding SQL Server timeouts and tried reinstalling both Axapta and
> the Desktop SQL Engine numerous times without success. The log files
> and system event log contain nothing that I can relate to this.
>
> The one thing I have noticed is that the AXMSDE001 datasource doesn't
> connect if the local domain is used. If I change it to use
> "garys-laptop\AXMSDE001" (the machine name) it connects. The error
> shows that Axapta is trying to use local. What I don't understand is
> why local fails. Changing the datasource to use "garys-laptop" doesn't
> stop Axapta failing, even though the datasource connects.
>
> As always, any ideas are appreciated.
>
> Thanks,
>
> Gary.
>
>
>
>
>
>
>
>
>
> Sharing the knowledge on Axapta.
> Visit www.frappr.com/axapta for axapta friends.
>
>
>
>
------------------------------------------------------------------------------
> YAHOO! GROUPS LINKS
>
> a.. Visit your group "Axapta-Knowledge-Village" on the web.
>
> b.. To unsubscribe from this group, send an email to:
> [EMAIL PROTECTED]
>
> c.. Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service.
>
>
>
------------------------------------------------------------------------------
>
>
>
> [Non-text portions of this message have been removed]
>
Sharing the knowledge on Axapta.
Visit www.frappr.com/axapta for axapta friends.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/Axapta-Knowledge-Village/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
